MSMG ToolKit

@MSMG I made a change about adding the Administrator Account. I went to test it, because it's been a while since I've tested it, and adding multiple accounts isn't working.

In this case I removed the option and made other corrections. In the AutoUnattend block.
I changed some details in the Language Fallback scheme.
Because if it becomes empty, removing the initial empty space will add "~1" as a value in the variable.

I like the change in the "Installation Notes" part and make the IMCK Changes to "Unattended". In IMCK I keep the :AutoUnattendXML outfile block as it is. Thnks!

Follow the new file.

 

Hi @DennyAmaro,

Thank you for your feedback.

I never integrate updates, I find it pointless we you get 2 updates a month these days.
All I did was using the component removal option and adding the Registry tweaks.
Never faced any issues doing the same for Windows 10, though that is an entirely different system.

So after removing the components, applying the registry tweaks, saving the image, installing the system, the first thing I tried was to use the Momentum 3 update (KB026446) from the .msu file (preparation for the update, when it extracts the files, takes way longer than for Windows 10!), and it failed.
I went online, tried Windows Update, failed again.
Then I also tried the online update for May, failed again.
CBS.logs were 100-400 MB each time, which is insane amount of data, a lot of complaints about components not being accessible.
And of course, no (terminating) errors were encountered for an untouched image.

Is there anything special required for Windows 11 after components have been removed?
Honestly, I am not aware, but things should not be over complicated in any case.

 

Hi @tempdrive1 about Windows 11, is not complicated and is basically like Windows 10 except for the difference between applications names and new features in the system. Maybe you could share your "preset" (Things you remove) so we can better assist you. But, keep in mind that MSMG toolkit has everything detailed and the team behind or the developer behind @MSMG try to provide all the possible informations for every component available in the toolkit.

Also you're using only MSMG toolkit? or you use MSMG and them another software, like NTLite?

 

Maybe if you share the registry tweaks that you apply we can check what is happening and better understanding the scenario you're facing. And if has a bug inside a registry tweak we can simply provide to you and them send to @MSMG to update in the next version of the toolkit.

 

@DennyAmaro,

I know this toolkit since 2019 or so, and I have been reading many of the posts here since.
I don't use other tools (I played around with NTLite many years ago) and I don't use Registry tweaks which are not part of the toolkit for creating the image.
I never use anything but what is listed as selectable in the menus for removal, and I never integrate updates.
I usually create once modified image, test it quickly, and (re-)use it as a base until I need to move to a new major version.
Started with 1803 (very-very easy-to-manage and stable system), which I was able to update until the very last release (05/2021), and only after that I moved on straight to 21H1, and now stuck with 21H2 "forever", so I have been using the toolkit a little more lately.
Nothing special was done, really, I was initially doing the same thing like for Windows 10: remove all the components listed in the remove menu, except for Windows Update, AppresolverUX and Notepad.
Works fine for Windows 10, did not work for Windows 11.
So, when installation of the .msu failed, I created another image, this time skipping everything that sounded to complex or had a dependency or was listed as being a dependency.
So pretty much Firewall, Linux Subsystem, Edge, Speech Recognition, Game Explorer, Narrator, System Backup, Windows Update etc. were kept, but even so, it did not work.
I had time for 4 tries as I had to hand over the (low effort) work, and for the 3rd try I only went for selecting everything from [8] Windows Apps.
This was the only success I managed to have, even though I did one more try after this, but it was unusable once again.
Registry Tweaks: from Customize menu, [8] Apply Tweaks, almost everything.
I specifically selected no drivers from online, and yet every driver was updated through Windows Update.

This is the base image I was using: en-us_windows_11_consumer_editions_version_22h2_updated_sep_2022_x64_dvd_f408dad5.iso, version 22621.525

I honestly don't think there was much room for errors, yet no major component could be removed for having a successful update installed afterwards.

Based on this experience, I would pretty much need to test it by removing each and every component individually to see which actually break the update behavior, and that is about 3-5 days of effort, creating 30+ images, deploying them, trying to update them.

 

Did you try with a more recent SO @tempdrive1 ? Microsoft update their ISO and also could fix your problem. I usually download ISOs from UUPdump and no issues

 

