MSMG ToolKit

Component Store integrity helps to have better compatibility with Windows Update.

What does not make sense to me is to remove components and want to use Windows Update since several files need to be kept in the WinSxS folder for this and Microsoft can change what it wants in the OS with future updates and undo the tweaks you made including returning the components removed.

If you want to continue to have support from Microsoft including updates better use official tools and methods to tweak your Windows.

 

In your post here... https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-840#post-1624586 you listed a total of 44 packages (22 base and 22 language specific). Here you list 6 + 6 packages, and the /Add-Package command lists only 12 as well. So I don't need to convert the other 16/32 to cabs?

Sweet. So I can remove the other 16/32. Lol, Well it was fun writing the script

I understand. I wasn't meaning to push you. I know you're very busy and other factors influence your time on this project. When you get time is fine. Don't drop more important things for me.

Perhaps someone else can chime in?

@Ace2, do you know how to do this part?

 

I tried 19041.208 with the latest ToolKit and everything went fine, I don't think the 20H2 image was the problem, also I don't want to use 572 update because it has a lot of issues. I'll try next version of ToolKit and see if it works, if not then I'll rather stay with my current 2004 ISO that I made months ago.

 

This is interesting. I have 10 1809 LTSC systems (because 1809 is supported for 10 years and there is nothing in 1903+ of any compelling need, plus removed components get restored).

Many of these PCs have Adobe products installed but the only product that refuses to install is Acrobat DC Pro. Pretty much everything in the CC suite has no issues. But we don't have licenses for Acrobat DC Pro so we just use the free reader, which also installs fine.

But I do agree sooner or later you have to upgrade. I really didn't want to move off Windows 7 but with ESU support being so expensive on top of existing licenses and subscriptions it is getting to the point where people need to win the lotto just to keep up

 

You need to login to view this posts content.

 

toolkit worked allways.
until windows 20H2
i get missing driver during installation
dono what causes this

 

Understood.

I want to test one idea - keep full set of stock GPO files (.ADMX + .ADML) in the OS, in spite of removed components in the ISO. E.g.:
1) Manually copy (restore) all stock policy files back after OS installation
2) Restore a backup of GPO presets using LGPO.exe commands

This way, expected benefits when you have "ready to go" presets backup of all necessary GPO:

- Protected OS settings, even when unwanted (missed) components will come back with CU = No leaks or unwanted consequences of unexpected enabling
- Much easier to control : easy to transfer COMPLETE SET of GPO presets from old OS version to the new one; adding a new policy presets is also much easier
- No dependence on removed/installed components in the ISO - the full set of GPO presets should work for any config
- Always fast and predictable results if you need reinstall or update OS : "set and forget"

This idea in simple words : Limited set of ISO Components, but full set of GPO presets (full policy protection).

------------------------
Question: is there a way to quickly extract .ADMX + .ADML from any ISO without installing stock OS?
Path: C:\Windows\PolicyDefinitions\
I guess I should use mount ISO commands for that?

 

@MSMG, suggestions:

It may be interesting to set to remove components that will no longer work after removing a dependency.

For example: if you remove Windows Defender, then also remove SmartScreen and Windows Store. If you remove SmartScreen, then remove Windows Store.

That way you will have a functional system. And, I believe that, when the user notices something missing, he would identify it through his list of removed components.

Or even add a question:
When removing this component the following components will be removed. Do you wish to continue? - answer 'Y'es or 'N'o

Or, instead of a question, it becomes more dynamic to inform in the menu, instead of the dependencies, what will be removed.

Edit:
So, as @ingviowarr commented, this could also be that way.
If 'Y'es - When removing this component the following components will be removed. If 'N'o - The component dependencies wil remain. To continue answer 'Y'es or 'N'o

 

@RaiyvaN
Not a bad idea in general. But I'd prefer keep Store | Defender+SmartScreen as a separated things.
Just to have more flexibility (anyway I don't need all of these).
In spite of dependecies, the Store may appear semi/functional when Defender+SmartScreen are absent (need to be tested online to be sure).
As I can remember, I didn't have errors relative to missed Defender+SmartScreen during my offline tests in the past (errors were here due to missed online licensing).

To say short, Store chain behavior may differ:
- If you have SmartScreen installed, but disabled/blocked, there will be error (Prompt to Enable SmartScreen)
- If you have SmartScreen removed completely (and Defender, as well), then no such prompt/error

 

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.

 

Are the google drive and cloudmail sites up to date to download the packs?, thanks

 

yep here I remove all 3 components and NO issues with sfc / scannow

 

I will download a second iso and continue torturing myself until the weekend is over

 

MCT iso is not serviceable, it has an install.esd. You would need to convert the install.esd to install.wim for MSMG to be able to service it.

 

yes i got warning about this and did convert it inside toolkit

 

FYI: To check system files without fixing them (scan only):

Code:

sfc /verifyonly