The Toolkit uses the Image info from DISM /Get-WimInfo and when the mounted image is updated with a new update, until you commit the changes to the image the DISM will not update the Image info. The ToolkitHelper reads the Image info from the registry and so it gets the info instantly, now I have made changes to the Toolkit script to read the info from registry when updates are integrated.
The ToolkitHelper checks for the existence of component folder/file name, if present it will continue with the removal but any new files/keys added by the update will be leftover.
Should I skip Cleanup (6 > 1) step from my below method? 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)
Yes the current method needs the ToolkitHelper to be updated for newer CU's if there are changes to the removed components in the new CU. Will check with the LTSC x64 build, may be resetbase is breaking the OS.
Yes the .NET Framework should be integrated after the image cleanup since it won't allow the clean if integrated earlier.
@MSMG If I am on 1809, how can I block the Updates to 1909. I'd like to receive only Updates Security and continue with version 1809..!! It is possible..?? Thanks in advance..!!
[G] Disable Automatic Windows Upgrade Code: Reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "DeferUpdatePeriod" /t REG_DWORD /d "0" /f Reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "DeferUpgrade" /t REG_DWORD /d "1" /f Reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "DeferUpgradePeriod" /t REG_DWORD /d "1" /f Reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v "AUOptions" /t REG_DWORD /d "2" /f
Do you also need... Code: REG add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /f /v TargetReleaseVersion /t REG_DWORD /d 1 REG add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /f /v TargetReleaseVersionInfo /t REG_SZ /d "1809" to stop upgrades to later versions? I have them set on all PCs here, but I use WSUS so I don't know if they work.
Hi there MSMG, first of all i would like to thank you for your amazing tool..... Maaan, i've been using your tool sinze 2017 and it's awesome MSMG Roooooooooooocks............................. I gotta say, i love you "not in a gay way" For the recent CU update for 1809, 1909, or 2004 (x64 version) Should I skip Cleanup (6 > 1) process to avoid getting sfc error or should i follow the instruction in the readme based on the windows version? Or Does the skip cleanup only applied for x86 version of windows 10? Thanks mate
Hi, On tools/WIM manager/Delete i try to enter a range [2-11] but it says its "invalid" and it doesnt accept any range in this format. Is there a way to avoid deleting one by one? Thanks