PLEASE EDIT YOUR TOPIC AND PUT (SOLVED) IF YOU ARE ALL FIXED.(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)(About Shane)Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee. " I reply "To make it better.""Only a life lived for others is a life worthwhile"Honor & Respect is all that matters.
I have disabled antivirus , firewalls prior to update attempts, does not work.
I do not want to format this machine and start fresh.
And whenever something takes me ages, rather than write it down in my personal notes, I prefer to put it out online for everyone with the same problem to easily find and benefit from.
The problem I'm talking about today is trying to upgrade your Windows 7 installation to SP1 by applying Microsoft's update KB976932, called "Windows 7 Service Pack 1 for x64-based Systems" and getting nothing but a failure every time.
The same problem may affect 32-bit systems as well, and I'm not sure what the update number for that would be, but the solution should work for either one. Windows Resource Protection did not find any integrity violations.
The update starts just fine, chugs along for 10 minutes or so, then reboots the system and starts performing more operations, when suddenly one of them fails about 10% down the road, reboots, and reverts the whole process. Even though there are no integrity violations, we should have enough info in the log to diagnose the problem.
You end up with this message (code 80070490) and a failure for which there are a lot of useless "solutions" on the web that just don't work. I can't take credit for it – all I did was spend a month weeding through the crap, retrying, and getting nowhere, until a genius by the name Ben-IS came up with exactly the right diagnosis and provided exactly the right solution. We are going to use a utility called SFC (System File Checker or Windows Resource Checker), which is part of the Windows installation. Open up a command prompt (cmd) as administrator and run This will run for a while and produce a file called which you can find in %WINDIR%\Logs\CBS (usually C:\Windows\Logs\CBS). Unfortunately, Windows overwrote my CBS.log, so I'll go by the one Ben-IS provided.
See this KB929833 for more info on SFC and CBS (Component Based Servicing). Open up and look for something like Failed uninstalling driver updates or 0x80070490 – ERROR_NOT_FOUND.
If you have this line, which you should if you're reading this post, you should also see lines similar to these a few lines above: 2011-04-14 , Info CBS Doqe: q-uninstall: Inf: usbvideo.inf, Ranking: 2, Device-Install: 0, Key: 598, Identity: usbvideo.inf, Culture=neutral, Type=driver Update, Version=6.1.7600.16543, Public Key Token=31bf3856ad364e35, Processor Architecture=amd64, version Scope=Non Sx S 2011-04-14 , Info CBS Doqe: q-uninstall: Inf: sffdisk.inf, Ranking: 2, Device-Install: 0, Key: 599, Identity: sffdisk.inf, Culture=neutral, Type=driver Update, Version=6.1.7600.16438, Public Key Token=31bf3856ad364e35, Processor Architecture=amd64, version Scope=Non Sx S 2011-04-14 , Info CBS Doqe: q-uninstall: Inf: sdbus.inf, Ranking: 2, Device-Install: 0, Key: 600, Identity: sdbus.inf, Culture=neutral, Type=driver Update, Version=6.1.7600.16438, Public Key Token=31bf3856ad364e35, Processor Architecture=amd64, version Scope=Non Sx S One of these files is the culprit, and we're going to find out which one in the next step.
Now open up a different log file located at %WINDIR%\inf\log (normally c:\Windows\inf\log).
Look for a line that contains Failed to find driver update or FAILURE(0x00000490). In my case, it was: pnputil -a C:\Windows\Win Sx S\amd64_usbvideo.inf_31bf3856ad364e35_6.1.7600.16543_none_8a1a2513d42628c3\Microsoft Pn P Utility Processing inf : Driver package added successfully.