I had removed support for TH2 long back and retain TH1 only for LTSB 2015 Branch as some people were still using it. But starting from v7.0 even support for TH1 will be removed too.
Probably mount install.wim, then edit the registry. Code: [HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\Explorer] "DisableNotificationCenter"=dword:00000001
Updated the ToolKit to v6.9 Changelog v6.9 + Updated ToolKit's Bin Folder with Windows 10 Redstone 2 WADK (v10.0.15052.0) Tools. + Added a Verification Check for the Feature "Extract Source from DVD ISO Image" to Verify Extraction. + Added a Verification Check for the Feature "Extract Source from OEM IMG Image" to Verify Extraction. + Fixed a Bug in the Feature "Remove Windows Components", Where the Remove Advanced Windows Components Menu was not Working for Windows Server 2016 Source OS. + Fixed a Bug in the Feature "Apply Source", Where the WIM Image Component Clean-up was Wrongly Applied to Windows 7/Server 2008 R2/ThinPC Source OS. + Updated the Feature "Format USB Flash Drive", with Improved USB Flash Drive Checking (Thanks to MDL Member: Psylow).
@MSMG Thanks for the new version of your utility. Nevertheless, I ask you to answer my question. The integrity violations is important, IMHO.
I know from experience by using this MSMG toolkit for a long time that if you remove certain components such as Biometrics, parental controls, etc, then sfc/scannow will ALWAYS find corrupt files and repair them, it has been like this for a long time I have found this only applies to the more in depth components such as biometrics that are more "woven" into the os, if you leave it and only remove basic features and apps, sfc /scannow will report no integrity violations!
Yep, I completely agree. 1) A complete list of such components is required. 2) Option to choose when removing such components. For example: Biometrics. Remove - "Microsoft-Windows-BioEnrollment-Base-Package" - "Microsoft-OneCore-Biometrics-Fingerprint-Package" - "Microsoft-OneCore-Biometrics-FaceRecognition-onecore-Package" - "Microsoft-OneCore-Biometrics-FaceRecognition-windows-Package" - "Microsoft-OneCore-Biometrics-FaceRecognition-Package" - "Microsoft-OneCore-Biometrics-onecore-Package" - "Microsoft-OneCore-Biometrics-WOW64-onecore-Package" - "Microsoft-OneCore-Biometrics-Package" - "Microsoft-OneCore-Biometrics-WOW64-Package" The folder and services for managing biometric data remain. But everything is easily turned off after installing the image (and blocked by the system, if necessary). Parental Controls. Remove the packages of this component, which collects the (spy) data. - "Microsoft-Windows-ParentalControls-OneCoreUapShell-Package" - "Microsoft-Windows-ParentalControls-Shell-Package" - "Microsoft-Windows-ParentalControls-Package"
Can't confirm this; neither related to the tool nor the biometrics packages you mention . Have removed Telemetry, Search/Cortana, Xbox, Geolocation, Biometrics, Alljoyn and Miracast with absolutely no sfc error at all. After installing 4 big CUs still the only sfc errors i get are related to the Win 8.1 WMC, which confuses the store. Additionally i was able to reinstall the packages (i exported prior to the removal) with TI elevated dism.
With ToolKit-V6.9 has been resolved the problem to enter cumulative updates on Windows 10 Enterprise LTSB v1607 ?
What problem do you refer to? I was able to integrate cumltv. updates fine on Windows 10 Enterprise LTSB v1607.
Sorry, that my answer took so long . sfc /scannow found some errors. In the attachment is the log file. It would be nice if you take a look at it.
Log states that some files regarding Bio.Enrollment and ParentalControl got repaired. Recommend to run the command again to see if those actually got repaired. Must commit i never saw any need to remove those, might be a dependencies conlict .
This is my experience with build 15063 1) MSMG 6.9 works well on this build, it removes all metro apps and associations, enables dotnet, integrates classic calc. (but complains a bit about missing index 2 wim) 2) Setup looks much nicer, But has to be launched via CMD, as booting only shows repair options (because of missing wim index), but PC works great after setup is completed! MSMG you rock!