6
2
I'm an advanced level user here with an odd issue. I have two Windows Updates that are failing to install, every single time. I'm getting a mysterious "Code 1" error on both updates, an error for which I'm having difficulty finding a solution.
The updates in question are:
- Security Update for Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (KB2538243)
- System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [May 2011]
Because these updates are failing, the Shut Down button in my start menu always has the shield icon next to it, indicating that "new" updates will be installed on shut down. But, of course, they'll fail and when the PC is restarted, the shield icon is still there.
When checking the update history and viewing the details of the failed updates, I get the following:
Security Update for Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (KB2538243)
Installation date: 6/29/2011 3:00 AM
Installation status: Failed
Error details: Code 1
Update type: ImportantA security issue has been identified leading to MFC application vulnerability in DLL planting due to MFC not specifying the full path to system/localization DLLs. You can protect your computer by installing this update from Microsoft. After you install this item, you may have to restart your computer.
More information: http://go.microsoft.com/fwlink/?LinkId=216803
and:
System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [May 2011]
Installation date: 6/28/2011 3:00 AM
Installation status: Failed
Error details: Code 1
Update type: ImportantThis tool is being offered because an inconsistency was found in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software. This tool checks your computer for such inconsistencies and tries to resolve issues if found.
More information: http://support.microsoft.com/kb/947821
About My System
I'm running Windows 7 Home Premium 64-bit. This is a custom PC build and the OS was installed fresh, not an upgrade from a previous version. I've been running this system for about four months. Windows Updates aside, the system is usually quite stable.
In my experience, (automatic) updates usually fail because I am too low on free space. I don’t know if that applies to you. – Synetech – 2011-06-30T02:15:35.107
I sure hope someone comes up with the answer to this. I have exactly the same problem (Windows 7 Enterprise, x64). I've tried every trick and method suggested by every article I can find. The kicker? I'm running a build from Microsoft IT and (usually) get my updates from internal MS servers. – BillP3rd – 2011-07-02T00:02:12.563
1Have you looked in %systemroot%\windowsupdate.log? Whole lotta info in there! – kreemoweet – 2011-12-29T07:54:08.793
You may want to follow the diagnostic methodology mentioned on Mark Russinovich's Blog that uses the logging capabilties of Sysinternals Process Monitor to get more information about what is going on during installs. It's not a guaranteed fix, however, it may get you a little closer to the root cause.
– Trav – 2012-12-24T07:54:50.910