That's because the Toolkit's component removal program has been updated to 10.0.19041.487 and you are using the .508 image. Always use the image to which the Toolkit's component removal program has been updated to.
Excuse me, but this is not correct. Please, look at my original info: Win10 20H1 build 450 (MSMG) Then, after installation, I tryed to update using KB (*.msu) manually to build 508, to be sure the future updates will work for the created (debloated) image. If you update your MSMG (forgive me if I didn't say thanks for this great tool), then I'll try to create build 450 (not 508) anyway (again), to check if MANUAL update works.
Ok got it, you updated to .508 manually and the image you used was .450 but the Tool was updated to be used with .487
You mean, the new MSMG v10.5 should fix the described problem? If so, I ready to try. How about my question 2)? Thanks.
I think take test app is missing and the cortana should not stay on ltsc in the toolkit helper template I know that microsoft is not easy to follow every day makes windows with more bloatwares
Hi @MSMG, Does that mean you could fix the defender removal issue on x86, where the CU failed to integrate? Cheers.
@MSMG Tested v10.5 with 2004 and received SFC errors for both x86 and x64 images. Hopefully just need an updated for ToolKitHelper.exe. Please note that OOBE during setup is no longer functioning correctly, as the Do more across devices with activity history screen is not shown. Here is the screen I mean: Spoiler: Files used x86 ISO: 19041.450.200808-0726.VB_RELEASE_SVC_REFRESH_CLIENTENTERPRISE_VOL_X86FRE_EN-GB.ISO x86 SSU: windows10.0-kb4577266-x86_189fc04e250eee5113654f9b2b56a8ce9f764bfe.msu x86 CU: windows10.0-kb4571756-x86_32b08a98d6246f4e0186c74e0280a5c1518d883d.msu x64 ISO: 19041.450.200808-0726.VB_RELEASE_SVC_REFRESH_CLIENTENTERPRISE_VOL_X64FRE_EN-GB.ISO x64 SSU: windows10.0-kb4577266-x64_126987f629769e860cd7985371754db91685ea16.msu x64 CU: windows10.0-kb4571756-x64_66f7130a68dd9748511454436b3ffb61730d9775.msu Spoiler: Method Extract ISO (1 > 3) Select source (1 > 1) (also mount boot and recovery images) Integrate Win32 calculator (3 > 3 > C) Apply SSU and CU updates (3 > 4 > 2 > 1 > 4) Apply setup media update (3 > 4 > 2 > 2) Remove using RemovePkgsList.txt (4 > 3) Spoiler: RemovePkgsList.txt GameExplorer MapControl OneDrive PeopleExperienceHost RetailDemoContent SecureAssessmentBrowser SkypeORTC WindowsMixedReality XboxGameCallableUI 3DViewer AdvertisingXaml Alarms BingWeather Calculator Camera CommunicationsApps Cortana DesktopAppInstaller FeedbackHub GetHelp Getstarted HEIFImageExtension Maps MixedRealityPortal OfficeHub OfficeOneNote Paint3D People Photos ScreenSketch SkypeApp SolitaireCollection SoundRecorder StickyNotes VP9VideoExtensions WalletService WebMediaExtensions WebpImageExtensions WindowsStore XboxApp XboxIdentityProvider YourPhone ZuneMusic ZuneVideo Unpin all Start menu icons (5 > 6) Tweaks for Task View, App Downloads, Photo Viewer (5 > 8 > B/D/J) Cleanup (6 > 1) Apply changes to image (6 > 2 > Y) Rebuild (6 > 1) Convert WIM to ESD (2 > 4) Make ISO (7 > 1) Have attached CBS log files.
@MSMG Build 450, MSMG v10.5 : Still can't get manual cumulative updates working after debloating: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-820#post-1618911 Or I should dive deep into dependencies (check the services/packages/registry)? @ALL: Which packages I should include to make "Restore point" functional? (Interesting, that when I prepeared an image first time using MSMG Menu (UI), then "Restore point" worked, but when I started using the Lists, it's not...). Both times I keep "System Restore" package untouched. Hmm...
@MSMG I've been using 17763.1 for my base image, removing components and updating to a later CU before building the new image, per the readme.txt So, now that process is reversed? I MUST Integrate updates before I remove the components, and the CU MUST be 1457, no other? Otherwise package removal might fail? Just checking to be sure In 10.1 Readme it says Code: [F] - Remove all required Windows Components using [Remove->Remove Windows Components] menu. [G] - Integrate Windows Updates using [Integrate->Windows Updates->Windows Updates] menu. whereas 10.5 says Code: [E] - Integrate Windows Updates using [Integrate->Windows Updates->Windows Updates] menu. [G] - Remove all required Windows Components using [Remove->Remove Windows Components] menu.
@MSMG ,In ToolKit Integrate Menu,like the line 1287: :: Checking whether the selected Source OS is a Windows 10 v2004/v2009 32-Bit Client Edition It should be v20H2,not v2009.v2009 is not an official version.
As said earlier and yesterday, if are going to remove components using ToolkitHelper then you need use the image with a CU integrated for which the ToolkitHelper has been updated to. In v10.5 you need an image with a CU .508 as a base image to remove components and then it allows you to install or integrate the further updates. But if you use an image with CU lower or higher then .508 then it may break further updates installation. And regarding System Restore not working try retaining Windows Backup since both share some files and registry entries, will check and fix them in due time.
Checked with CBS logs, doesn't see errors related to removed components, can you confirm whether the error is due to component removal or is it with other tasks. Regarding Activity History screen not being shown it might be due to adding disable activity history in the Unified Telemetry Component, will check out and fix it.
Yes now for v1809, v1903/v1909, v2004/20H2 the steps are same, first integrate the update that the ToolKitHelper has been updated to support and then remove the components.