I spent the whole month in testing, integrating the recent updates (for W11 22621.1) from MS... Along with removing components via the ToolkitHelper Method (Menus or Lists)... Every week I was waiting for something to be fixed by MS in the next update. But I believe it was a premeditated change. For me, the last one that worked was the update to 22621.2283. All others 2359 2361 2428 2500, if I try to remove any component, the start menu, taskbar and settings are broken. Does this happen to everyone of you too? If so, we have to wait for the release of MSMG. Note: All tests were performed on a VM.
Found an easy way to disable windows 11 22h2 updates, if you like me like to keep ms store and dont want to perm remove windows update services just disable it for as long as you want without any sfc /scannow errors because of you will get error if you sc delete waasmedic. go to system32 find WaasMedicSvc.dll go to Properties security security tab, advanced change owner to yourself then go back and remove permissions for Trusted installer. open autoruns as admin type update uncheck BITS Usosvc wuauserv Dosvc also disable delete everything uso wuauserv from taskscheduler, no more updates or autoupdates. if you need to download something from store then again autoruns and mark back BITS Dosvc wuauserv install whatever you need then disable bits etc the same goes for updates
its not very clear to me.. when you mention i selected C.? so you saying theres is a way for me to removed winsat but tooklkit has some sort of fail safe so that way you wont remove a component that will break something else.. and that is option C..?? UPDATE ok i now see a option C compatibility wich i can remove and it allows mwe to remove winsat =kernel debugger ect..
right i also manually update in windows store for apps that are installed and i do not use mcst account either.. thanks
im only saying that if something is marked as * down where you mark windows components for removal you should go back from remove windows components and select option C there you can mark or unmark things that are later blocked or not in option select windows components for removal.
Use [C] Compatibility Menu option. Check it in Remove Menu or Remove Components Menu. EDIT: Have you ever found... It's all right then!
Hi, I'm having a bit of a "philosophical" problem I'm using MSMG Toolkit to customize one of the latest Windows 10 versions obtained via "UUP Dump". I'm not giving any specifics because I want to keep this message short and maybe expose it fully later if I get someone's help on the matter. The point is: I am doing a massive removal but, as an example of recent results I'm getting, let me just speak of one "thing" -- I am removing Windows Defender except Firewall. Well... when I load my initial ISO image, the script tells me I have to use DISM method to remove packages. So I follow this advice, and remove a bunch of packages relateds to Defender. Resulting ISO is fine, but I find A LOT of references in Windows registry about, say, SecurityHealth, and there's a menu left for that functionality, a taskbar icon, etcetera. Now... I repat the whole process but when removing Defender I use ToolkitHelper method instead. Resulting ISO is bigger BUT there's not a single instance of SecurityHealth in the registry. Also, no menu or icon residuals left. Can someone help me understand what's going on? What method should I use then? And... what are ToolkitHelper's changes done to the registry? Could I just apply them via registry patch after to removing packages via DISM - which maybe would give me the best of both worlds result? Thanks for any help you can provide. If someone is interested in helping me further I can give a more detailed explanation with every change made -- and they are A LOT.
inTerActionVRI, ''...Does this happen to everyone of you too?'' I have a similar situation) Therefore, I’m looking forward to the new version of this tool...
when integrating drivers what is the difference to place them in boot/recovery or installation media.?
@raptorddd You just need to add special drivers to your installed image. There is almost no need to add special hardware drivers to setup boot image or create a recovery image unless your PC needs, say, a SCSI, SAS or other special hardware driver in order to boot or start up. In a recovery or boot environment a PC mainly needs mouse, keyboard, monitor and hard drive access and most modern versions of Windows provide that out of the box.
to simple disbale windows update, just disabled USOSVC ( or Update Orchestrator Service) you still can update app from MS store, but you cant update your windows.
Just a supplement of information: Autoruns is part of the SysinternalsSuite that was acquired by MS a long time ago.
You have to provide a supported ISO to not get the "Not supported" message. To do this, just create a UUP dump ISO without integrating updates. You will get an ISO 19041.1 then you add the updates through the Toolkit and use the methods provided through the ToolkitHelper. Or an ISO with exactly the supported updates 1904x.xxxx, described in the ChangeLogs.txt file. The ToolkitHelper Methods are: by ToolkiHelper list and the method through the 8 sub-menus (Remove Components Menu). So, they only work for supported ISOs. Yes, anything related to the removed Component should also be removed. But there must be workarounds to keep other dependencies functioning.