@ 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.
What's the windows manual setup feature under the Remove Advanced Windows Components menu? Also I didn't install dotnet 4.7.1 on the computer I'm making this ISO on and MSMG toolkit is working fine... It's W10-RS4 so it came with 4.0 preinstalled. So I guess it doesn't need that specific version? Also: Will I mess anything up by applying the same option twice? Like rebuild source image or remove cortana? Also: xbox removal and some other stuff doesn't work... (from my previous install with dotnet 4.7.1 included)
Enabling dotnetfx3 (step 6 in your list) sets the pending flag, after that a cleanup can't be performed. There is also no need for step 4 and 5, doesn't do anything special to unmount and remount.
Thanks for the reply, So I could just do: 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 ( or just skip to Step 6 and do step 4 and 5? ) 6. Add .NET Framework 3.5 7. Step 4 and 5 8. Create my ISO
Thanks again for the reply, I have one last question... How do I correct that pending.xml warning or I just don't do the cleanup? And do Apply changes and save to source image.
Now you know what sets the pending flag (adding dotnet35) you can play with the order of doing stuff. It should be done after the cleanup.
I noticed this and I asked the same question here earlier, hoping that @MSMG would give an explanation. Using "diff" in Linux I recursively compared contents of two ISOs processed with NTLite using exactly the same settings. I found the differences were in Windows NT Registry hives. I binarily compared the respective files. I saw the differences but couldn't understand them because I don't know the specification of the registry file format. You probably noticed I said NTLite - not MSMG Toolkit. The size differences between outputs were smaller using NTLite so I rolled with that. You would have to repeat the same process for the Toolkit to see if it's just registry hives or more.
Intriguing. So there may well be something changed that I don't know about - more importantly, how does it effect the final result. It's attention to detail like mine that can help bring bugs and discrepancies to the surface. People should stop being so dismissive and accepting errors as normal.
I completely agree with you on deeper level. I feel exactly the same, it's like you took those words out of my mouth. At this point it's a relief to see there are other people who have extreme attention to detail and understand it's value and use, it's much too rare! It seems like tons of blatantly obvious bugs, errors, and design oversights go completely unacknowledged or dismissed entirely these days. Not to be rude to MSMG, the comment is a general one, aimed at a lot of different software. But yes, MSMG toolkit and part of it's design and use is included to a degree.