Hello, @MSMG Here some mistakes typo: In line 11357 : Code: goto :IntDaRTBoot This labeled section is not found in Toolkit.cmd In line 18770 : Code: Code: if exist "%BootMount%\%%i\Windows\WinSxS\Backup\*.*" del /f /q "%InstallMount%\Windows\WinSxS\Backup\*.*" >nul 2>&1 Should be: Code: if exist "%BootMount%\%%i\Windows\WinSxS\Backup\*.*" del /f /q "%BootMount%\%%i\Windows\WinSxS\Backup\*.*" >nul 2>&1 In line 21166 : Code: Code: ImageIndexNo=Enter the WIM Image Index # ['Q'uit] : Should be: Code: set /p ImageIndexNo=Enter the WIM Image Index # ['Q'uit] : sorry for my bad English, I'm using google translate
By updates, do you mean any updates under the Windows Update section (like definition updates, .NET updates, monthly cumulative updates etc.) or only the major feature updates (like 1809, 2004, 2009)?
May be is not a bad idea include this into the cleanup scenario as a additional (hidden) step(s) that help to produce an image more clean? I beleive all such cleanings should help to reduce "user fingerprint" and improve privacy a little bit (do not save such data on disk forever for M$). I like every smallest step that help us to survive in the era of privacy leaks.
I was thinking we could make a separate open script that deals with empty folders and obsolete files for cleanup
Well, why not? But I thought about non-urgent collecting of the most sensitive cleanups with time flow inside the bundle (as a solid/approved/safe part of the bundle). 1. The most important thing for me is that all such initiatives must be approved by our own expert - @MSMG. Here I trust his decision: is it a good idea to make such edits for the image or not. Do not brake things - is a priority. Also I don't want to bother @MSMG unnecessarily, because he busy within much more important things (I'm expecting a new cool things in the near future). 2. I have my own CMD (still W.I.P.) for cleaning AFTER Windows installation. But I'm not an expert in prepearing of images. So, here I fully rely on our favorite bundle and his creator.
With Windows v1903 and above the Microsoft introduced a new update package format which will restore the removed components upon updating the system. Almost all components do get restored either in full or part, only Windows Apps are not affected since it gets updated through store. Window Store and Xbox which have backend files do get restored by Cumulative update.
Agree with you absolutely OK, But remove empty folders is bad idea. I tried to remove empty folders in entire install.wim. 'Cause it to breaks Windows setup.
Can someone tell me if Windows 10 Version 1607 Build 14393 is still supported by MSMG v11.0? Is removing components for Windows 10 Version 1607 Build 14393 supported by MSMG v11.0 and if so by what methods?
I am having trouble running assasin's creed valhalla. It's the only game that doesn't work on my win 10 mod (on full version works) My remove component's list: Spoiler: RemovePkgsList AdobeFlashForWindows EdgeChromium FirstLogonAnimation GameExplorer SnippingTool SpeechRecognition WinSAT AssignedAccess CEIP_SQM FaceRecognition KernelDebugging LocationService PicturePassword PinEnrollment UnifiedTelemetryClient WindowsErrorReporting WindowsInsiderHub HomeGroup MultiPointConnector RemoteAssistance DeviceLockdown EaseOfAccessThemes EasyTransfer Paint SecurityCenter StepsRecorder WindowsSubsystemForLinux WindowsToGo Wordpad AssignedAccessLockApp BioEnrollment CBSPreview ECApp EdgeDevToolsClient Edge FileExplorer LockApp MapControl NarratorQuickStart OneDrive ParentalControls PeopleExperienceHost QuickAssist RetailDemoContent SecureAssessmentBrowser SettingSync SkypeORTC SmartScreen Win32WebViewHost WindowsDefender WindowsMixedReality WindowsReaderPDF 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 YourPhone ZuneMusic ZuneVideo I have no idea what is missing.
Could be WinSAT, GameExplorer or both. GameExplorer and WinSAT are necessary for Microsoft Games, so we cannot discard it as a dependency for other games considering the connection between game producers with Microsoft. I suspect the influence of these components. if you want to test with AssignedAccessLockApp you have to keep AssignedAccess. SpeechRecognition I think it may be necessary for some games' features. FaceRecognition I also think that it may be necessary for features of some games that support virtual reality. I don't know if that is the case. if you want to test with KernelDebugging you have to keep WindowsErrorReporting LocationService required for some games. RemoteAssistance may be required as for Multiplayer game systems. You have to do some tests there. Prepare an iso without removing those components. Then you can make versions just by mounting and removing the components for testing.
*Almost all*?! Damn I didn't realize it was that bad haha. I use both MS Store and Xbox (for Forza and stuff), so that wouldn't be an issue. But almost all? Yeah that'd be pretty frustrating..
Can't do "Cleaning Up Source Images with Component Cleanup & ResetBase" After added .NET Framework 4.8 in Windows 10 LTSC 2019 / Windows Server 2019. I tried 2 ways to add .NET Framework 4.8. 1.Put Windows Update files in the path "\WHD\w10\x64\17763\NetCumulative" KB4486153 (Microsoft .NET Framework 4.8 on Windows 10 version 1709, Windows 10 version 1803, Windows 10 version 1809 and Windows Server 2019) KB4586877 (Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10, version 1809 and Windows Server, version 2019) The error shows: Cannot Perform Image Component Cleanup when Pending.xml is present... 2.Use MSMG Toolkit's pack. Microsoft-Windows-NetFX48-Package~31bf3856ad364e35~amd64~~10.0.16299.15.cab It works fine. Is that a bug of I do the wrong step? PS: I only know enable .NET Framework 3.5 would cause Pending.xml problem.
Check the order of installation in your first method, is it like below KB4486153 KB4586877 or KB4586877 KB4486153