"Windows Updates Cleanup" failing after reboot

mkv4ever · 14 Jan 2014

It wasn't a Symantec product in the past, but was later acquired by them...
It wasn't perfect, but I don't think they ruined it, but it is effectively abandoned since it hasn't been updated since last year (12 months, I mean).
Anyway, what I wanted to know if in the logs I provided are listed what updates are obsolete.
Thanks a lot.

NoelDP · 15 Jan 2014

The DeepClean log does show a list of what it's touched and how - but I'd think a number of times before attempting to follow it, as there are a mass of interdependencies which may cause problems.

mkv4ever · 15 Jan 2014

What would your suggestion be? Leave everything as is?
Not that I'm lacking space, but I wanted to remove useless updates...

EDIT: I rerun SURT and got these log, I added dism too since it seems I'm missing a file somewhere.

NoelDP · 16 Jan 2014

I'm not seeing any errors? the CheckSUR did find three errors relating to Symantec software, which it managed to correct, but the SFC results, if you ran one, have rolled off into a CBSPersist file.

For ease of reading the DeepClean log, I selected one update, and looked for occurrences....

Code:

 Line 7: 2014-01-12 01:29:57, Info                  CBS    Adding: Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514
 Line 388: 2014-01-12 01:30:52, Info                  CBS    DC: Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514: unique components: 3 Size: 204.81 KB (209,726 bytes)
 Line 4770: 2014-01-12 21:18:02, Info                  CBS    Adding: Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514
 Line 5151: 2014-01-12 21:18:55, Info                  CBS    DC: Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514: unique components: 3 Size: 204.81 KB (209,726 bytes)
 Line 9527: 2014-01-12 21:21:21, Info                  CBS    Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 superseded - uninstalled
 Line 9754: 2014-01-13 17:43:31, Info                  CBS    Adding: Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514
 Line 10135: 2014-01-13 17:44:24, Info                  CBS    DC: Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514: unique components: 3 Size: 204.81 KB (209,726 bytes)
 Line 14517: 2014-01-15 21:08:07, Info                  CBS    Adding: Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514
 Line 14902: 2014-01-15 21:08:57, Info                  CBS    DC: Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514: unique components: 3 Size: 204.81 KB (209,726 bytes)
 Line 19320: 2014-01-15 21:09:38, Info                  CBS    Microsoft-Windows-IE-Troubleshooters-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 superseded - uninstalled

So it looks like everything is happening right, except the removals

I have a nasty feeling that if you attempt to remove all the (140+?) superseded updates, you may run into more problems than it's worth for he sake of 6.8GB of disk space.

Troy6 · 17 Jan 2014

Your problem is similar to the problem in this thread:
https://www.sevenforums.com/windows-updates-activation/308666-kb2852386-windows-updates-cleanup-failing-after-reboot-4.html

It is likely that you are having the same problem with bth.inf, and the same steps will resolve your issue. However, since "Cleanup Windows updates" is attempting to remove multiple packages at the same time and more than one of them includes drivers, one or more of the other packages might also be causing the problem.

Additionally, there is a 2nd issue at work here. The RDP8 package (KB2592687) you have (Remote Desktop 8) hasn't actually been superseded. Instead, a package that it depends on has, and when the package that it depends on is scheduled to uninstall that makes RDP8 also eligible to be uninstalled. This package is known as the "DTLS" package (KB2574819). Most likely you have the v1.007 version of the DTLS package, which has a bug in its packaging that allows it to be superseded and removed, while RDP8 still needs it. To fix that you can install the v2.000 version of the DTLS package from here: http://support.microsoft.com/kb/2574819/en-us

Here's what I'd recommend:

A. Install the update to the DTLS package listed above.
B. Manually attempt to uninstall the KB2532531 (the package with bth.inf) by executing the following from an elevated cmd prompt, and allow it to go through the reboots as needed.

Code:

dism /online /remove-package /packagename:Package_for_KB2532531~31bf3856ad364e35~amd64~~6.1.1.0

If that succeeds upon reboot, then skip to C.
If and only if that fails upon reboot, then you will need to execute the following steps:

1. re-run the dism command above, but do not reboot
2. run regedit.exe as Administrator
3. navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations
4. There should be a sub-key named either "0" or "1". Expand that key
5. Under that key, you will see one or more numbered keys. Look for the numbered key that contains a value named "Inf" which is equal to "bth.inf" (probably "1".). You need to delete that entire key, and in order to do that you will need to give Administrators ownership of the key, and give Administrators delete access following these instructions:
6. Right click that numbered key and select "permissions"
7. Select the Owner tab
8. Select Administrators in the “name” list
9. Click OK
10. Select Administrators in the “Group or User names” list
11. Click on the Allow check box for Full Control
12. Click OK
13. Right click the numbered key again and select Delete
14. Reboot the computer

C. Re-attempt running "Cleanup Windows Updates." Report back, and supply a new cbs.log if it fails.

NoelDP · 18 Jan 2014

SOunds like a plan to me! (thanks - again! - Troy)

mkv4ever · 18 Jan 2014

Had to follow all steps, Cleaning still failed.
Attached the new cbs logs.
Thanks a lot.

EDIT: Changed rar with zip

Troy6 · 18 Jan 2014

I don't have a rar extractor, and I'd prefer not to install one. Can you post that in a .zip format please?

mkv4ever · 19 Jan 2014

I uploaded the zip version.

Troy6 · 19 Jan 2014

Thanks for uploading it as a zip.

It is still having a problem with usb.inf, or usbport.inf (likely both) that were installed by KB2529073. Here's how to work around it (similar to what you already did.)

1. Re-run "Windows update cleanup" command, but do not reboot
2. run regedit.exe as Administrator
3. navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations
4. There should be a sub-key named either "0" or "1". Expand that key
5. Under that key, you will see one or more numbered keys. Look for the numbered keys that contain the value named "Inf" which is equal to "usbport.inf" (probably "1".), and "usb.inf" (probably 2.) You need to delete both of those keys, and in order to do that you will need to give Administrators ownership of the key, and give Administrators delete access following these instructions:
6. Right click that numbered key and select "permissions"
7. Select the Owner tab
8. Select Administrators in the “name” list
9. Click OK
10. Select Administrators in the “Group or User names” list
11. Click on the Allow check box for Full Control
12. Click OK
13. Right click the numbered key again and select Delete
14. Reboot the computer

That should clear it up.