Tenfold Increase In Boot Time: Failed Win 7 Update KB2862335 (8007002)

[LouieChuckyMerr]

Hello and thank you in advance for any help. I try to keep my Windows 7 Home Premium up to date and typically manually install Windows Updates monthly without issue. This month (October 2013), however, while installing all of the important updates (except IE10 and the Windows Malicious Software Removal Tool), my laptop froze partway through the installations. After a powering off-powering on my laptop seems to function fine but for 2 things: update KB2862335 failed, with error code 80070002, and is in an endless update-failed loop (after a few days of this I hid the update) and my boot time has increased roughly tenfold, from about 10 seconds to almost 2 minutes. While I realize that the increased boot time isn't necessarily a huge issue since the computer still functions properly, I'd like to solve this puzzle and once again derive the boot-time benefits from my extra RAM and SSD (as well as scratch a brain itch ). For the last few days I've been poking away at the problem with no success. I've:

• Uninstalled all the successful October updates then reinstalled them (KB2862335 still continued it's update-failed loop and boot time was still increased).

• Renamed C:\Windows\Software Distribution then attempted to update (KB286335 still continued it's update-failed loop and boot time was still increased; also, my update history is now truncated , live and learn).

• Run the command prompt sfc /scannow, from the desktop and the Repair Console, multiple times each, with the same result: failure at 54% and the error message "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Log\CBS\CBS.log".

• Downloaded and run the System Update Readiness Tool. It ran with no problems, installing a patch (I forgot to note the name-number ), but after a (still slow) reboot KB2862335 still loops update-failed.

Opening the CBS.log in Notepad just about made my head explode , as there are line after line (after line after line...) of what appear to be some form of modern hieroglyphics. More research allowed me to shrivel the log to only text pertinent to the last sfc /scannow and corrupt files, but it's still 1.32 MB of (seemingly random, ha ha) text. Attached are a snapshot of the failed update error code, a zipped copy of the CBS.log for a single sfc /scannow (I deleted the log then ran the scan once), and a zipped copy of the shriveled CBS.log. It seems to me that there are a oodles and oodles of corrupt files in need of deletion-repair but, unfortunately, I've exhausted my rather limited storehouse of ability to solve the problem. Thanks again for any help, I really appreciate it.

 

[Layback Bear]

I no expert on such things but some more information would be helpful
when one get here.


Fill in your System Specs including what security programs you have installed. This Tutorial from Brink will help.

http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

 

[LouieChuckyMerr]

I've updated my system specs; apologies for the oversight.

 

[NoelDP]

There are a LOT of file errors in the report - and the SFC scan didn't complete properly.


Please attempt another SFC scan, and post the new CBS.log file - also post the CheckSUR.log file from the same folder.

 

[LouieChuckyMerr]

Thanks for your reply, NoelDP. As I typed in my original post, multiple and different source sfc /scannows all resulted in failure at 54% with the same message. Attached are the zipped CBS.log file after another scan and the zipped CheckSUR.log. Thanks again.

 

[NoelDP]

It's not surprising - here's the summary from the CheckSUR scan...

Summary:
Seconds executed: 288
 Found 7239 errors
  CSI Manifest Missing Total count: 4
  CSI Payload File Missing Total count: 7235

There is no point in attempting to fix this manually

A Repair Install may work - but back up your data to external media first!

See the instructions here...
http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[LouieChuckyMerr]

Thank you very much for your help, NoelDP. I was afraid it might come to this given the size of the log files. I'll try a Repair Install, thanks for the link, but I'll image my drive first.

 

[NoelDP]

Good luck with it!

 

[LouieChuckyMerr]

In case anyone reads this, I would absolutely recommend that you image your partition-disk before doing a repair install. That way, if you're unhappy with the overall result then it's easy enough to revert. Although the repair install cured my slow boot issue it also overwrote myriad customizations that I'd made to my Windows 7 and generally wreaked havoc on my system (havoc in the sense of installing unwanted programs, adding things to the start menu, etc). Given that I'll be getting a new laptop in a couple of months (on which I'll do a clean custom install), I'd rather live with a slow boot for a short stretch than have to retweak everything. Read and understand the "Note", "Tip", and "Warning" sections prefacing the Repair Install guide (excellent guide, by the way, many thanks to Brink, the author ) and you should have no problems. Thanks again for all the help.