Not yet, is just support Windows 11 22H2. The latest version supported is Windows 11 22H2 22621.2134, you can check it the changelog in Toolkit v13.6
@ MarvelX7 The MSMG application wants you to put them in the ..\Custom\Registry folder. However I have found that rarely works because Windows won't install user registry tweaks until their desktop appears and that is long after MSMG is active. You can download my MSMG guide, unzip it, click the Versions.exe file and choose "Quick Start" for a rather detailed explaination of adding user tweaks to a clean install. Basically you need to create a \sources\$OEM$\$$\Setup\Scripts folder and REBOOT after MSMG setup completes in order to run custom registry scripts that install user tweaks. You can also use this method to re-install any saved custom Windows *.deskthemepack to setup your desktop appearance. Hope that helps.
It may well be. I just read multiple times in multiple places that it replaced the deprecated snipping tool. There was also snippingtool++, but that no longer works, then there was Gyazo, but that's now payware and really should be classified as "spyware". IIRC, there was also Greenshot. That too is no longer developed. If all else fails, WIn+Shift+S. (Which requires clipboard service and a few registry keys to be set so that it works).
Doesn't look like it. I get errors inside the Virtualbox session when I try doing a clean install with my modified ISO.
You have to wait for @MSMG to return the current Windows 11 22h2 and 23h2 isos, it is breaking when removing components, wait for it to return to update toolkit helper, the program responsible for removing components.
Since I deleted some components of LTSC2021, now I cannot start ‘Intel Driver & support assistant’ with error code 0xe0434352. Does anyone have experience with this?
Only works util update 2283. After that if you remove some component set with toolkihelper methods it will bring to you a Broken ISO. It doesn't matter if you use a supported ISO and integrate the Updates... Updates above 2283 if you use the toolkithelper methods for removal, this is breaking all the ISOs I made in my tests. I did a lot of removal combinations. Unsuccessfully. I tested it yesterday with the 2506, it broke too. I haven't yet tested just removing components via DISM, only this way people should be able to remove components without problems, but the number of components that can be removed is much smaller.
Hey @inTerActionVRI any idea why this error is occuring ? I am debloating 19045.3208 with autounattend. Attaching the removed pkg list
can I get an example of removing multiple components in one line? similar to ToolKitHelper C:\WORK\Mount EdgeChromium,OneDrive,ContentDeliveryManager,SecurityCenter
If I use the "Disable Windows 11 Installer Hardware Check" tweak and install this iso on a compatible PC who wouldn't need it, could it cause problems given the additions to the registry?? Tia
in the future there surely will be update, but why wait for a new version if current one is working ?
Maybe because for most people the current version just doesn't work?) If you know the correct sequence of how to clean Windows of the latest version 22621 or 22631 as much as possible without errors at the installation stage, I will be glad to hear. Because, personally, I have been waiting for the update for two month now, because no matter what options I try, there is always an error during installation.
I'll probably agree. Lately, only the numbers change from version to version. Let's say a copilot appeared at 22631... It seems that the benefit from this is no less than in slippery Android app support.
In light of my impressions and experiences so far, I have learned that using the base (xxxxx.1) version of the relevant Windows distribution instead of the latest Windows version that supports MSMG is the most effective and problem-free method (as possible). Also, the procedure I follow is what is written step-by-step in the current README.txt file, without ignoring the side notes. I think and hope friends with similar experiences will confirm me.