Windows 7: Unable to update to SP1 on Win7 64bit Pro

Last year or so I had an issue with KB2446709. My computer was one of those that ended up in the endless reboot loop, after uninstalling the KB I was back up and running but have since been unable to update Windows.



I have spent the better part of the last 3 days finally trying to fix this. I have gotten the error nailed down to one last file that for some reason is not included in the KB2446709 stand alone installer. I have grabbed that file already and expanded it, moving all files within listed in my Checksur.log file and have whittled them down to a single error. It's this last error I can not seem to get rid of as one file was missing from that package.

The file in question is Package_for_KB2446709~31bf3856ad364e35~amd64~~6.1.1.2.mum and
Package_for_KB2446709~31bf3856ad364e35~amd64~~6.1.1.2.cat

I was able to manually install all other security updates that have been waiting for the last year, this is the last one to get finished.

An in place install or upgrade is not an option.

Am currently at work, but am willing to post logs when I get home.

System is a homebrew, no new hardware installed prior to errors, error began showing after failed KB2446709 install and subsequent removal.

Have already tried the System Update Readiness tool, always completes but does nothing. As I said when I started this there were 4 errors listed in the Checksur.log and I have gotten it down to this last one.

Any help is greatly appreciated.

Have you seen this? How to fix Server Manager Errors after installing updates (HRESULT:0x800F0818 / HRESULT:0x800B0100) - Microsoft GTSC Romania - Enterprise Platforms Support - Site Home - TechNet Blogs

I had not seen that particular article, but several others similar. Like I mentioned in my post using that method, I lowered the number of problems from 4 or 5 down to 1, all the same KB number, just the package didn't contain the last entry that is showing in my Checksur.log file.

Was actually hoping someone had those particular files.

Thank you for the reply.

Package_for_KB2446709~31bf3856ad364e35~amd64~~6.1.1.2.mum
Package_for_KB2446709~31bf3856ad364e35~amd64~~6.1.1.2.cat

These two files are not included in Windows6.1-KB2446709-x64.msu from http://www.microsoft.com/download/en...ang=en&id=7909

Issue is fixed, since this KB pertains specifically to .NET 3.1 I treated it like any other failed uninstalled program and removed it's entries from the registry.

It took me less than 20 minutes to write an app in C# to do it. It would seem to me that if I can do it, MS should be able to fix these, and without doing a reinstall or in-place install.

Thank you for all the help. Happy computing.

I'm trying to find out if your problem is the same problem I'm having. Were you unable to install SP1, it failing maybe 60-70% into the install regardless of whether you did it manually or through windows updates? If not then sorry to muddle your thread, if so then could you please share your C# app because not having SP1 is making me unable to install certain programs.

No problems, yes I was having errors trying to install both regular updates and also SP1. I was able to manually install the updates, and eventually I was able to install SP1 without doing an in place install. My system is now running my original install with SP1. I am still unable to update to IE9, but as I'm a Firefox user this isn't a really big issue for me.

Download and run the Windows Update Readiness Tool Download: System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011] - Microsoft Download Center - Download Details

As for my app, I am not releasing it as it was specifically written to solve my problem, and unless yours is identical it would not do you any good.

Once you run the readiness update tool look in %WINDIR%\Logs\CBS\Checksur.log

There should be listing there what will help you identify why your update is failing. Also have a look in the Event Logs.

Click Start in the search field type eventvwr.msc Click the Event Viewer link under Programs that pops up. In the left hand window of Event Viewer expand the Windows Logs and select System. Here you should find direct error codes for the update failures. These will also help you identify your issues.

For instance one of my errors in the event log from failed updates was
I'd be more than willing to help in any way I can to recover your system.

Ok, thank you for the information.

My CheckSUR log:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 13.0 2012-01-19 21:10
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.21747_none_acdc7a2fd087986e.manifest amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.21747_none_acdc7a2fd087986e
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.17632_none_c180eb382346c80f.manifest x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.17632_none_c180eb382346c80f
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.17632_none_1d9f86bbdba43945.manifest amd64_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.17632_none_1d9f86bbdba43945
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.21747_none_de05c1b3714cccd3.manifest amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.21747_none_de05c1b3714cccd3
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.21747_none_cf64bd82be6eec44.manifest amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.21747_none_cf64bd82be6eec44
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.17632_none_dd81f362582b9265.manifest amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.17632_none_dd81f362582b9265
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.17632_none_ac58abdeb7665e00.manifest amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.17632_none_ac58abdeb7665e00
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_c204b9893c68027d.manifest x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_c204b9893c68027d
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_1e23550cf4c573b3.manifest amd64_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_1e23550cf4c573b3
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.17632_none_cee0ef31a54db1d6.manifest amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.17632_none_cee0ef31a54db1d6

Summary:
Seconds executed: 324
Found 10 errors
CSI Manifest All Zeros Total count: 10

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.21747_none_acdc7a2fd087986e.manifest
winsxs\manifests\x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.17632_none_c180eb382346c80f.manifest
winsxs\manifests\amd64_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.17632_none_1d9f86bbdba43945.manifest
winsxs\manifests\amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.21747_none_de05c1b3714cccd3.manifest
winsxs\manifests\amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.21747_none_cf64bd82be6eec44.manifest
winsxs\manifests\amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.17632_none_dd81f362582b9265.manifest
winsxs\manifests\amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.17632_none_ac58abdeb7665e00.manifest
winsxs\manifests\x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_c204b9893c68027d.manifest
winsxs\manifests\amd64_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_1e23550cf4c573b3.manifest
winsxs\manifests\amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.17632_none_cee0ef31a54db1d6.manifest

My event viewer shows:
Installation Failure: Windows failed to install the following update with error 0x80070643: Windows 7 Service Pack 1 for x64-based Systems (KB976932).

Installation Failure: Windows failed to install the following update with error 0x80073712: Windows 7 Service Pack 1 for x64-based Systems (KB976932).

Service Pack installation failed with error code 0x80073712. (this was attempting manual install)

Please let me know if you need any other information, I will provide it ASAP.

Hello, a quick google of your errors indicates there is corruption in your Component Store. Several posts indicate to try the System Update Readiness tool to fix these, but most who have tried it have had little luck. You can try running a few disk utilities to see if that cures your issue. Have a look at the second reply in this thread. How to fix - error code 80073712 - windows component store is corrupt - Microsoft Answers

Also from your event log the first error indicates there is a problem with the .NET framework. You can try to uninstall the framework, upon uninstall shutdown the machine, DO NOT REBOOT, a reboot will not clear the memory, wait a minute or two then restart the machine and download and reinstall the .NET framework. That should rid you of that first error.

See this page for details on that error. Windows Update error 80070643

More information on error 80073712 can be found here. Windows Update error 80073712

Let's first try to uninstall, and reinstall .NET and go from there. I am currently at work but will keep poking around for more information about recovering the component store.

So, I ran the tool that uninstalls .Net framework after turning the feature off. Shut down completely, upon reboot I try to install the .Net Framework ver 3.5 and it tells me "You must use 'Turn Windows features on or off' so I'm guessing it didn't get completely taken off. I'm not really sure how to proceed from here.

Windows 7 has .NET 3.5 built in by default. Try installing .NET 4, you should be able to turn 3.5 back on from Control Panel | Programs and Features | in the left hand window select Turn Windows Features On or Off, look for .NET 3.5 and just turn it back on. Then try to manually update .NET to version 4.

Use this version of .NET http://www.microsoft.com/download/en....aspx?id=17718

It's the offline installer. When you install it, either unplug your network adapters or disconnect them under Windows. This will force Windows to use the files inside the installer.