Need some help here. Windows 10 2004 Removing Windows Components Requires Cumulative Update specified in the changelog.txt to be integrated before the removal. The problem is i dont see this update specified in changelog.txt inside toolkit folder. How can i know what update to integrate? This is driving me crazy.
Don't think DISM.exe allows parallel processing using same Wim file and moreover the script a dos batch file which executes line by line. But in DISMAPi there's something called session for each DISM operation, right now in the DISMAPi based Tool I'm working on I have added only single index servicing at a time, will check with the option multi-index parallel processing.
I don't have a WMR device to troubleshoot the issue you are facing, only with trail and error you can test which component is breaking the WMR. Only component Cortana shares some of it's files and registry setting with WMR, you can try retaining Cortana.
Selecting the parent component will automatically select it's child components. Selecting Windows Defender in System Apps will auto select Security Center in System since the Security Center is dependent on Windows Defender.
See the changelog to know the supported source image For Windows 10 Client v2004/v20H2/v21H1 you can use either KB5004237 or KB5004296 For Windows 10 Client v2004/v20H2/v21H1/v21H2 you can use KB5004296 Will add the CU KBID from next version. Code: + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809 (v10.0.17763.2061) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1903/v1909 (v10.0.18362.1679/v10.0.18363.1679) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004/v20H2/v21H1 (v10.0.19041.1110/v10.0.19042.1110/v10.0.19043.1110) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004/v20H2/v21H1/v21H2 (v10.0.19041.1151/v10.0.19042.1151/v10.0.19043.1151/v10.0.19044.1151) Source OS.
But some other tool like DISM++ allow parallel processing using same wim but this doesn't have api/command to use.
DISM++ doesn't use DISM.exe, DISMApi.dll or DISMCore.dll instead it uses CBS which is another Windows internal way of servicing images. May be CBS also have session to use the Wim image.
Dear @MSMG, I tried resetting the non-removable state on the latest Win11 (10.0.22000.132) build, but still can't remove SecHealthUI_8wekyb3d8bbwe package: Code: Dism /Image:C:\MSMG\Mount\Install\1 /Set-NonRemovableAppPolicy /PackageFamily:Microsoft.SecHealthUI_8wekyb3d8bbwe /NonRemovable:0 Deployment Image Servicing and Management tool Version: 10.0.22000.1 Image Version: 10.0.22000.132 The operation completed successfully. Code: Dism /Image:C:\MSMG\Mount\Install\1 /Set-NonRemovableAppPolicy /PackageFamily:Microsoft.SecHealthUI_8wekyb3d8bbwe /NonRemovable:0 Deployment Image Servicing and Management tool Version: 10.0.22000.1 Image Version: 10.0.22000.132 Error: 15610 Removal failed. Please contact your software vendor. From "C:\Windows\Logs\DISM\dism.log": Code: 2021-08-18 12:11:54, Info DISM DISM Appx Provider: PID=12696 TID=992 packagename='Microsoft.SecHealthUI_1000.22000.1.0_neutral__8wekyb3d8bbwe' - CAppxManager::ProcessCommandRemoveAllUserAppx 2021-08-18 12:11:54, Error DISM DISM Appx Provider: PID=12696 TID=992 Failed to uninstall becuase policy prevents the removal of this package - CAppxManager::RemoveAllUserAppx(hr:0x80073cfa) 2021-08-18 12:11:54, Error DISM DISM Appx Provider: PID=12696 TID=992 Failed to remove package 'Microsoft.SecHealthUI_1000.22000.1.0_neutral__8wekyb3d8bbwe' - CAppxManager::ProcessCommandRemoveAllUserAppx(hr:0x80073cfa) 2021-08-18 12:11:54, Error DISM DISM Appx Provider: PID=12696 TID=992 Failed processing command to remove Appx package - CAppxManager::ExecuteCmdLine(hr:0x80073cfa) How can we remove it, any ideas? Thanks for your amazing ToolKit! P.S. Other ProvisionedAppxPackages (e.g. Microsoft.WindowsTerminal_2021.226.1915.0_neutral_~_8wekyb3d8bbwe, etc...) can be removed normally.