@inTerActionVRI any idea how to solve this error ? Its not allowing me to change any optional features like enabling, disabling of optional features! Is it happening since i disabled windows updates while creating the debloated iso?
@ MSMG & @ inTerActionVRI I've developed an MSMG guide in html format I'd like you guys to take a look at before posting. Is there a way to PM it to you?
Does anyone know which option to keep in the msmg tool for Internet options in the control panel? I need that, I only have Network and Sharing. I tried several options but without success
I just help MSMG when I can and work in my custom project based on his project. This you should explain to him and inform here, in the thread, you had sent him a PM/DM. Thnx, imlost2!
MS store opens fine and just now installed camera and netflix app just for checking. Can I download those files offline and enable or disable those features via powershell or cmdline ?
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.