Follows the fixed "ConvertReg.ps1" file; I was able to find the error that did not convert CurrentControlSet to ControlSet001. from Code: "[HKEY_LOCAL_MACHINE\TK_SYSTEM\CurrentControlSet\" = "[HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001\"; "[-HKEY_LOCAL_MACHINE\TK_SYSTEM\CurrentControlSet\" = "[-HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001\"; to Code: "[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet" = "[HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001"; "[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet" = "[-HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001"; "[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001" = "[HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001"; "[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001" = "[-HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001"; I also put a redundancy for you to be working with some registry file that has already been converted to use with Toolkit. No more problem described above, which doubles the header and removes all keys. The original "ConvertReg.ps1" file is present in the "Toolkit_v11.8.7z". If you need to recover it from there. So just extract "ConvertReg.zip" inside the ".\Toolkit\Bin" folder and replace. EDIT: Extract "ToolkitREGsConverter.zip" inside the ".\Toolkit" folder.
What is ClientWebExperience from RemovePkgsList_W11_10.0.22000.txt ? And what corresponds to it in the window for selecting components for manual removal via the toolkit helper ?
Widgets. But to remove manually via Toolkithelper command you have to use "ClientWebExperience". Widgets only through the menu.
Clientwebexperience is giving error and the only one, it does everyone when it arrives in it, the message in the toolkithelper the rest goes well
Removing the below things will remove the non win32 stuffs, the rest is upto you to decide which one is required. - System Apps (Except AADBrokerPlugin - needed for Microsoft Account, Windows Store Client - needed for Microsoft DCH drivers) - Windows Apps
I'm using AMD Ryzen 5 3600 6-Core Processor 3.60 GHz with UEFI + TPM20 with modified Windows 11 (10.0.22483.1011) image and it's working fine, lets see what changes they will make in future builds.
Make this changes to Toolkit.cmd to revert back to old thing. from Code: PowerShell -Executionpolicy Bypass -File "%Bin%\ConvertReg.ps1" "%CustomRegistry%" "%Temp%\CustomRegistry" PowerShell -Executionpolicy Bypass -File "%Bin%\ConvertReg.ps1" "%CustomRegistry%" "%Temp%\CustomRegistry" to Code: PowerShell -Executionpolicy Bypass -File "%Bin%\ConvertReg.ps1" "%CustomRegistry%" "%Temp%\CustomRegistry"
Though the double conversion fixes the CurrentControlSet thing but it removes the registry paths totally, need to workout with the ConvertReg.ps1
Reduce the path length of the Toolkit folder to avoid this error, the app folder can't be deleted even from command prompt if the path is too long.
MSMG, Thank you for answering all my questions and suggestions. About Windows.Client.ShellComponents - I saw this component in NTLite in the FOD components section, and I was a little confused by this name, that is, I just didn't guess right away. what Windows.Client.ShellComponents is the Windows Feature Experience Pack ) Thank you again!
@olris Try renaming the toolkit folder to just toolkit or msmg or w/e - one simple word with no non-letter symbols or numbers.
Is it possible remove Windows Defender in definitive mode with this project? it also corrupts the .exe files with false positives. it's really terrible Windows Defender.
@MSMG , I use Windows 11 Insider Preview Build 22483, I try run toolkit, I see: 正在读取主机操作系统信息…… (Dev) - v10.0..1011 x64 or (rs_prerelease) Dev (v10.0..1011) x64 In Build 22483, wmic not support.so, Windows Version and Build detect method maybe get change further.
Yes you can but starting with Windows 10 v1903, the MS uses a new update format which restores the removed components when the system is updated offline or online.
Will check, if it's feasible to get the proper output then will it's better to keep it simple like Windows 11 (10.0.22483.1000) x64 en-US Windows Server 2022 (10.0.20348.1) x64 en-US