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

Maxstar · Aug 22, 2022

You can check the Task Manager or using Process Explorer to see if there is still running a CMD command.

soj4trade · Aug 23, 2022

Code:

C:\Windows\system32>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 1

Incorrect function.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Logs are attached below!

CBS.zip

Maxstar · Aug 24, 2022

Hi,

Upload your COMPONENTS hive.

Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

soj4trade · Aug 24, 2022

Thanks for your patience! Busy morning. Here's the COMPONENTS file!

COMPONENTS.zip

Maxstar · Aug 24, 2022

Hi,

No problem at all, please run the ComponentsScanner on this server and post the result.

Download

ComponentsScanner and save it to your desktop.

Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
Follow the on-screen instructions.
Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
Post the logfile ComponentsScanner.txt as attachment into your next reply.

soj4trade · Aug 24, 2022

Here ya go!

Maxstar · Aug 25, 2022

Rich (BB code):

2022-08-23 06:07:10, Error                 CSI    000001c0 (F) E_UNEXPECTED #12598327# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_UninstallDeployment(Flags = 0, a = 76e3200e6b9aa2b158863c37a07b8315, Version = 6.3.9600.18786, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, cb = (null), s = (null), rid = [83]"Package_1490_for_KB4601384~31bf3856ad364e35~amd64~~6.3.1.5.4601384-2487_neutral_GDR", disp = 0)[gle=0x8000ffff]
2022-08-23 06:07:10, Info                  CBS    Failed to begin deployment uninstallation for Update: 4601384-2487_neutral_GDR [HRESULT = 0x8000ffff - E_UNEXPECTED]
2022-08-23 06:07:10, Info                  CBS    Failed to execute item[0] in Package: Package_1490_for_KB4601384~31bf3856ad364e35~amd64~~6.3.1.5, Update: 4601384-2487_neutral_GDR [HRESULT = 0x8000ffff - E_UNEXPECTED]
2022-08-23 06:07:10, Info                  CBS    Failed to execute execution update. [HRESULT = 0x8000ffff - E_UNEXPECTED]
2022-08-23 06:07:10, Info                  CBS    Failed to execute execution package: Package_1490_for_KB4601384~31bf3856ad364e35~amd64~~6.3.1.5 [HRESULT = 0x8000ffff - E_UNEXPECTED]
2022-08-23 06:07:10, Info                  CBS    Failed to prepare execution. [HRESULT = 0x8000ffff - E_UNEXPECTED]
2022-08-23 06:07:10, Info                  CBS    Failed to process component watch list. [HRESULT = 0x8000ffff - E_UNEXPECTED]

2022-08-23 05:57:34, Info                  CBS    Exec: Unproject package: Package_1490_for_KB4601384~31bf3856ad364e35~amd64~~6.3.1.5, Update: 4601384-2487_neutral_GDR
2022-08-23 05:57:34, Info                  CBS    Exec: Unprojecting Package: Package_1490_for_KB4601384~31bf3856ad364e35~amd64~~6.3.1.5, Update: 4601384-2487_neutral_GDR, UninstallDeployment: amd64_76e3200e6b9aa2b158863c37a07b8315_31bf3856ad364e35_6.3.9600.18786_none_e65f26c2c1498255
2022-08-23 05:57:34, Error                 CSI    000001be (F) Assembly installed and uninstalled with same reference in single transaction (id = @0xaf177713d0, guid = {d16d444c-56d8-11d5-882d-0080c847b195}, ref = [83]"Package_1490_for_KB4601384~31bf3856ad364e35~amd64~~6.3.1.5.4601384-2487_neutral_GDR")
[gle=0x80004005]
2022-08-23 05:57:34, Error                 CSI    000001bf@2022/8/23:09:57:34.998 (F) base\wcp\servicingapi\assembly.cpp(727): Error E_UNEXPECTED originated in function Windows::ServicingAPI::CAssembly::AddUninstall expression: ((HRESULT)0x8000FFFFL)
[gle=0x80004005]

Hi,

Please check if KB4601384 is installed and if you can remove this update.

Code:

wmic qfe | find "KB4601384"
wusa /uninstall /KB:4601384

soj4trade · Aug 25, 2022

Believe it or not, that patch doesn't seem to be installed.

Code:

PS C:\Windows\system32> Get-Hotfix -id KB4601384
Get-Hotfix : Cannot find the requested hotfix on the 'localhost' computer.
Verify the input and run the command again.
At line:1 char:1
+ Get-Hotfix -id KB4601384
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (:) [Get-HotFix], ArgumentExcept
   ion
    + FullyQualifiedErrorId : GetHotFixNoEntriesFound,Microsoft.PowerShell.Com
   mands.GetHotFixCommand

Code:

C:\Windows\system32>wmic qfe | find "KB4601384"

C:\Windows\system32>

Should I install it?

