Slimdown10 – turn Windows 10 22H2 or LTSC 2021 into classic/legacy Windows

Discussion in 'Windows 10' started by Deleted member 190847, Feb 15, 2023.

  1. egalerst

    egalerst MDL Junior Member

    Sep 3, 2017
    64
    58
    0
    #1241 egalerst, Jul 12, 2024
    Last edited: Jul 12, 2024
    @SunLion
    In "hfixes_ltsc.txt" you replaced the baseless urls, but kept the filename of last months KB as target ;)
    In "hfixes_all.txt" the 21H2 Enablement Package v1237 target is x64 twice

    If you wanna continue taking care of Slimdown you might consider adding my changes from Post_1153
    As acer5100 would say "dont use 90s installers when you can deploy" ;)

    Updated hfixes only included.
    Thanks for your work
     

    Attached Files:

  2. SunLion

    SunLion MDL Addicted

    May 11, 2011
    662
    1,626
    30
    #1242 SunLion, Jul 12, 2024
    Last edited: Jul 13, 2024

    Attached Files:

  3. KMPLAYER

    KMPLAYER MDL Junior Member

    Jan 12, 2014
    72
    51
    0
  4. Agony4121

    Agony4121 MDL Novice

    Apr 12, 2024
    14
    6
    0
  5. SunLion

    SunLion MDL Addicted

    May 11, 2011
    662
    1,626
    30
    #1245 SunLion, Jul 13, 2024
    Last edited: Jul 13, 2024

    Attached Files:

  6. SunLion

    SunLion MDL Addicted

    May 11, 2011
    662
    1,626
    30
    #1246 SunLion, Jul 13, 2024
    Last edited: Jul 13, 2024
    Still clarifying some questions from @KMPLAYER:

    This is part of the original script. I didn't change anything about it.
    The file size became larger because of 1.wim which was not removed before creating the final ISO, which has already been corrected in the script.

    My test with:
    bg-bg_windows_10_consumer_editions_version_22h2_updated_march_2024_x64_dvd_2ff6c8a4.iso
    1 – The script ran until the end and presented some errors:
    1.1 – The integration of the Windows10.0-KB5020683-x64.msu update presented an error, which was expected, as this update only applies to HOME and PROFESSIONAL versions (line 18306)
    1.2 – DaRT integration presented an error because the Dart_w10_bg-BG.tpk file was not found
    See attached LOG file

    2 – The other commands worked normally.

    3 – The install.wim image, after being modified, was 4.45 GB in size (4787679678 bytes)

    Now I will try to adjust these errors above.

    I will also create another script to use W10UI.

    The intention is to preserve the original codes as much as possible.

    That was the first step... Wait...


    IMPORTANT reminders!

    1 - The folder containing the script must be excluded from antivirus scanning.

    2 - Before running the script, disable the antivirus

    3 - Do not execute anything else while the script is running

    4 - Run the script as administrator
     

    Attached Files:

  7. hoak

    hoak MDL Member

    Nov 13, 2009
    231
    424
    10
  8. CharlieHNY

    CharlieHNY MDL Novice

    Apr 3, 2015
    1
    0
    0
    Script doesn't seems to be working spits out 'The system cannot find the path specified' error tested on two different PCs and ISOs consumer and LTSC edition with no antivirus software no modifications to script. when manually extracted ISO to DVD folder with 7zip, it crashed cmd window at Exporting image 100% with same error. forum doesn't letting me post full Log link
     
  9. SunLion

    SunLion MDL Addicted

    May 11, 2011
    662
    1,626
    30
    Would you have a log file to post?

    Try extracting Slimdown10_v2_02 to a short path, for example C:\Slimdown10 and try again.

    This part of the script has not been modified.
     
  10. Agony4121

    Agony4121 MDL Novice

    Apr 12, 2024
    14
    6
    0
    All of them was already done when I last took the log.
    The original Slimdown script from 2023 completes without errors.
     
  11. gutentaghallo

    gutentaghallo MDL Novice

    Jan 1, 2022
    18
    5
    0
    Not sure if my info helps, but I have had Slimdown10 on my D: drive fully functional and moved it to a subfolder on my E: drive. Afterwards it didnt worked anymore. So just copying the files to another location broke the script. (happened with version 2-02-4)
     
  12. SunLion

    SunLion MDL Addicted

    May 11, 2011
    662
    1,626
    30
  13. SunLion

    SunLion MDL Addicted

    May 11, 2011
    662
    1,626
    30
    Good!

    This error is not significant as it only shows the image details as below:

    ###############################################
    Get-WInfo
    ###############################################


    WIM Information:
    ----------------
    Path: E:\SD10_v2_02_6\DVD\sources\install.wim
    GUID: 0x8fe85f36e4ec9c419d2d9584e7a332b4
    Version: 68864
    Image Count: 1
    Compression: LZX
    Chunk Size: 32768 bytes
    Part Number: 1/1
    Boot Index: 0
    Size: 4268797722 bytes
    Attributes: Integrity info, Relative path junction

    Available Images:
    -----------------
    Index: 1
    Name: Windows 10 Pro
    Description: Windows 10 Pro
    Directory Count: 30400
    File Count: 103129
    Total Bytes: 15625614711
    Hard Link Bytes: 6363412644
    Creation Time: Sat Dec 07 16:09:04 2019 UTC
    Last Modification Time: Tue Jul 16 13:42:09 2024 UTC
    Architecture: x86_64
    Product Name: Sistema Operacional Microsoft® Windows®
    Edition ID: Professional
    Installation Type: Client
    Product Type: WinNT
    Product Suite: Terminal Server
    Languages: pt-BR
    Default Language: pt-BR
    System Root: WINDOWS
    Major Version: 10
    Minor Version: 0
    Build: 19045
    Service Pack Build: 4651
    Service Pack Level: 0
    Flags: Professional
    WIMBoot compatible: no



    Just to confirm, check the properties of install.wim, if it is read-only, please.

    If possible, upload the log file (rename it to .txt first)

    Thanks
     
  14. Agony4121

    Agony4121 MDL Novice

    Apr 12, 2024
    14
    6
    0
    I dont have the log file now as I deleted it, successfully installed windows with the created iso and everything seems to be working as itended. Thanks for your work :)