Win 7 SP1 fails with E_FAIL 0x80004005

Anonymous
2011-02-23T19:11:43+00:00

Hi, I can't get Windows 7 Service Pack 1 to install. I'm running Ultimate. I''m installing via Windows Update. I've got internet access. I've tried multiple times, but I always get an E_FAIL 0x80004005. I looked in the CBS.log and find (around the error) this:

2011-02-23 17:49:23, Info                  CBS    TrustedInstaller service starts successfully.

2011-02-23 17:49:23, Info                  CBS    SQM: Initializing online with Windows opt-in: False

2011-02-23 17:49:23, Info                  CBS    SQM: Cleaning up report files older than 10 days.

2011-02-23 17:49:23, Info                  CBS    SQM: Requesting upload of all unsent reports.

2011-02-23 17:49:23, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]

2011-02-23 17:49:23, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]

2011-02-23 17:49:23, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6

2011-02-23 17:49:23, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]

2011-02-23 17:49:23, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.

2011-02-23 17:49:23, Info                  CBS    NonStart: Checking to ensure startup processing was not required.

2011-02-23 17:49:23, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x55fb5c

2011-02-23 17:49:23, Info                  CSI    00000005 Creating NT transaction (seq 1), objectname [6]"(null)"

2011-02-23 17:49:23, Info                  CSI    00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x1c4

2011-02-23 17:49:23, Info                  CSI    00000007@2011/2/23:16:49:23.537 CSI perf trace:

CSIPERF:TXCOMMIT;11544

Any ideas on how to fix it would be appreciated.

Regards,

Mike

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2011-04-11T05:31:43+00:00

Right on.  I also did an in place upgrade (or what some others call a repair installation), and SP1 installed after the 1-2 hours it took to redo the installation.  Pain in the butt, but it worked.  I'm surprised no one from the Microsoft support team has posted this as a possible solution on these forums--I've only seen it mentioned by community members like NickMoul.

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2011-04-05T08:45:02+00:00

After trying everything, I performed an in place upgrade, using a DVD I had of my version of Windows 7. Don't forget to write down your activation code before you do it.

After inplace upgrade SP1 installed with no issues. I have no idea what was wrong, but W7 performs same as before.

MS needs to sort this out with a Fix-It link.

Only clue was that the inplace upgrade notified me that dot NET 4 was e corrupted and needed a reinstall which it downloaded and reinstalled. Hope that help someone.

Best of luck.

Support? What support?

Was this answer helpful?

0 comments No comments

54 additional answers

Sort by: Oldest
  1. Anonymous
    2014-01-14T18:02:33+00:00

    As knowledgeable and frequent Community contributor A. User stated on March 19, 2012 (see previous page in this thread, page 5), Norton and other AV solution suites are often culprits in regards to CBS.log errors, especially 0x80004005. I've found that many users with OEM builds (i.e., a machine pre-loaded with Microsoft Windows by an Original Equipment Manufacturer) are unaware that their box came with a Symantec/Norton product pre-installed by the OEM (usually, a trial version), as they have never used the product. Uninstalling such AV products via the Windows Control Panel's Uninstall applet (Control Panel\Programs\Programs and Features on a Windows 7 unit) is the recommended approach, but as is so often the case - software programmers seem to widely assume that no one would ever wish to actually uninstall their product, and consequently uninstallers typically leave behind many things that can impact the functionality of Windows processes such as updates - a Control Panel uninstall may not suffice to solve all problems. 

    Symantec provides utilities that can help in this regard; their Norton Removal Tool is highly recommended. For users actively using a Norton AV solution suite, the Norton Remove and Reinstall Tool is a good choice.  If neither performing a Clean Boot as outlined in Microsoft KB929135 and/or running the Microsoft Fix it 50738 available on the KB2530477 Rev. 4.0 page "Installation of Service Pack 1 for Windows 7 fails with errors 0x8004a029 or 0x80004005 - E_FAIL" help, ensuring that Symantec software and settings are sufficiently removed may do the trick. For users of other AV software, the same types of "complete" uninstallation tools are also usually available; MVP Stephen Boots' Wiki Article "List of anti-malware product removal tools" contains a comprehensive selection of updated links to such utilities, as does Bleeping Computer's "List of Antivirus Uninstallers and Removal Tools". A helpful post by Microsoft Community Contributor James.Orr (see his post of April 12, 2011 on page 4 of this thread) mentions information taken from an article by Guy Thomas on his excellent ComputerPerformance.co.uk site, "Error Code 80004005 - Unspecified Error"; both this site and the Bleeping Computer forums contain a wealth of helpful information on a wide variety of topics.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-06-06T23:25:34+00:00

    After months of searching THIS WORKS!! Many thanks WillFuBev

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-11T19:26:07+00:00

    In my case, there was problem with more than 14 network adapters. Win accept only 14 at maximum, i had 16. After removing two of them and reboot everything works as a sharm. To discover the number of network adapters use this command from commandline:

    wmic nic get name, index
    

    Was this answer helpful?

    0 comments No comments