Maxstar · Aug 25, 2022

Please perform a REG search with FRST for this update.

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Open the startmenu and type the command cmd.
After you find the Command Prompt, right click on it and select Run as Administrator.
Copy and paste the following into the Command Prompt and press enter.

Code:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

Right-click on the file FRST64.exe and choose Run as administrator.

Copy and paste the following (code) into the Search box and click the Search Registry button.

Code:

KB4601384

When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
Post the logfile SearchReg.txt as attachment in your next reply.

soj4trade · Aug 25, 2022

Code:

C:\Windows\system32>reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONEN
TS
The operation completed successfully.

Here's that text file!

Maxstar · Aug 25, 2022

Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

Download the attachment fixlist.txt and save it to your desktop.
Right-click on FRST.exe and select "Run as administrator".
Press the Fix button.
If for some reason the tool needs a restart, please make sure you let the system restart normally.
When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
Post the logfile Fixlog.txt as attachment in your next reply.

soj4trade · Aug 25, 2022

Marvelous. Here's that log!

Maxstar · Aug 25, 2022

All the leftovers of this update are removed succesfully. Please run the following commands again, but maybe there is a reboot needed before the second command will succeed!?

Code:

DISM /Online /Cleanup-Image /AnalyzeComponentStore
DISM /Online /Cleanup-Image /StartComponentCleanup

soj4trade · Aug 25, 2022

Code:

C:\Windows\system32>DISM /Online /Cleanup-Image /AnalyzeComponentStore

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[===========================99.9%========================= ]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 7.83 GB

Actual Size of Component Store : 7.70 GB

    Shared with Windows : 4.92 GB
    Backups and Disabled Features : 2.06 GB
    Cache and Temporary Data : 729.79 MB

Date of Last Cleanup : 2022-08-23 06:27:17

Number of Reclaimable Packages : 10
Component Store Cleanup Recommended : Yes

The operation completed successfully.

Code:

C:\Windows\system32>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 1

Incorrect function.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

I did NOT reboot though. Would you like me to do that tonight and try again tomorrow?

Maxstar · Aug 25, 2022

Yes reboot the machine first and try the DISM /StartComponentCleanup command again.

The count of Reclaimable Packages is now on 10, so maybe we need to remove other updates as well with FRST?

soj4trade · Aug 25, 2022

Maxstar said:
The count of Reclaimable Packages is now on 10, so maybe we need to remove other updates as well with FRST?

Just what I was thinking... :)

I feel comfortable using SFCFix on my own, but I haven't fully understood FRST yet. Essentially we're just looking for 0x8000ffff in CBS.log, checking for that KB, and ripping it out of the registry with FRST if it's not present on the system? If so, then I can reboot tonight, try /StartComponentCleanup again tomorrow, and then begin tearing KBs out of the registry tomorrow (assuming DISM fails again).

The one thing I'm lacking insight on is how you compiled fixlist.txt so quickly. SearchReg.txt called out thousands of registry entries that didn't belong, and you converted those into a hit list pretty fast. If I could do this as well, then I could probably start knocking out these 10 remaining packages...

Or I'm happy taking it slow with you as well! No worries wither way!!

Maxstar · Aug 25, 2022

The public tutorial for FRST is hosted at G2G with a detailed description of all the directives.

soj4trade said:
Essentially we're just looking for 0x8000ffff in CBS.log, checking for that KB, and ripping it out of the registry with FRST if it's not present on the system?

This depends entirely on all the errors the CBS log reports, each time it can be different. That said, there is no standard way of fixing.

soj4trade said:
Or I'm happy taking it slow with you as well!

This is the best option, because I can follow the whole process what we've done - and I have all the (previous) logs to take a look at if needed.

soj4trade · Aug 25, 2022

Code:

C:\Windows\system32>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]

Error: 1

Incorrect function.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

This was after a reboot unfortunately...

Maxstar · Aug 26, 2022

Hi,

Please post the latest CbsPersist logs as well.

Rich (BB code):

2022-08-25 10:57:11, Info                  CBS    Archived backup log: C:\Windows\Logs\CBS\CbsPersist_20220821051529.cab.
2022-08-25 10:57:11, Info                  CBS    CAB compressed log file: C:\Windows\Logs\CBS\CbsPersist_20220821051529.log
2022-08-25 10:57:28, Info                  CBS    Archived backup log: C:\Windows\Logs\CBS\CbsPersist_20220822041342.cab.
2022-08-25 10:57:28, Info                  CBS    CAB compressed log file: C:\Windows\Logs\CBS\CbsPersist_20220822041342.log

soj4trade · Aug 26, 2022

Sorry about that. Here's those files!

CBS.zip

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

Moderator, Windows Update Expert, Security Analyst

Well-known member

Moderator, Windows Update Expert, Security Analyst

Well-known member

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member