It will be released tomorrow, it will be a minor update. Right now have uploaded just the ToolkitHelper.exe, you can use it to test the removal, I have only tested the removal with 64-bi images. Code: Name: ToolKitHelper.exe Size: 16230912 bytes (15 MB) SHA1: AFAF7FEEFCE3D62CCF24B89D2CF187FCC0EF0DF7
Updated the ToolKit to v11.0 Spoiler: Changelog v11.0 + Updated ToolKit's Bin folder with Windows 10 20H1 Insider Preview WADK (v10.0.20279.1) Tools. + Updated ToolKit's Bin folder with 7-zip v20.02 Command-line Binaries. + Updated ToolKit's Bin folder with NSudo v8.0.1.0 Binaries. + Updated ToolKit's Bin folder with WimLib-Imagex v1.13.3 Binaries. + Optimized the ToolKit code for "Select Source from DVD" (Thanks to MDL Member : RaiyvaN). + Updated the ToolKit to return to it's parent menu instead of Main menu at the end of each operation. + Added a Feature "Integrate Microsoft .NET 5". + Added the Microsoft .NET 5.0.1 Pack (Windows 10) for MSMG ToolKit. + Updated the Microsoft Edge Chromium Browser Pack for MSMG ToolKit with updated Microsoft Edge Chromium Group Policy Definitions files. + Updated the Microsoft Visual C++ Runtime Pack for MSMG ToolKit with VC++ 2019 v14.28.29617.0 Runtime (Thanks to MDL Member : abbodi1406). + Updated the Feature "Integrate WHD Updates" to support updated Feature Enablement Pack for Windows 10 Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809 (v10.0.17763.1637) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1903/v1909 (v10.0.18362.1256/v10.0.18363.1256) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004/v20H2 (v10.0.19041.685/v10.0.19042.685) Source OS. + Fixed Typo Errors (Thanks to MDL Members : RaiyvaN and 正义羊).
Since the component removal data is manually processed, it will be difficult for adding support for each insider preview builds.
Checked with v10.9 and it seems I do get the Pending.xml error - never noticed that before! is this a serious problem and how can I stop it from happening?
Indeed, it is better to have a pending flag than an SFC error. The pending flag is nothing to worry about, it just won't let you clean the image, and the final ISO size will be slightly larger, it's not critical when .wim is converted to .esd I am very grateful to you for this hint, which will save me from wasting time looking for solutions, since I myself have encountered exactly the same problem at the present time. I usually integrate only a few files to customize the appearance of the OS, and this did not cause any problems. But I needed to disable the automatic start of some Services, I integrated a few tweaks with CurrentControlSet using NTLite, and got an error during the installation phase that looked something like this: "Your PC was rebooted...."
Actually technically the 19042.685 MVS ISO would be best to use for being able to cleanup the image, the latest 20H2 ESDs and TB/MVS ISOs are made from a sysprepped 19042.572 install (iirc) and those won't have the 20H2 EP on "pending install" but "installed". But MSFT forgot to do some cleaning themselves, causing leftover installed drivers and other stuff. The UUP dump or manually updated image will have the 20H2 EP with "pending install", which prevents cleaning up. The cleanup, on the other hand, causes the ghost sfc errors (found errors and repaired by sfc /scannow but no record of it in cbs.log.
Thanks for your reply, one more question: Should I download the newer version that ends in .eappx or ignore the .eappx files? I'm thinking I should download both, for example: "Microsoft.DesktopAppInstaller_2020.1111.2238.0_neutral_~_8wekyb3d8bbwe.BlockMap 12.99 KB Microsoft.DesktopAppInstaller_2020.1111.2238.0_neutral_~_8wekyb3d8bbwe.appxbundle 9.55 MB Microsoft.DesktopAppInstaller_2020.1111.2238.70_neutral_~_8wekyb3d8bbwe.BlockMap 36.52 KB Microsoft.DesktopAppInstaller_2020.1111.2238.70_neutral_~_8wekyb3d8bbwe.eappxbundle 28.03 MB " I couldn't find any information regarding .eappxbundle, are these newer versions dependent on the standard .appxbundle? Can I safely ignore the standard older version ending in .appxbundle if a newer version is an .eappxbundle?, I read that these eappxbundles are encrypted, which is why I ask and I don't know if I need the older version when the newer one uses eappxbundle as part of a dependency. (Since you said I can safely ignore the older versions.) Thanks
bugs: -After selecting source i went to 7 -> 1 and now can't escape for there -When integrating WHD updates it doesn't check the respective folder, when need to move the subfolders out from 10.0.19041 (or similar) to the main folder (since builds don't change for non previews, the folder 10.0.19041 can be hardcoded into the path?)
Hi MSMG and Others Does anyone know what the difference is Old Feature Enablement Pack windows10.0-kb4562830-x64_816fd030691161bfc9f892f0e9e1259e23a56c82 New Feature Enablement Pack windows10.0-kb4562830-x64_93a5c65488affb6e73a0a48ad6a58d8bc1713fd7
