Understanding Installed Package/Update Discrepancies

E

ErikM

New Member
Good afternoon,

I hope one of you can help me understand an issue that has been occurring for me for quite a while about cumulative updates. The latest example occurred during this month's patch cycle and finally drove me to post here, looking for clarity. KB5032190 is at the heart of this issue as I have integrated it into my Windows 11 22H2 Operating System WIM. This was confirmed via a DISM /Get-Packages command, which shows "Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.2715.1.16" as installed. Unfortunately, when I image an endpoint with this WIM and visit Microsoft Update to confirm all is current, "2023-11 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5032190)" promptly appears as a newly installed quality update. Does anyone know if I am missing a step that is causing Microsoft Update to consider this update as not existing? This problem will continue to repeat itself month after month until I find the missing step.

Thank you,
Erik
 
Are you saying WU isn't recognizing the existence of an installed update? Or WU is asking you to re-install an existing update?

There's many reasons for the latter case, usually if any updates conflict by overwriting some shared components. A later check will reveal they need to be restored (by re-applying the latest CU which bundles them). Maybe a copy of your preset (after removing any user passwords or license key) can help explain the situation.
 
You must log in or register to reply here.
Back
Top