As part of the Ventoy-Power Ultimate Boot Disk II package, I have added an illustrated MSMG Toolkit Guide that addresses some of the recurring configuration and usage issues raised in this forum. I am still awaiting MSMG's review of the guide. In the meantime, other users' comments, feedback and corrections are welcome.
I remember having a similar problem when I disabled Action Center (Notification Center) in Windows 11.
If you weren't successful in making the downloads through the Store I would have a suggestion. But in this case, I don't know what happens. So we have to wait for the MSMG, to see if he has any ideas on that error. For now you can create your iso using, within the Customize Menu, the Option EnableFeatures by list. Inside the lists folder, the template file is only one, you must put the options you want to disable and the ones you want to enable, in the correct files (EnableFeatures and DisableFeatures).
Does removing ShellExperienceHost and similar items breaks Start Menu or did MSMG Toolkit author find a way to remove such components without breaking the Start Menu?
Guys, it's been a while (a few days) that the MSMG hasn't visited the topic. He always takes time off after releases. After all, he is very busy. So I'm going to provide a "Toolkit.cmd" with the correction I sent him. I just revised it, to send it right to you, since the AutoUnattend part was a suggestion of mine that was getting bug feedback over the days, since the 9th of June. I also took the liberty of disabling the automatic selection of some new components when using the "select all" option in some menus. Also, along with newly added components, WindowsDefender and WindowsUpdate. These components are the ones that cause the most problems for beginners. So, it will make people pay attention to these components, and consciously decide to remove them. Along with "Toolkit.cmd", also a version, for those who want to test without using "Start.cmd" or "Toolkit_Start.cmd" scripts. "Toolkit_TESTING.cmd" can be run directly. Note 1: if you don't want to test, simply use "Start.cmd" or "Toolkit_Start.cmd" will run "Toolkit.cmd", not "Toolkit_TESTING.cmd". Note 2: Both versions are similar, just with the only change in script startup mode. This change "in script startup mode" was made to know if those using disabled UAC would still continue to have problems with "component removal", "access denied" errors, etc. In this modification, even running as administrator or with UAC disabled, nSudo is still executed. Previously this did not happen. And, therefore, the availability of the Toolkit without "Start.cmd" was discontinued at that time. Please bring your testimonial if it worked well or if you had problems. Although I am making this TESTING version available. The main focus I am making available is the fix for creating the Autounattend.xml file. In which, I removed all settings that could potentially cause problems in the future. Note 3: Keep a copy of your Toolkit.cmd. And extract the zip package in the Toolkit folder. EDIT: Updated Pack
You didn't say if it's your everyday installation that's having problems or if it's some VM testing. If testing on VM, discard this. Create a new one. Now back to what I read in the logs... Your system is corrupted (you already know that). And, from the errors, I assume that when using the Toolkit, you provided an ISO, which had already been modified, or you used an ISO not supported by the Toolkit, to make the ISO that you installed there. Try making a fresh ISO using one of the builds that are supported and avoid using ApplyMenu option 1 "DISM Cleanup-Image /ResetBase". Do an In-Place Update to recover your system. I've also seen problems related to identifying the UID of partitions. Perhaps there is partition table or file system corruption. You have to pass a checkdisk "chkdsk C: /x /f" to see if there is a problem. If it's GPT partition, checking EFI partition is good. And when doing a clean install, recreating the EFI is essential. If that doesn't work, you'll need to do a clean install. Is it possible to recover? Yes, it is possible. But you will waste more time than if you do a clean install. I could be very wrong. The logs have things like MountUUP mount points which are from abbodi scripts that have nothing to do with the Toolkit, you should know what you were doing and what that folder means, I assume you used it to try a "DISM. exe /English /Online /Cleanup-Image /RestoreHealth /source:"InstallMediaPath" /LimitAccess". So considering what I said, only you can decide which way to go.
Hello and Thanks! That version fixes the error when installing image with AutoUnattend, right? Also, is configuring password and username beforehand in AutoUnnatend necessary when CloudExpHost removed? Or I can do that in install process?
Read this: Then you need to specify at least the username. If you don't remove CloudExperienceHost and you create autounattend without specifying username. You must be prompted during installation. Give a try. This got me thinking of another improvement... But it should not affect the operation, it will only reduce the User's interaction with the function of creating autounattend. After all, if you don't create a user, why ask for a password? Am I right?
Hi @inTerActionVRI did you know if removing WiFi Network Manager (WiFi Sense) cause issues in a laptop? Like not connecting to a Wireless network Just asking due the unavailability to test in a laptop, I keep this component due the fact I don't know if could cause some issues.
I use a laptop on a daily basis. I always remove it, never had any problems. Disabling ActionCenter (NotificationCenter) "this is a registry tweak" causes problems with displaying taskbar functions. Wifi, VolumeControl, clock none of them show their functions when clicked. I don't know if the removal of ClientCBS or some other component is related.
I forgot to say that before proceeding with the mount, if the image is not supported this message will appear. The one I sent yesterday was without color, but the message is present I posted today's update in the previous post. In the link below. https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1286#post-1794123
@inTerActionVRI I also have a question: Which Windows edition is more preferred to be customized in MSMG: IoT LTSC 21H2 or Pro 21H2? As far as I know, in LTSC a lot of things such as MS Store, OneDrive and etc. are disabled and not removed, which means these things are hidden in registry and not completely removed in the way MSMG Toolkit does. So, when applying removal tweaks in Toolkit on IoT LTSC image the toolkit skips a lot of things cause it sees that these are not being present in the image cause these things are disabled already. And when doing removal on Pro, it sees that everything is enabled and it removes them the right way instead of skipping. Am I right? Or even when applying on LTSC it removes even though it skips components which Toolkit considers not being present in the image cause it were disabled? (sorry for my english, I'm not a native)
Just my 2 cents worth...I always disable notifcationcenter and I've never had a problem with taskbar/system tray icons/functions. But I've never tried to remove clientCBS either Disabling the ClipSvc will break those functions.
Following inTerActionVRI's MSMG Toolkit fix, I have updated the Ventoy-Power Ultimate Boot Disk II package to address the changes in MSMG Toolkit version 13.4 and also improve the graphical user interface of the guide. Going forward, updates will only occur when major new features are added to MSMG Toolkit and will be posted in this thread. As always, users' comments, feedback and corrections are welcome.
Hello. It is your Ventoy version? I thought default Ventoy supports booting from ISOs made in MSMG. I never had any problems booting my custom ISO from Ventoy. Can you explain for what exactly your version is intended?
I had and have this problem until today, only in windows 11, in builds 22000 and 22621 to 22631. It's best to leave Notification Center enabled. Could it be something particular to the ISOs in pt-BR? I don't know. It's up to test.