Difference between revisions of "Windows 7 Service Pack 1 Won't Install"

Revision as of 12:10, 1 October 2015

From Windows Update some users report a problem installing SP1. One common error is "Windows Update error 800B0100." This is often due to the downloaded installer in cache becoming corrupted. The next thing users attempt to do is grab the so called "network install" file which is the full install file as opposed to doing an "online install". The full install file is meant for system administrators to use on removable media or for multiple machine deployment. It is actually the best way to install a service pack, having the full file in hand. However, Microsoft has made it incredibly confusing locating the full network install for Windows 7 SP1 because of their dopey naming convention (or lack thereof) and poorly named debug files.

To download the stand-alone Service Pack 1 for Windows 7, go to Service Pack 1 for Windows Server 2008 R2 and Windows 7.

There are many files to choose from. The first file on the list is the .ISO (DVD image) of the Service Pack containing three different versions of the full installer. The three versions (IA, x64, x86) are meant for three different processor / architecture types. This ISO is for burning to a DVD disc. The installer auto-detects the architecture.

The large array of files with the word "Symbols" in the name you should not use. They are debug files and language pack files.

The final three files in the list happen to be the ones rolled up in the a aforementioned ISO file. As a stand alone installer it is one of these three files that you actually need for your computer. The naming of the files relates to architecture:

• IA64 for an Itanium processor (used in enterprise level servers)
• X64 for 64-bit Windows 7 (AMD and Intel)
• x86 for 32-bit Windows 7 (AMD and Intel)

The file names indicate they are for Windows 6.1. Well didn't you know that Windows 7 is Windows 6.1? You have to think like Microsoft! Windows 6.1 was the internal name for the version of Windows before the marking people rebranded it Windows 7.

It is important for you to be able to identify whether or not you have the SP1 already installed, or successfully installed after your attempt to install. Press the Windows Key + R and type the command "winver" and press enter.

• Version 6.1 (Build 7600) - indicates you have Windows 7 without SP1
• Version 6.1 (Build 7601) - SP1 installed

If you have a typical modern home computer or laptop you probably have a 64-bit processor and you will want to download the file:

• windows6.1-KB976932-X64.exe - which is Service Pack 1 for Windows 7, the full network install file. It is 903MB.

Note: Microsoft moves their file and link locations all the time. The links presented here were last known to work as of September 2015.

If installation fails using the full install file, typically this will occur immediately, then Microsoft recommends that you download something they call the "System Update Readiness Tool." For the example 64 bit system the filename for this tool is:

• Windows6.1-KB947821-v34-x64.msu - Hot fix for Windows (KB947821) update

KB is for Knowledge base with the number of the article it refers to. This tool is a misnomer in that it is nothing more than a fix for bugs in Windows 7 preventing the service pack from correctly installing on some systems. The fix is said to, "The tool scans for inconsistencies on your computer and fixes them." Be patient, as this install may appear to stall or freeze, give it up to 15 or 20 minutes. Even though the progress bar may not show movement, the tool is said to be working. Furthermore, it is said, "You can use the System Update Readiness Tool on computers that are running Windows 8, Windows 7, Windows Server 2008, Windows Server 2008 R2, and Windows Vista. "

note: When I installed this hotfix it took about 28 minutes. The progress bar didn't move and appeared stuck at the beginning, however, after 28 minutes "Installation Complete." Make sure you have Power Management configured so your computer does not go to sleep during installation of the System Update Readiness Tool.

If the hotfix was able to resolve your installation problem and allow you to install the service pack, then you are in the minority of users. Usually the hotfix is more useful for generating a report that indicates the missing or corrupted files that you need to go out and manually retrieve and hack into the windows directory on your own! Not a job for the faint of heart.

See: Microsoft KB-2700601

TRUST_E_NOSIGNATURE(0x800b0100)

CheckSUR.log says Unavailable Repair Files.

The Component Store that contains information about Windows components has been corrupted

KB2522422

https://www.microsoft.com/en-us/download/details.aspx?id=14826
http://www.microsoft.com/en-us/download/details.aspx?id=19953

Windows6.1-KB2522422-x64.msu


There was a microsoft update installed that is a fix for certain Canon brand printers.  (KB2522422)
"Cannot print from Internet Explorer 9 using some Canon printers "

Turn Windows Features on or off is blank or empty

External References

• Microsoft TechNet: Windows 7 Service Pack 1
• Microsoft Downloads: Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932)
• Microsoft: Windows Update error 800B0100
• Microsoft TechNet: TRUST_E_NOSIGNATURE (0x800b0100) when installing W7 SP1 or KB2758857
• Microsoft: How to perform a clean boot in Windows
• Microsoft TechNet:Advanced guidelines for diagnosing and fixing servicing corruption
• Windows Seven Forums: Windows 7: 8007370B Windows update encountered an unknown error
• Using CheckSUR and update packages to fix corruption - joscon [Microsoft] 26 May 2010 6:37 AM

See Also

• Annoyances of Windows Vista and Windows 7
• Windows 7 Tips & Tricks