New
#1
Tenfold Increase In Boot Time: Failed Win 7 Update KB2862335 (8007002)
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.