but in that case, one shouldn't integrate any Windows updates. it's best to just remove the bloatware, then use the DISM Command to integrate the .NET Framework 3.5, then install the latest Windows updates manually right?
Testing updated .NETFX47 Pack (Windows 7) for MSMG ToolKit and so the delay, it will be released soon.
Yes, I have created Microsoft Windows 7 Games Pack and will be releasing it soon for user testing to check for any bugs, then I will add it to the ToolKit.
yep exactly, I always works so and no issues using Windows 10 Education x64 Build 15063.rs2_release.170317-1834
What makes you lean towards MSMG being the cause? What exactly did you do with MSMG to your install what maybe have caused it?
I noticed that if you use MSMG Toolkit to update the official image without removing anything, then removing certain components will result in errors, such as several Defender components. I assume it happens because MSMG Toolkit seeks to remove the 15063.0 versions of the component, but after ResetBase, the version of that component changes to 15063.332 or newer, which confuses MSMG Toolkit. However, I find that doing all the removal first, followed by ResetBase, and only then updating the image, works better than the other way around. In my trials, no components that were removed from the original image came back after updating the image afterwards!
Yes the Recent change in CU updates the Image ServicePackBuild version and breaks the ToolKit function if the image is pre-integrated with the CU. I have fixed this problem for only .NET Framework Integration as we need to Integrate it at the last stage. The Best thing is to Integrate the Features + CU and then Remove packages. Integrating CU afterwards just restores few resources files of the removed components but doesn't bring back the component. As MS keeps changing it's update method and so the ToolKit too will have to be changed.
Yes! Would love to see the change log ahead of the release to decide whether to wait or get the job done now .
I had no problem with the original, and I do not update. With MSMG I deleted most of the components and my registry tweak works with other PCs (but no 4K monitor), otherwise I disable Fast Startup (ramdisk) may be that it comes from there.