Hoping there is an updated ToolKitHelper for the current (stable) versions of Windows 10 and 11 soon. Of course I understand that @MSMG health wasn't 100% last time he posted, so I shall wait patiently.
But toolbox works with 10 and 11 I have installed latest insider preview 10.0.22624.1755 and the only thing I had to do is to manually copy 4 files from untouched iso to directory of installed Windows. Dism didn't want to do that on its own. Took me like week to find out what files were corrupted but I made it .
Unfortunately, disable / enable features via DisableFeaturesList.txt / EnableFeaturesList.txt not working for me on last 22621/22624 builds with MSMG Toolkit ver.13.3, but with ver. 13.2 it's working.
Hi MSMG After debloating the install.wim file with Toolkit 13.3 , My Windows 10 does not hide some of the file extensions , for example .msu extension. I downloaded .NET CU Preview and it is shown like that on my computer windows10.0-kb5026513-arm64-ndp48_33ce98c34d34e6f69709bac993f49cce7acbde4f.msu ( .msu extension is not hidden) When i click on it , it does not install and it asks me to choose the program i want to open it with Version 13.2 was fine and did not have this issue , i hope you have a solution for this Thanks for this great tool and thanks for your help
Will be releasing a new version today, have added some new components for removal, the below components removal also comes with issues which the user needs to deal with. ClientCBS - Will remove the user experience pack, breaks Input App, Windows 11 Start menu and Screen clipping. For Windows 11 v21H2 it will restore the Windows 10 Start menu, Explorer and Taskbar., also can restore some resources files for some system apps. CloudExperienceHost - Requires a full unattended installation without internet connectivity and requires SkipMachineOOBE enabled in unattended xml. If removing this component then do not add OOBE updates to the image. InputApp - Will lose the touch input application, touch keyboard functionality. ShellExperienceHost - Breaks Start Menu and taskbar flyouts popups for battery calendar, clock, sound, network, action center for Windows 10 v17763-v18363 Breaks Taskbar flyouts popups for battery calendar, clock, sound, network, action center for Windows 10 v1904x and Windows 11 StartMenuExperienceHost - Breaks Start Menu, for Windows 11, a error dialog will appear on first boot, once the ok button in the dialog box is clicked it will logout the OS, then the user needs to login to fix this error. This is due to Windows 11's default show Startmenu on logon option, if anyone finds a tweak to disable it, will add to the removal process. UndockedDevKit - Will remove Setting -> System -> About window page. when this component is removed alone without the above components the windows Setup completes properly else it will get stuck with a blank screen at the setup completion stage, then the user needs to reboot once to fix it. So haven't added this component in the Toolkit's removal menu, if the user want to remove it then they can use the list or manual method.
The code for Disable or Enable Features is untouched for past few versions, may be it's due to the newer version of DISM being added to the Toolkit is causing the error.
You have removed Windows Update component and hence the .msu extension has become unknown extension, removing Windows Update component also removes the installation of .msu files. You can extract the update cab file from the msu file and install the cab update from command prompt.
10.0.22624.1755 is unsupported because the updated components files will not be removed while removing the component and hence the DSM will show the errors.
@bala1 and I just implemented a function to create "AutoUnattend.xml" in MainMenu before using ApplyMenu. What do you think about delaying today's release a bit and implementing this function in this release as it will be useful for users?
Okay then will upload just the updated Toolkit.cmd and ToolKitHelper.exe so that users who waiting for the update ToolkitHelper.exe can use it. Do share the code for creating AutoUnattend.xml, will add the feature and release the Toolkit.
Spoiler: Images In AutoUnattendXML_Feature[InterActionVRI].zip there are the Toolkit*13.4.cmd and text file with the changes. If User wants Admin Account the Local User Account will be without Admin Privileges. If boot.wim is mounted will exhib an option to integrate the AutoUnattend.xml in boot Index 2 Windows Setup. You can Integrate in one or another options. Never both. The script will not allow that. I put a random for the computer name generation thinking about another detail. Which is not having 2 machines with the same name on the same network. But if the User uses the same file multiple times on different machines this will have no effect. Then, the user must leave the "Machine Name" empty, for the system to choose the "Machine Name" automatically. This is good for Technicians. But I didn't leave any warning in the option, just in case. EDIT: Toolkit*cmd updated from 13.3 to 13.4.
I think there's something else going on, I have tested latest toolkit against several win 11 22h2 versions older ones too, packages were always removed correctly but when installed windows then used dism resetbase after that dism scanhealth was giving error 3. And in every each version to correct dism error 3 had to replace manually 4 files in winsxs from an untouched iso as dism couldn't fix it on its own. Always same files. I think there's something else going on, I have tested latest toolkit against several win 11 22h2 moment 3 and older versions too, packages were always removed correctly but when installed windows then used dism resetbase after that dism scanhealth was giving me error 3. And in every each version to correct dism error 3 had to replace manually 4 files in winsxs from an untouched iso as dism couldn't fix it on its own. Always same files.
Toolkit with function to make "AutoUnattend.xml", updated from 13.3 to 13.4. Please do the download again!
@MSMG, You can Optimize from these: Code: if "%ImageBuild%" geq "22621" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "22H2" /f >nul 2>&1 if "%ImageBuild%" equ "22622" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "22H2" /f >nul 2>&1 if "%ImageBuild%" equ "22623" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "22H2" /f >nul 2>&1 if "%ImageBuild%" equ "22624" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "22H2" /f >nul 2>&1 if "%ImageBuild%" equ "22631" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "22H2" /f >nul 2>&1 to: Code: if "%ImageBuild%" geq "22621" if "%ImageBuild%" leq "22631" Reg add "HKLM\TK_SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "TargetReleaseVersionInfo" /t REG_SZ /d "22H2" /f >nul 2>&1 and from: Code: if "%Tweak%" equ "DisableDownloadsLayout" ( Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "ColumnList" /t REG_SZ /d "prop:0(34)System.ItemNameDisplay;0System.DateModified;0System.ItemTypeText;0System.Size;1System.DateCreated;1System.Author;1System.Category;1System.Keywords;1System.Title" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "GroupAscending" /t REG_DWORD /d "0" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "GroupBy" /t REG_SZ /d "System.None" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "LogicalViewMode" /t REG_DWORD /d "1" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "Name" /t REG_SZ /d "NoName" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "Order" /t REG_DWORD /d "0" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "PrimaryProperty" /t REG_SZ /d "System.Name" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "SortByList" /t REG_SZ /d "prop:System.Name" /f >nul 2>&1 ) to: Code: if "%Tweak%" equ "DisableDownloadsLayout" ( Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "GroupBy" /t REG_SZ /d "System.None" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "PrimaryProperty" /t REG_SZ /d "System.Name" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "SortByList" /t REG_SZ /d "prop:System.Name" /f >nul 2>&1 ) These are default entries/values: Code: Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "ColumnList" /t REG_SZ /d "prop:0(34)System.ItemNameDisplay;0System.DateModified;0System.ItemTypeText;0System.Size;1System.DateCreated;1System.Author;1System.Category;1System.Keywords;1System.Title" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "GroupAscending" /t REG_DWORD /d "0" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "LogicalViewMode" /t REG_DWORD /d "1" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "Name" /t REG_SZ /d "NoName" /f >nul 2>&1 Reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderTypes\{885a186e-a440-4ada-812b-db871b942259}\TopViews\{00000000-0000-0000-0000-000000000000}" /v "Order" /t REG_DWORD /d "0" /f >nul 2>&1
V13.4 supports 22631? Great... Removing client cbs, shellexperience, startmenu, undockdevkit ... breaks my windows ... lol I think it's experimental features, shouldnt use those if u dont know what are those components to windows os... and @MSMG already said so.. so it's ur decision and ur own risk
Have uploaded updated Toolkit.cmd and ToolKitHelper.exe to support these patch Tuesday builds : Windows 10 Client v1809 (v10.0.17763.1/v10.0.17763.4377 [KB5026362]) Windows 10 Client Enterprise LTSC 2019 (v10.0.17763.1/v10.0.17763.4377 [KB5026362]) Windows 10 Client v1903 (v10.0.18362.1) & v1903/v1909 (v10.0.1836x.2274 [KB5013945]) Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2/v22H2 (v10.0.1904x.2965 [KB5026361]) Windows 10 Client Enterprise LTSC 2021 (v10.0.19044.1288/v10.0.19044.2965 [KB5026361]) Windows 11 Client v21H2 (v10.0.22000.1/v10.0.22000.1936 [KB5026368]) Windows 11 Client v22H2 (v10.0.22621.1/v10.0.2262x.1702 [KB5026372])
What I'm referring to is that each ToolKit version is updated to work with source images integrated with specific patch Tuesday updates, using the Toolkit to remove component with unsupported source images will result in SFC/DISM errors. The error you are referring to is different related to applying DISM /StartComponentCleanup with/without /ResetBase. Can you specify the 4 files needed to fix the error related to image clean-up.
Although it's supported but I haven't added the support yet as there are component changes in the build 10.0.22621.1778 and later which needs to be fixed. It will take time for adding support for 22631 may be two more patch Tuesdays builds need to come.