"Component Removal requires a source image with supported cumulative update integrated" and if isos from uupdump don't have it which do?
@Benzinjiq Code: + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1809 (v10.0.17763.1/v10.0.17763.4737 [KB5029247]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client Enterprise LTSC 2019 (v10.0.17763.1/v10.0.17763.4737 [KB5029247]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v1903 (v10.0.18362.1) & v1903/v1909 (v10.0.1836x.2274 [KB5013945]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client v2004 (v10.0.19041.1) & v2004/v20H2/v21H1/v21H2/v22H2 (v10.0.1904x.3324 [KB5029244]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 10 Client Enterprise LTSC 2021 (v10.0.19044.1288/v10.0.19044.3324 [KB5029244]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v21H2 (v10.0.22000.1/v10.0.22000.2295 [KB5029253]) Source OS. + Updated the Feature "Remove Windows Component" to support Windows 11 Client v22H2 (v10.0.22621.1/v10.0.2262x.2134 [KB5029263]) Source OS. This is what I meant.
Having issue with appx dependancies: - I have noticed that despite Toolkit.cmd having a code to specify appx + dependencies (i.e. UIXaml28_Appx, VCLibs14_Appx, etc), deps almost never installed.. (Though already installed ones seemed to get updated = VCLibs14_Appx, etc) ~ Is it supposed to be like that? Example: (Toolkit_v13.6, Windows10 (19045.2965.230505-1139.22h2)) 1. \Packs\Apps\w10: contains updates versions of appx and their dependencies (from store.rg-adguard.net) 2. used: [2] Integrate: [5] Windows Inbox Apps: [1] Select Windows Apps [+ some] [2] Start Integrating Windows Apps = this will indeed integrate / update existing appx + deps that are installed - also updated.. BUT it appears that none of dependencies that are not installed were actually integrated.. - since "[1] Select Windows Apps" does not have an option to select them => I end up having to do manual integration of deps (croped batch i use): call :AddProvisionedAppxPackage "%InstallMount%" "UIXaml20_Appx" "%UIXaml20_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "UIXaml24_Appx" "%UIXaml24_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "UIXaml27_Appx" "%UIXaml27_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "UIXaml28_Appx" "%UIXaml28_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "VCLibs14_Appx" "%VCLibs14_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "VCLibsUWPDesktop14_Appx" "%VCLibsUWPDesktop14_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "NETNativeFramework22_Appx" "%NETNativeFramework22_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "NETNativeRuntime17_Appx" "%NETNativeRuntime17_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "NETNativeFramework22_Appx" "%NETNativeFramework22_Appx%" "" /SkipLicense call :AddProvisionedAppxPackage "%InstallMount%" "NETNativeRuntime22_Appx" "%NETNativeRuntime22_Appx%" "" /SkipLicense %DISM% /Image:"%InstallMount%" /Get-ProvisionedAppxPackages > Get-ProvisionedAppxPackages2.txt ----- Also x86 license file "Bin\AppLicense\Microsoft.D3DMappingLayers_8wekyb3d8bbwe.x86.xml" is missing (even though seemed to install without one)..
This may have been asked in some thread, but I'll ask anyway. When trying to remove apps, some of them have an asterisk (*) instead of the + sign. Can someone explain what it means. Thanks
Same here, I couldn't get it to work either. I tried this, but I got the same result as @GreenGremlin got. I'm in no hurry, though
@jahike I've not had any issues integrating the additional codecs. I've done it without a license (/skiplicense) and with one (these are available in the toolkit folder). The toolkit was using .appx file, but Microsoft changed to using .appxbundle and MSMG hadn't updated the toolkit to use all .appxbundle. I modified my script to handle those I had downloaded as .appxbundle files, which is what @inTerActionVRI was referring to. You need to codec file, the vclibs dependency and optionally a license. file. @inTerActionVRI recommends using both the x86 and x64 vclib dependency file, but I typically only use the x64 and I've never had a problem. The .appxbundle files are architecture neutral. This assumes everything is in the current folder. Spoiler: Using both VClibs dependency files DISM.exe /Online /Add-ProvisionedAppxPackage /PackagePath:Microsoft.HEVCVideoExtension_2.0.61931.0_neutral__8wekyb3d8bbwe.appxbundle /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.32530.0_x64__8wekyb3d8bbwe.Appx /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.32530.0_x86__8wekyb3d8bbwe.Appx /skiplicense Looking at the 13.6 script it appears everything has been changed to .appxbundle, so if you have .appx files (apart from the vclibs), you will need to download the latest .appxbundle files from store.rg-adguard. If using the script to integrate into the currently edited image put the files in the tookits packsp\apps\w10 folder (or w11 if using Windows 11)> Spoiler: Codecs integrated C:\Users\Tanya>dism /online /get-provisionedappxpackages Deployment Image Servicing and Management tool Version: 10.0.19041.844 Logging is disabled: Unable to obtain access to the log file C:\Windows\Logs\DISM\dism.log. Image Version: 10.0.19044.3208 Getting the list of app packages (.appx or .appxbundle) in this image... DisplayName : Microsoft.HEIFImageExtension Version : 1.0.61171.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.HEIFImageExtension_1.0.61171.0_neutral_~_8wekyb3d8bbwe Regions : DisplayName : Microsoft.HEVCVideoExtension Version : 2.0.61931.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.HEVCVideoExtension_2.0.61931.0_neutral_~_8wekyb3d8bbwe Regions : DisplayName : Microsoft.MPEG2VideoExtension Version : 1.0.50901.0 Architecture : x64 ResourceId : PackageName : Microsoft.MPEG2VideoExtension_1.0.50901.0_x64__8wekyb3d8bbwe Regions : DisplayName : Microsoft.VP9VideoExtensions Version : 1.0.61591.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.VP9VideoExtensions_1.0.61591.0_neutral_~_8wekyb3d8bbwe Regions : DisplayName : Microsoft.WebMediaExtensions Version : 1.0.61591.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.WebMediaExtensions_1.0.61591.0_neutral_~_8wekyb3d8bbwe Regions : DisplayName : Microsoft.WebpImageExtension Version : 1.0.62011.0 Architecture : neutral ResourceId : ~ PackageName : Microsoft.WebpImageExtension_1.0.62011.0_neutral_~_8wekyb3d8bbwe Regions : DisplayName : NVIDIACorp.NVIDIAControlPanel Version : 8.1.964.0 Architecture : x64 ResourceId : PackageName : NVIDIACorp.NVIDIAControlPanel_8.1.964.0_x64__56jybvy8sckqj Regions : all DisplayName : RealtekSemiconductorCorp.RealtekAudioControl Version : 1.44.302.0 Architecture : neutral ResourceId : ~ PackageName : RealtekSemiconductorCorp.RealtekAudioControl_1.44.302.0_neutral_~_dt26b99r8h8gj Regions : The operation completed successfully.
Hey @Yanta, Pardon if asked previously, from where I can get the vclibs dependency & license file ? Kind Regards
It's about the MSMG Toolkit. When removing apps from within the Toolkit, you have the + and - symbols to the right of the page, so when removing an app it changes to the - symbol, but some apps have an asterisk (*) symbol, so no matter how many times you try to remove the app, the asterisk remains. However, This happens only with the latest 13.6 version. The previous version does not have that problem. So I am guessing it's a bug on the latest version.
Oh, ok, so you already have the files. Then ignore what I said about downloading them. The dism command was showing how to integrate them into an online system. If you're using the toolkit to integrate them you don't need the dism. You have me there. I have the same issue. I don't see the VP9 codec in Apps & Features, yet when I use DISM /online /get-provisionedappxpackages it shows that it is installed. I am using 21H2 19044.3324 LTSC. So what do you see if you run dism /online /get-provisionedappxpackages from an elevated command line?
MSMG merged the w10 and w11 UWP app folders. Now the w10 folder is used for both Windows 10 and Windows 11 ISOs. Look at his message below.
It means they are blocked from removal so you can keep some functionality. When someone wants to remove it, it is believed that the person knows what they are doing. To unlock use the option Compatibility Menu.