Well, technically speaking what we are doing here is not what they intend us to do by any means.
The untouched software is updatable, I was facing no issues at all with it, and that's what they are providing support for anyway.

I must assume that this system has more severe core differences beyond the new design, which seems to be affecting such in-depth customizations.
(To me it feels like it was developed by well-taught, but young, freshly out-of-school developers, who only used mobile phones or tables in their lives - you all know exactly which core features are missing compared to Windows 10.)
Honestly, I would be surprised if it would be better with any of the latest releases, assuming this is a solid base for how it should work, and I hardly think they are going to undo something like that rather than keeping it as a new baseline.
And it's not like it's the initial release (of Windows 11), so changes they did must be intentional and for their own (support related) benefits.
If, however, this is how it is going to work going forward, you will not be able to update your systems, or at least not in an easy way.
All of the errors that I was seeing when briefly checking on the logs were about missing system parts.
And unless they allow the system to have missing parts (which again contradicts the intended designed as per my guess), later releases will behave the same.

I will try to stay away from it, mostly because I do not need any of these new features, while everything is quite stable and predictable with Windows 10.
The task I was assigned has been completed, and the user knows very little about computers anyway, I just wanted to make the most out of it, but this is the system that was forced on a relatively new hardware, being the new standard.

I'm curious if anyone else is going face such issues.

If the rumored Windows 12, that should be released in about a year's time, is going to similar to this, it is not going to be a good situation for us.
One thing people tend to overlook whenever a "downgrade" surfaces is that the younger generations, who have no exposure to former experience, will have nothing to compare to, and believe it is as good as it gets, and as such there will always be users for it, no matter how terrible things get.

I appreciate the effort you put into helping me.

 

Hi @MSMG,

Thank you once again for your efforts.

My tests (for removing the suggested Registry COMPONENTS and WinSxS data) were based on the removal performed on a live system with and without ResetBase and checks prior trying to install an update.
As the updates failed every single time, these changes were not something that could be used by the general public, at least not this way.
I did not try applying the changes to the offline image yet, as it is more time consuming (trim, modify additionally, deploy, test), and I wanted to go backwards (if the changes applied to a live system work, try the same changes applied to the offline image - which you did).
Needless to say, the goal is to have enhancements without system breaking changes, especially for the main user base.
Untouched LCUs are not causing issues when using ResetBase, because the intended state of the system will be restored by the LCU, undoing (almost) all the work done by the Toolkit.

One thing you did not mention (or at least I could not figure out based on your reply) with regards to the modified LCU + ScanHealth test is whether the ScanHealth errors were terminating ones.
My initial problem was (to recap) that for system that resembles this approach (to prevent redeployment of the removed components) ScanHealth (called after LCU deployment + ResetBase) was aborted, which is not an acceptable behavior.
Did this happen during your test as well?

I will be doing the tests I have in mind and report back once done.
Nevertheless, I would be happy to assist you any way I can - I do have a lot of free time on my hands.

As for Windows 11, by "base image" I meant what I was using as a starting point/to build up on, not being the initial release.
And believe me, I was not expecting any issues, given how well things worked out for Windows 10 based on your efforts, yet that is all I was left with despite all my efforts to make it work unfortunately.
Could you perhaps give it a try as well by working with the same image version?
There should not be any compatibility issues.
Just remove a couple random components from every group that you see fit.
And once you installed the system, go for installing KB5026446 from .msu while being offline as a first, though trying Windows Update should result in the same.
I was facing issues on both virtual and real machines, however, there should not be any difference with regards to this issue at least.
For me it is not really a problem as I don't intended to use Windows 11 (now that 12 is also around the corner as a hopefully better alternative), but I think others could be impacted as well.

If you need me to redo this for Windows 11 and provide you log data (assuming you did not manage to reproduce the issue), do let me know.

 

which Component removes

Code:

Program Files\Windows Security\BrowserCore\BrowserCore.exe

?

 

Yes, it will only be true if user account name be defined.

If user remove this component we need to warn them to remember to make AutoUnattend.xml file.

 

On a couple of recent Windows 11 builds where I used Toolkit's package removal list instead of DISM, I have ended up with an unusual Windows sources folder: all nearly all the files have been replaced with a single file called "gatherthestate.exe". Any idea of what causes this behavior and how to avoid it?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.