Good find. Yeah, as you mentioned, there are many other components that have regressed in version. Here are all the ones that have gone from ver .223 to in the older 3197356 to .206 in the newer 3194798. A few went to even older versions, as noted below: Spoiler amd64_microsoft.virtualiz..ent.rdpclientaxhost amd64_microsoft-onecore-coremessaging amd64_microsoft-windows-acluifilefoldertool amd64_microsoft-windows-b..ironment-dvd-efisys amd64_microsoft-windows-b..re-memorydiagnostic amd64_microsoft-windows-c..erymanager.appxmain amd64_microsoft-windows-c..xperiencehostbroker amd64_microsoft-windows-d..rvices-adprep-files amd64_microsoft-windows-data-pdf amd64_microsoft-windows-devices-bluetooth amd64_microsoft-windows-inputservice amd64_microsoft-windows-internal-bluetooth amd64_microsoft-windows-m..ation-mfmediaengine amd64_microsoft-windows-m..ents-mdac-oledb-dll amd64_microsoft-windows-p..installerandprintui amd64_microsoft-windows-printing-dialogs amd64_microsoft-windows-r..ckgroundmediaplayer amd64_microsoft-windows-s..l.onecore.resources amd64_microsoft-windows-s..ptionhandlersplugin amd64_microsoft-windows-s..s-datasensehandlers (.223 to .51) amd64_microsoft-windows-s..y-spp-plugin-common amd64_microsoft-windows-security-tokenbroker amd64_microsoft-windows-speechpal-desktop amd64_microsoft-windows-store-licensemanager amd64_microsoft-windows-w..for-management-core amd64_microsoft-windows-wifinetworkmanager (.223 to .187) amd64_microsoft-windows-windowscodec amd64_microsoft-windows-winsrv amd64_windows-media-speech-winrt msil_microsoft.powershel..nagement.activities (.223 to .187) msil_microsoft.powershel..orkflow.servicecore (.223 to .187) msil_microsoft.powershell.commands.utility msil_microsoft.powershell.gpowershell msil_microsoft.powershell.graphicalhost (.223 to .103) msil_microsoft.powershell.isecommon (.223 to .187) msil_microsoft.powershell.scheduledjob msil_microsoft.powershell.security.activities msil_microsoft.powershell.security msil_microsoft.updateservices.baseapi msil_microsoft.windows.f..anagement.plugin.ui msil_microsoft.windows.f..r.management.plugin msil_microsoft.wsman.management.activities (.223 to .67) msil_system.management.automation wow64_microsoft-onecore-coremessaging wow64_microsoft-windows-b..iagnostic.resources wow64_microsoft-windows-b..re-memorydiagnostic wow64_microsoft-windows-c..ovdatamodel-library wow64_microsoft-windows-coreuicomponents wow64_microsoft-windows-devices-bluetooth wow64_microsoft-windows-inputservice wow64_microsoft-windows-internal-bluetooth wow64_microsoft-windows-m..ation-mfmediaengine wow64_microsoft-windows-m..ents-mdac-oledb-dll wow64_microsoft-windows-p..installerandprintui wow64_microsoft-windows-printing-dialogs wow64_microsoft-windows-r..ckgroundmediaplayer wow64_microsoft-windows-security-tokenbroker wow64_microsoft-windows-store-licensemanager wow64_microsoft-windows-w..for-management-core wow64_microsoft-windows-windowscodec wow64_microsoft-windows-winsrv wow64_windows-media-speech-winrt x86_microsoft-windows-acluifilefoldertool x86_microsoft-windows-cpfilters x86_microsoft-windows-data-pdf And these were in the previous update, but are missing from the newer one (unless I missed them): Spoiler amd64_microsoft-windows-t..es-workspace-radcui x86_microsoft-windows-t..es-workspace-radcui msil_microsoft.wsman.management
Enthousiast: thanks for testing. I don't know about the install issues, but what 600412 said about older versions of components being in the new update is true. I'm sure MS will release a newer CU that fixes this soon (hopefully).
I did 2 tests and all went well, no errors installing any update after resetbase on .223. Not even on a .187 install, updated to .223 and resetbased, then installed .321.
[It seems the CUs released for preview or catalog only, are not fully migrated to the official patch tuesday CU
How can I uninstall the superseded servicing stack update? For an example, I previously installed KB3173428 in Windows 10 Version 1511. When KB3181403 was released, I installed KB3181403. But, KB3173428 is no longer shown in 'View Installed Updates'.
It's done by installing the new one, when you want to cleanup you could use this command (in an elevated CMD): Code: Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
I was refering to servicing stack updates, which have unique CBS name CU have the same name, thus only latest is shown Flash updates however, have the same display name, but the CBS name is unique per KB number
If I did not delete the line "delete permanence="permanent"" as mentioned in your method, I cannot use your script (the attachment) to uninstall superseded servicing stack update, right? View attachment Windows 10 Updates Uninstaller.txt Thank you very much for your advice.
What does this command -actually- do? Should I use it after integrating to an offline image and then installing windows?