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.
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])
Thank u so much...no need to rush..., personally im just a simple person, what u did is already more than enough for me... v13.4 is more than i expected.. u are a genius... I dont need the newest windows 11, im happy with the old windows 11 build.. The newest the build, the more complex it is, the more CPU, RAM, and Process needed... it become slower and heavy.. Life is to be enjoyed, not to be bothered with un needed things... Enjoy ur day.. சாந்தியும் அல்லாஹ்வின் அருளும், ஆசீர்வாதமும் உங்கள் மீது உண்டாவதாக
hi MSMG folder and 3 files located in amd64_dual_tsprint.inf_31bf3856ad364e35_10.0.22621.1_none_b9191cbed895f871 likely just one was corrupted not even sure what was corrupted but when i manually replaced those 4 files with ones from an untouched iso DISM ScanHealth error produced by DISM /StartComponentCleanup / ResetBase was fixed permanently. DISM /RestoreHealth no matter how i used it didn't want to fix those files. as to sfc/scannow it too produced error related to btmodem as far as i remember but on every iso i used it always fixed that error on its own.
dual_tsprint.inf is related to Remote Desktop Server, will check out and see if anything needs to be fixed.