hallo i have a problem with msmg when i try to load a wim it asks to load boot and recovery i answer no and then it just stops also when i say yes it just quits anyone knows how to solve this??
Right, but, I need this system to be stable. So there's no reported bugs when handling windows LTSB is there? I checked the README and it didn't say anything about RS1 so I guess I'm safe but I want to make sure. I can always update later, right? I would love to see that package list...
Someone has done a list list of telemetry removals for each w10 build number. You still need a tool that does it though. If i was given a basic sample file i could build up my own batch file.
What is the last version of MSMG that I should use for 1709-RS3? I used 8.6 to create a new image with the latest patches but i fails after the first reboot saying "Windows cannot be installed on this computers hardware" or something like that.
To get home and pro to ltsb is a lot of work and there is a chance of bugs(no disrespect msmg, bugs happen). The only down side is ltsb is 1607 and not the latest build series with improvements. LTSB is slim out of the box, why dick around when you dont have too? My only 2 major bugbears with ltsb are one drive(solved by using melerix one drive uninstaller) and defender(disable services). Its still bloated AF with a ton of crap packages i remove.
NO dude if you have some knowledge or patience searching via Google or any other 2015/2016 LTSB builds no need CUT/Remove or something only need you use your BRAIN for my humble opinion MSMG Toolkit is used for a lot of builds with TONS of craps I hope that now you know how to things works here; still this is valid since launch of bad Windows 8 (NOT W 8.1) and today ALSO is valid for 1803 truste me
(Bold text above by me) You can report bugs/errors/concerns in the wumt wrapper script thread in my signature. Yep, my script causes errors when using sfc because UsoClient.exe, WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll, WaaSAssessment.dll, MusNotificationUx.exe, and SIHClient.exe have all permissions removed, so uninstall the wrapper script temporarily to restore those files default permissions before you run sfc, or at least be aware of this situation. I'll add this info to the next version's readme and make a note of this in the OP in my project's thread, so thanks. You can check for wrapper script caused sfc errors with this command in command prompt: Code: findstr /c:"[SR] Cannot" %windir%\logs\cbs\cbs.log|more The only errors you should see are with one or all of these files: UsoClient.exe, WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll, WaaSAssessment.dll, MusNotificationUx.exe, and SIHClient.exe More about that this sfc/wrapper script issue here. Also, just thought I'd mention that I upgraded 1709 to 1803 with UsoClient.exe, WaaSMedic.exe, MusNotificationUx.exe, and SIHClient.exe disabled with the wrapper script as a test (AFAIK 1709 doesn't have WaasMedicSvc.dll, WaaSMedicPS.dll, and WaaSAssessment.dll), and I had no problem at all and everything is working fine.
I had the same problem, could not integrate latest cu or it would fail had to remove things out of the image, install, and add the cu after the initial install!
Exactly, like i've said, it's useless to remove anything on TH1 and RS1 LTSB, the only thing that i can remove and i DON'T NEED MSMG is OneDrive.
yep bro this is correct for me is unecessary comment more nothing only think a little you know bro errr. sorry for some errors I'm a little problematic sorry in this moment
yep dude since long time still remember: our big Teacher is MSMG with original Toolkit in times of dangerous Windows 8 so for all users first anyone first need choose what them want to make right
Oh... I figured, as with 1703, once MSMG toolkit moves on tho the next release that it stops working for the previous release. Eg. v7.7 was the last version for 1703. So is this not the case? Ah well... It's only and extra 10 minutes per PC to do as you suggest.