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.
@ All Please do run the ToolKit using the start.cmd and follow the instructions given in readme.txt file, this would solve most of the issues people are facing using the ToolKit. The data for ToolKitHelper.exe got mixed up while merging the code for RS3 and RS4 and I had to redo it, will release an update as soon as possible.
How do I restore homegroup on Windows 10 Enterprise LTSB 2016 when I removed it using MSMG Toolkit? @MSMG
You can't, you have to start over. I mean there MIGHT be a way with DISM but I'm no expert. I don't even know if it can be done without problems either. It'll be faster to redo it and not mess up. Also, homegroup is so dead that nobody on earth has used it in the last 20 years. Do it differently. It's been depreciated and isn't present in v1803+.
Hello everyone I am trying to update Windows 10 1709 VL with the latest CU update release May 21, 2018—KB4103714 (OS Build 16299.461). But getting the pending.xml when I try to cleanup the image. Using MSMG ToolKit 8.6 and started the script “Start” as normal with no Admin rights as advised. The steps I took are the following: 1. Added fr-FR language pack 2. Integrated CU KB4103714 (OS Build 16299.461) 3. Perform Cleanup 4. Apply changes and save to source image. 5. Re-mount source 6. Add .NET Framework 3.5 7. Perform Cleanup On Step 7 I get the pending.xml task message I didn’t remove anything other than add a language pack and Integrate the latest CU for Windows 10 1709. By the way I am using VL version of Windows 10 Enterprise.Can some one here tell me if I am doing anything wrong or missing something? I have another image with the same ISO of the Windows 10 1709 VL where I only Added the language pack and Added the .NET Framework 3.5 without no issues at all.
read the Readme file and follow the instructions carefully. there clearly stated the order of actions.