[SOLVED] Number of Reclaimable Packages Stuck/won't clear out - Server 2012 R2 Standard

Please run the DISM /Online /Cleanup-Image /StartComponentCleanup command while ProcMon is running

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the DISM command .
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.

Edit:
Post the DISM log as well, so I have the timestamp when it fails.
 
Hi,

Open an elevated command prompt and run the following command. Attach Dirlist.txt to your next post.
Code:
dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.20475_none_fab32e54b4561e08 > "%userprofile%\Desktop\Dirlist.txt"
 
Could you please run DISM /Online /Cleanup-Image /StartComponentCleanup again with ProcMon running? And then attach the CBS log as well the DISM log, so we have the same timestamps to look at. For the time being, I couldn't find anything yet.
 
Hi,

Do you have a similar server with the same patch level? If so, please provide the COMPONENTS hive from that server.
 
Hey, I wanted to reach out with an update. The problem is now solved. I opened a case with Microsoft as a 2nd option. To be honest, I figured they'd cop out and tell me to reload the server (like the last three times), but in this case they actually stuck with it and helped get this issue squared away. In case it helps you kind folks (or perhaps other users), I'd like to share what we did to resolve the issue.

  1. Download this super secret report generator used by Microsoft: MSSetupReport.zip (see bottom for update, this may not be necessary anymore)
  2. Extract it, and rename setupreport.cmd.txt to setupreport.cmd, and then run it.
  3. Wait for the command to complete. It could take 10-20+ mins.
  4. On the desktop, extract, then inspect the resulting folder full of logs. In my case it was named Setup_Report_THALES_Mon08222022.zip
  5. Within the folder I found (amongst dozens of files that I didn't understand) THALES_Servicing_PackageState.txt. I opened it and saw the following info:
Code:
CBS servicing states, as seen on https://docs.microsoft.com/en-us/archive/blogs/tip_of_the_day/tip-of-the-day-cbs-servicing-states-chart-refresher
This will list any packages not in a state of 80 (superseded) or 112 (Installed)
If blank then none were found
--------------------------------------------------------------------------------------------------------

Cumulative/rollup package(s) in broken state                 
--------------------------------------------                 
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.19941.1.5
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20045.1.13
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20046.1.0
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20069.1.16
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20094.1.8
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20120.1.12
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20144.1.17
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20174.1.16
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20371.1.17
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20402.1.18
Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20478.1.13



Standalone package(s) in broken state                       
-------------------------------------                       
Package_for_KB3016437~31bf3856ad364e35~amd64~~6.3.1.0       
Package_for_KB5008263~31bf3856ad364e35~amd64~~9600.20207.1.9
Package_for_KB5009624~31bf3856ad364e35~amd64~~9600.20246.1.12
Package_for_KB5010419~31bf3856ad364e35~amd64~~9600.20269.1.8
Package_for_KB5011564~31bf3856ad364e35~amd64~~9600.20303.1.14
Package_for_KB5012670~31bf3856ad364e35~amd64~~9600.20337.1.23

For some reason, Microsoft specifically excluded Package_for_KB3016437~31bf3856ad364e35~amd64~~6.3.1.0 from the following commands. Not sure why. I guess it wasn't necessary?

We ran:
Code:
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.19941.1.5 ## This one didn't work, by the way. Maybe it's the one you and I already ripped out?
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20045.1.13
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20046.1.0
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20069.1.16
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20094.1.8
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20120.1.12
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20144.1.17
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20174.1.16
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20371.1.17
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20402.1.18
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.20478.1.13
dism /online /remove-package /packagename:Package_for_KB5012670~31bf3856ad364e35~amd64~~9600.20337.1.23
dism /online /remove-package /packagename:Package_for_KB5011564~31bf3856ad364e35~amd64~~9600.20303.1.14   
dism /online /remove-package /packagename:Package_for_KB5009624~31bf3856ad364e35~amd64~~9600.20246.1.12
dism /online /remove-package /packagename:Package_for_KB5010419~31bf3856ad364e35~amd64~~9600.20269.1.8
dism /online /remove-package /packagename:Package_for_KB5008263~31bf3856ad364e35~amd64~~9600.20207.1.9

Next, I rebooted the server and ran DISM /Online /Cleanup-Image /AnalyzeComponentStore. The number of reclaimable packages was 1! Next, I ran DISM /Online /Cleanup-Image /StartComponentCleanup, which completed successfully. The following execution of DISM /Online /Cleanup-Image /AnalyzeComponentStore reported 0 reclaimable packages. Nice.

I ran Windows Updates and they installed successfully. I ran DISM /Online /Cleanup-Image /RestoreHealth and got The restore operation completed successfully. The component store corruption was repaired.

Finally, SFC /SCANNOW reported Windows Resource Protection did not find any integrity violations.

UPDATE: Looks like the same information regarding staged packages can be obtained by running DISM /ONLINE /GET-PACKAGES /FORMAT:TABLE > KB.txt &&kb.txt instead of downloading that Microsoft report generator.
 
UPDATE: Looks like the same information regarding staged packages can be obtained by running DISM /ONLINE /GET-PACKAGES /FORMAT:TABLE > KB.txt &&kb.txt instead of downloading that Microsoft report generator.
I haven't downloaded or ran their tool yet but it seems that it just enumerates the Packages subkey and prints the packages where the CurrentState value is not installed or superseded. Thanks for sharing this though!
 
Hi,

Glad to hear you've managed to solve this problem, and thanks for sharing the solution, this is greatly appreciated... (y)
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top