Solved KB2852386 - "Windows Updates Cleanup" failing after reboot ! :(

[adi518]

KB2852386 - "Windows Updates Cleanup" failing after reboot !

Hi, I finally heard of this KB and ran like mad to install it and get some gigs off my ssd.

Installing went fine. I ran the clean up wizard and lo and behold, it found 3.5 gigs of windows updates leftovers. I selected it and let it do it's thing... then a reboot occured and when it's time to "configure updates", it showed "failure to configure windows updates reverting blabla".

The annoying thing that not only it fails, it also creates several gigs of "error reporting data". meh.

So, I did a heck of a search on google and found one thread (on a different forum) where someone getting the same msg when specifically trying to use the new clean up feature. Unfortunately there was no solution posted.. he didn't solve it.

I tried all the "fixit" apps or the "WU troubleshooter" and none of them work. Really annoying cause I can't enjoy this new wonderful KB.

I'm not a novice, but would appreciate any idea that pops into mind in solving this issue!

Thanks

 

[NoelDP]

Pleasefollow the WindowsUpdate Posting Instructions and post the requested data

 

[adi518]

Yes, I followed them, but forgot to attach the CBS logs. They're now added to the first post. I excluded the cab files as they seem unrelated and weigh unreasonably for this request.

I tried to run the readiness tool 3 times now.. didn't make any difference.

Ah... I now recalled something. I ran sfc and it came back saying it couldn't repair some stuff. Never happened to me before, since I ran this tool couple times and it always came back fully successful.

 

[NoelDP]

This batch of errors may have something to do with your problems...

Checking Component Store
(f) CSI Payload File Missing 0x00000000 Koala.jpg amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 Jellyfish.jpg amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 SampleRes.dll amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 desktop.ini amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 Desert.jpg amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 Lighthouse.jpg amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 Tulips.jpg amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 Chrysanthemum.jpg amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 Hydrangeas.jpg amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 Penguins.jpg amd64_microsoft-windows-photosamples_31bf3856ad364e35_6.1.7600.16385_none_f36e0e659b8042be 
(f) CSI Payload File Missing 0x00000000 Clip_1080_5sec_VC1_15mbps.wmv amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4 
(f) CSI Payload File Missing 0x00000000 Clip_480_5sec_6mbps_h264.mp4 amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4 
(f) CSI Payload File Missing 0x00000000 winsat.wmv amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4 
(f) CSI Payload File Missing 0x00000000 Clip_1080_5sec_MPEG2_HD_15mbps.mpg amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4 
(f) CSI Payload File Missing 0x00000000 Clip_1080_5sec_10mbps_h264.mp4 amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4 
(f) CSI Payload File Missing 0x00000000 winsatencode.wmv amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4 
(f) CSI Payload File Missing 0x00000000 Clip_480i_5sec_6mbps_new.mpg amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4 
(f) CSI Payload File Missing 0x00000000 Clip_480p_5sec_6mbps_new.mpg amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4 
(f) CSI Payload File Missing 0x00000000 desktop.ini amd64_microsoft-windows-videosamples_31bf3856ad364e35_6.1.7600.16385_none_51a21f033003affd 
(f) CSI Payload File Missing 0x00000000 Wildlife.wmv amd64_microsoft-windows-videosamples_31bf3856ad364e35_6.1.7600.16385_none_51a21f033003affd 
(f) CSI Payload File Missing 0x00000000 Kalimba.mp3 amd64_microsoft-windows-musicsamples_31bf3856ad364e35_6.1.7600.16385_none_06495209cbd8e93b 
(f) CSI Payload File Missing 0x00000000 desktop.ini amd64_microsoft-windows-musicsamples_31bf3856ad364e35_6.1.7600.16385_none_06495209cbd8e93b 
(f) CSI Payload File Missing 0x00000000 Maid with the Flaxen Hair.mp3 amd64_microsoft-windows-musicsamples_31bf3856ad364e35_6.1.7600.16385_none_06495209cbd8e93b 
(f) CSI Payload File Missing 0x00000000 Sleep Away.mp3 amd64_microsoft-windows-musicsamples_31bf3856ad364e35_6.1.7600.16385_none_06495209cbd8e93b 
(f) CSI Payload File Missing 0x00000000 desktop.ini amd64_microsoft-windows-ehome-samplemedia_31bf3856ad364e35_6.1.7600.16385_none_b6b9b223710b3802 
(f) CSI Payload File Missing 0x00000000 win7_scenic-demoshort_raw.wtv amd64_microsoft-windows-ehome-samplemedia_31bf3856ad364e35_6.1.7600.16385_none_b6b9b223710b3802

It looks to me as if someone has been attempting to 'tidy up' the system by deleting files that they don't use - and removed them from the protected area of the OS.

I'll post a fix to repair those files later (possibly tomorrow, now) and we'll see if that helps at all.


There are a couple of errors in the CBS.log (actually the same error twice, once at shutdown and again on boot) -

2013-10-18 17:10:37, Info                  CBS    Shtd: Processing non-critical driver operations queue, Count 1.
2013-10-18 17:10:37, Info                  CBS    Doqe: Locking driver updates, Count 1
2013-10-18 17:10:37, Info                  CSI    0000001b Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:7ee0cfd10bccce0192030000080a9014} pathid: {l:16 b:7ee0cfd10bccce0193030000080a9014} path: [l:172{86}]"\SystemRoot\WinSxS\amd64_bth.inf_31bf3856ad364e35_6.1.7601.17607_none_d0789c5ad225ef11" pid: a08 starttime: 130265786204997858 (0x01cecc0ad922c8e2)
2013-10-18 17:10:37, Info                  CBS    Doqe:   q-uninstall: Inf: bth.inf, Ranking: 2, Device-Install: 0, Key: 1, Identity: bth.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.17607, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
2013-10-18 17:10:37, Info                  CBS    Perf: Doqe: Uninstall started.
2013-10-18 17:10:37, Info                  CBS    Doqe: [Forward] Uninstalling driver updates, Count 1
2013-10-18 17:10:37, Info                  CBS    DriverUpdateUninstallUpdates failed [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-10-18 17:10:37, Error                 CBS    Doqe: Failed uninstalling driver updates [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

I'll see what I can do about that after we've fixed the file errors.

 

[adi518]

Yeh, I think I removed these via wise disk cleaner.. why, are these samples needed?

Isn't this caused by an 'access denied' error of some sort? that's what happens when I try to install the latest 4 KB updates posted in another thread here.

 

[NoelDP]

If you're using ANY of the Wise stable of programs please uninstall them. They are without exception dangerous and WILL break your installsooner or later.

 

[adi518]

Yeh I know these apps aren't too popular, but in this case, the only thing I did was removing these samples. I won't remove something I feel unsure of.

 

[NoelDP]

There are good reasons why Wise apps aren't liked. Get rid.

 

[adi518]

What about the other batch of errors? any ideas? _

Hmm... I see this error code in there: 0x80070490

Which searching for, leads to this: http://support.microsoft.com/kb/958044

Hmm maybe windows repair will indeed help?

 

[NoelDP]

PLEASE wait until I can get back to you@

 

[adi518]

Ok, will do.

 

[NoelDP]

I've uploaded a file - a58aa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print theseinstructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, starttapping F8 - this should bring up the Advanced Boot Menu, at the top of whichshould be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\a58aa
hit the enter key - if you get a 'NotFound' error try
DIR D:\a58aa
or
DIR E:\a58aa



The drive letter in use when you find the folder willneed to be substituted (for<drive>) into the followingcommand...



XCOPY<drive>:\a58aa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time)andwhen the prompt returns, type
EXIT
and hit the Enter key to exit CommandPrompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in anElevated Command Prompt
then reboot and upload the new CBS.log file to your reply.

 

[adi518]

Hmm.. it wants the installation dvd for that. Am I suppose to do this without it?

 

[NoelDP]

In that case I suspect that you would be best off doing a repair install...
See the instructions here...
http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[adi518]

Ok, I'll try that and come back in like 30 minutes.

Should I run sfc after that and report back with the cbs log?

 

[NoelDP]

It will take a LOT longer than 30 minutes for you to do it properly. The updates afterwards (assuming the repair goes OK) will take a good couple of hours.

 

[adi518]

Hmm.. I made a usb boot stick from the latest win 7 sp1 msdn iso I had on my drive. Stuck it and let it reboot, I went to 'repair my computer' which I already used many times in the past to fix startup issues. Then, I chose CMD and copied these files.. went fine. I'm now doing sfc /scannow and will report back in 5.

In the repair wizard there isn't an option that 'fixes' windows.. you have startup fixes but that's unrelated afaik. And you have restore points and restore images which I don't use.

Ok, this time sfc came back saying it found no integrity violations.

 

[adi518]

Ok, the new CBS is attached.

Edit: I just tried (again) to clean up "windows updates cleanup" via the wizard and it still comes back with a failure msg.

 

[NoelDP]

Good - SFC claims to have fixed the remaining error itself

There are some interesting entries in the background CBS log -

 Line 158:     6: Create Directory: Directory = [l:72{36}]"\??\C:\Windows\System32\LogFiles\AIT", Attributes = 00000084
 Line 481:     10: Create Directory: Directory = [l:74{37}]"\??\C:\Windows\System32\LogFiles\WUDF", Attributes = 00000080
 Line 842:     108: Create Directory: Directory = [l:72{36}]"\??\C:\Windows\System32\LogFiles\Fax", Attributes = 00000080
 Line 843:     109: Create Directory: Directory = [l:90{45}]"\??\C:\Windows\System32\LogFiles\Fax\Outgoing", Attributes = 00000080
 Line 844:     110: Create Directory: Directory = [l:90{45}]
 Line 1129:     17: Create Directory: Directory = [l:28{14}]"\??\C:\inetpub", Attributes = 00000080
 Line 1134:     21: Create Directory: Directory = [l:44{22}]"\??\C:\inetpub\wwwroot", Attributes = 00000080
 Line 1135:     22: Create Directory: Directory = [l:38{19}]"\??\C:\inetpub\logs", Attributes = 00000080
 Line 1136:     23: Create Directory: Directory = [l:38{19}]"\??\C:\inetpub\temp", Attributes = 00000080
 Line 1643:     11: Create Directory: Directory = [l:30{15}]"\??\C:\PerfLogs", Attributes = 00000080
 Line 1644:     12: Create Directory: Directory = [l:42{21}]"\??\C:\PerfLogs\Admin", Attributes = 00000080
 Line 1691:     7: Create Directory: Directory = [l:28{14}]"\??\C:\inetpub", Attributes = 00000080
 Line 1692:     8: Create Directory: Directory = [l:38{19}]"\??\C:\inetpub\temp", Attributes = 00000080
 Line 1693:     9: Create Directory: Directory = [l:56{28}]"\??\C:\inetpub\temp\appPools", Attributes = 00000080
 Line 1694:     10: Create Directory: Directory = [l:44{22}]"\??\C:\inetpub\history", Attributes = 00000080
 Line 2333:     27: Create Directory: Directory = [l:114{57}]"\??\C:\Windows\System32\LogFiles\Windows Portable Devices", Attributes = 00000080
 Line 2432:     4: Create Directory: Directory = [l:82{41}]"\??\C:\Windows\System32\LogFiles\Firewall", Attributes = 00000080
 Line 2821:     19: Create Directory: Directory = [l:30{15}]"\??\C:\PerfLogs", Attributes = 00000080
 Line 2822:     20: Create Directory: Directory = [l:42{21}]"\??\C:\PerfLogs\Admin", Attributes = 00000080
 Line 4175:     4: Create Directory: Directory = [l:114{57}]"\??\C:\Windows\SysWOW64\LogFiles\Windows Portable Devices", Attributes = 00000080

It seems that something had deleted a lot more (and more critical) than just the sample files!

How is Windows Update behaving now?

What happens if you attempt to run the cleanup now?

 

[adi518]

WU cleanup still doesn't work.. will come back with the failure msg after reboot.