Most of the components do get restored, some fully and some partially, only the Windows Apps don't get restored.
The features list differ for each OS, you better get the list by the below command Code: Dism /Image:Mount\Install /Get-Features /Format:Table
Since you are referring to W10 v2004 and the component removal has not been added yet, may I know what changes you have done to the installation image and using which Tool?
Got this txt as answer : Spoiler: Features List [Table] -------------------------------------------- | ----------------------------- Feature Name | State -------------------------------------------- | ----------------------------- Printing-XPSServices-Features | Disabled MSRDC-Infrastructure | Disabled TelnetClient | Disabled TFTP | Disabled TIFFIFilter | Disabled LegacyComponents | Disabled DirectPlay | Disabled SimpleTCP | Disabled NetFx4Extended-ASPNET45 | Disabled WCF-HTTP-Activation45 | Disabled WCF-TCP-Activation45 | Disabled WCF-Pipe-Activation45 | Disabled WCF-MSMQ-Activation45 | Disabled WCF-TCP-PortSharing45 | Disabled IIS-WebServerRole | Disabled IIS-WebServer | Disabled IIS-CommonHttpFeatures | Disabled IIS-HttpErrors | Disabled IIS-HttpRedirect | Disabled IIS-ApplicationDevelopment | Disabled IIS-NetFxExtensibility | Disabled IIS-NetFxExtensibility45 | Disabled IIS-HealthAndDiagnostics | Disabled IIS-HttpLogging | Disabled IIS-LoggingLibraries | Disabled IIS-RequestMonitor | Disabled IIS-HttpTracing | Disabled IIS-Security | Disabled IIS-URLAuthorization | Disabled IIS-RequestFiltering | Disabled IIS-IPSecurity | Disabled IIS-Performance | Disabled IIS-HttpCompressionDynamic | Disabled IIS-WebServerManagementTools | Disabled IIS-ManagementScriptingTools | Disabled IIS-IIS6ManagementCompatibility | Disabled IIS-Metabase | Disabled WAS-WindowsActivationService | Disabled WAS-ProcessModel | Disabled WAS-NetFxEnvironment | Disabled WAS-ConfigurationAPI | Disabled IIS-HostableWebCore | Disabled WCF-HTTP-Activation | Disabled WCF-NonHTTP-Activation | Disabled IIS-StaticContent | Disabled IIS-DefaultDocument | Disabled IIS-DirectoryBrowsing | Disabled IIS-WebDAV | Disabled IIS-WebSockets | Disabled IIS-ApplicationInit | Disabled IIS-ASPNET | Disabled IIS-ASPNET45 | Disabled IIS-ASP | Disabled IIS-CGI | Disabled IIS-ISAPIExtensions | Disabled IIS-ISAPIFilter | Disabled IIS-ServerSideIncludes | Disabled IIS-CustomLogging | Disabled IIS-BasicAuthentication | Disabled IIS-HttpCompressionStatic | Disabled IIS-ManagementConsole | Disabled IIS-ManagementService | Disabled IIS-WMICompatibility | Disabled IIS-LegacyScripts | Disabled IIS-LegacySnapIn | Disabled IIS-FTPServer | Disabled IIS-FTPSvc | Disabled IIS-FTPExtensibility | Disabled MSMQ-Container | Disabled MSMQ-DCOMProxy | Disabled MSMQ-Server | Disabled MSMQ-ADIntegration | Disabled MSMQ-HTTP | Disabled MSMQ-Multicast | Disabled MSMQ-Triggers | Disabled IIS-CertProvider | Disabled IIS-WindowsAuthentication | Disabled IIS-DigestAuthentication | Disabled IIS-ClientCertificateMappingAuthentication | Disabled IIS-IISCertificateMappingAuthentication | Disabled IIS-ODBCLogging | Disabled NetFx3 | Disabled SMB1Protocol-Deprecation | Disabled MediaPlayback | Disabled DataCenterBridging | Disabled ServicesForNFS-ClientOnly | Disabled ClientForNFS-Infrastructure | Disabled NFS-Administration | Disabled SmbDirect | Disabled HostGuardian | Disabled MultiPoint-Connector | Disabled MultiPoint-Connector-Services | Disabled MultiPoint-Tools | Disabled Printing-Foundation-Features | Disabled FaxServicesClientPackage | Disabled Printing-Foundation-InternetPrinting-Client | Disabled Printing-Foundation-LPDPrintService | Disabled Printing-Foundation-LPRPortMonitor | Disabled Windows-Identity-Foundation | Disabled Client-EmbeddedBootExp | Disabled Client-EmbeddedLogon | Disabled Client-KeyboardFilter | Disabled Client-UnifiedWriteFilter | Disabled AppServerClient | Disabled Client-DeviceLockdown | Disabled Client-EmbeddedShellLauncher | Disabled SMB1Protocol | Disabled SMB1Protocol-Client | Disabled SMB1Protocol-Server | Disabled Windows-Defender-Default-Definitions | Disabled WorkFolders-Client | Disabled MicrosoftWindowsPowerShellV2Root | Disabled MicrosoftWindowsPowerShellV2 | Disabled Microsoft-Windows-Subsystem-Linux | Disabled Client-ProjFS | Disabled DirectoryServices-ADAM-Client | Disabled Containers | Disabled HypervisorPlatform | Disabled VirtualMachinePlatform | Disabled Containers-DisposableClientVM | Disabled Microsoft-Hyper-V-All | Disabled Microsoft-Hyper-V | Disabled Microsoft-Hyper-V-Tools-All | Disabled Microsoft-Hyper-V-Management-PowerShell | Disabled Microsoft-Hyper-V-Hypervisor | Disabled Microsoft-Hyper-V-Services | Disabled Microsoft-Hyper-V-Management-Clients | Disabled Windows-Defender-ApplicationGuard | Disabled All Features Shown Disabled
You need to copy the Feature Names from the list to the DisableFeaturesList.txt Use the below command to get the list entries for easier editing Code: Dism /Image:Mount\Install /Get-Features | findstr "Feature Name" Replace the text "Feature Name : " to BLANK in notepad and copy the entries. PS. don't enter the " or "
I made an image based on the 2004 version (19041.172) with several components and applications cut out. Installed the system, updated via Windows Update and delayed the receipt of future updates until January 2, 2024
Meanwhile I cannot update my image with the CU as it fails every time. Stuck on 18363.449. There must be a way to manually repair it, but all attempts have failed. Although I didn't try mounting my image offline to attempt repair like that. Running too low on motivation for that... I guess I will wait for 2004 update, I won't use component removal if it means they will return with each CU. App removal and disabling components gives a stable clean result. Although you can't disable a lot of the components with MSMG, only remove. Obviously some things can't be disabled, but I'm sure there are some more that can be to avoid the "restore on CU" problem. I hope at some point a feature is added to skip setup questions and select local install. Anything to streamline the install process. Especially when I cannot supervise the install (and some noob leaves the boxes ticked and puts in a microsoft account because they don't listen to instructions)!
Interesting. Do you try: - Other autounattend.xml file? - Do not use SetupComplete.cmd ? - Put to iso file boot.wim from older version ? Pozdrawiam i zdrowia zycze
1. Have full control over updates using That or That 2. Use DISM commands to repair WU for eg. Code: DISM /Online /Cleanup-Image /ScanHealth Code: DISM /Online /Cleanup-Image /RestoreHealth 3. Use Windows 10 Enterprise LTSC 2019 to get regular updates without returning removed components. Thanks. ...
- Try install the update using .msu or .cab file with DISM - Do integrate the latest CU and remove the components and then try in-place upgrade. Yes even for v2004 expect the Windows App all other removed components will be returned back. Try using unattend.xml to skip the setup questions and to use local account.
Updated the ToolKit to v9.7 Highlights: Windows 10 10.0.19592.1000 ADK Tools Windows 10 v1909 (v10.0.18363.753 ) removal support. Windows 10 v2004 (v10.0.19041.172 ) Windows Apps removal support. Spoiler: Changelog v9.7 + Updated ToolKit's Bin folder with Windows 10 20H1 Insider Preview WADK (v10.0.19592.1000) Tools. + Fixed bugs in the Integrate Windows Features Menu choice items. + Updated the Feature "Integrate WHD Updates" to Reflect the WHD Hotfix Repository Update List. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1909 (v10.0.18363.753) Source OS. + Updated the Feature "Remove Windows Component" to support removing Windows Apps for Windows 10 Client v2004 (v10.0.19041.172) Source OS. + Fixed Typo Errors and Optimized ToolKit Code (Thanks to MDL Member Kenafri). Note: I have moved the Store, Xbox and Xbox Identity Provider Apps to Windows Apps section and split Windows Apps category as Windows Apps-1 and Windows Apps-2. Removing All Windows Apps in Windows Apps-1 menu will also remove the apps in Windows Apps-2 too.
@MSMG Thank you again for your hard work. This will help with my boredom later, as I can test with latest 1909 and perhaps 20H1.
Yes don't integrate any packs just remove components and try the image as the log reports some file/folder permissions are set twice.