Problems with Windows Update, Error Code 8000FFFF

Skeeedunt

Platinum Member
Oct 7, 2005
2,777
3
76
Bear with me, I'll try to keep this as concise as possible. System is Vista Business x64 with 4 gigs. A few days ago, I opened Windows Update (set to download and notify), and noticed that there were updates dating back to October 9th (5 of em). No problem, click install. Comes back with "Error code 8000FFFF" (which apparently can mean any number of things). After extensive googling, I tried a few things, none of which (really) worked:

Uninstalled KB929777, restarted, downloaded KB929777 directly from microsoft.com and installed. That installed fine, but same errors in WU.

Tried installing some of the updates individually through WU, same error.

This is where things get interesting. Ran "sfc /scannow", which came back saying it found errors which it could not fix. Re-ran in safe mode, still couldn't fix. Re-ran after booting from Vista DVD (with /offline=c:\ stuff), said it didn't find any errors - but booting back into the OS and running it again revealed the same errors. Turned off AV (Kaspersky) before I ran all of these.

Per the advice of some MS KB articles, I looked through my CBS.log files for all the [SR] entries. The logs contained no indication of errors, corrupted files, or attempts to fix files, despite the fact that sfc.exe says it found errors. Looking through the windowsupdate.log file, however, indicated that it could not download due to certain errors that sounded related to windows protection/sfc (sorry, the exact lines escape me at the moment, I can look it up when I get home).

Some suggested a failing hard drive. I imaged the disk and restored to a different hard drive, same problems. I then tried the following on both images, with the same result:

Gave the Administrators group ownership, then Full Control permissions, of c:\Windows and all subcontainers. SFC now indicates no errors, and WU works fine. Unfortunately, when I reboot, I get Windows Protection errors and it says my copy of windows is not valid (I assume this has to do with dicking around with the permissions on \Windows). Not an ideal solution.


If anyone has any clue what's going on here, your help would be much appreciated. I'm going to restore the image I backed up and take another crack at this when I get home.