Win 7 SP1 fails with E_FAIL 0x80004005

Anonymous

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

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

Answer accepted by question author

Anonymous

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.

0 comments

Answer accepted by question author

Anonymous

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?

0 comments

54 additional answers

Anonymous

2011-03-03T16:16:07+00:00

I tried,

No success.

It does not work with a fresh install ether(tried 4x)

So I have reinstalled it and I'm not going to install the SP1...
Was this answer helpful?

0 comments No comments
Anonymous

2011-03-05T02:36:17+00:00

Like others I tried everything possible I even had remote support from Microsoft & it could not be resolved. I would like mention that the support I received from Microsoft was of a high standard. However In the end all I could do was use my recovery discs for the Windows (as it was a laptop and only recently purchased ..Jan 2011...I did not get a Windows Installation disc there is a hidden partition on my hard drive & also you are promoted to make a set of DVD's when you first use the computer). After I did that I went straight to getting all the windows updates (I did not install any other software until after this) all updates installed okay until I had nothing left. After the computer re-booted I checked Windows update and the SP 1 was the only update left to install so I let Windows 7 Install it. After the Service Pack 1 was downloaded and installed Windows 7 confirmed that the Service Pack was installed okay :) In weighing up the options it seemed to be a drastic choice but I figured if I put it off for say 6 months I would inevitably have to take this step & have more programs & data on the computer which would take more time to deal with than to tackle it now. Hope my experience is of help to someone else!
Was this answer helpful?

0 comments No comments
Anonymous

2011-03-10T23:02:27+00:00
Well, I won't bore everyone with another description of the 0x80004005 error. I think we all see the symptoms here.

    I do have a success story and some observations, though.

    I, too, was a victim of the dreaded error. I am an IT professional responsible for keeping our Windows environment up-to-date. We have about a dozen servers and 8 or so Windows 7 boxes. Most of the servers are running Windows Server 2008 R2 (which you should know is ONLY available in 64-bit). Almost all of the Windows 7 clients are x64 as well. This "troubled" server is the only one that does not have anti-virus installed on it at all. The others have Trend OfficeScan Corporate Edition installed on them which apparently has no impact on their SP1 success.

    The "troubled" Windows Server 2008 R2 Standard server exhibited the error and did not want to accept the SP1 from our WSUS server, Windows update or the DVD image manually run. Here's what I did to resolve this:
1. I downloaded to tool mentioned above, Windows6.1-KB947821-v10-x64.msu.
2. I stopped all non-essential services. This box happened to have Backup Exec 2010 which requires SQLEXPRESS to operate. I stopped all of the Backup Exec services and the SQLEXPRESS instance, agent browser and related services.
3. I then executed the Windows6.1-KB947821-v10-x64.msu file and the indication was that it completed successfully.
4. Without rebooting, I immediately ran the SP1 setup file from the DVD image mounted locally. I selected the option to reboot as needed during setup. This took about 30 minutes to run and the CPUs and disks showed activity. There was only one reboot that occured at the end of the installation.
5. After the system rebooted and I logged in, I was informed that SP1 was installed successfully. I viewed the system properties to confirm this. SP1 was listed below the version info. Also, MSInfo32 lists "Version 6.1.7601 Service Pack 1 Build 7601" now on this server.
6) Shortly after logging in, I was offered SP1 though Windows update again. I selected to install it and it immediately indicated that the installation was successful without even showing the setup dialog.
1. I reviewed the Windows Update installation history and discovered something really interesting:
This was viewed on 3/11:

-- On 3/9, it showed that SP1 had been installed successfully. This would have been via the scheduled updates. Of course, I was still offered the SP1 via Windows Update.

-- On 3/10, it showed the same SP1 unsuccessful.

-- Also on 3/10, an entry showed Canceled (which I did cancel manually)

-- Finally, on 3/10 it shows successful for this last attempt which appears to have been "actually successful".

   I'd be interested to see if others see multiple successful installations of SP1 in their Windows Update history.

   Well, for what it's worth, this process worked for me. Try stopping your SQL instances or any other service that maintains a file lock or real-time monitoring process. I did not try the other suggestions that seem to be fruitless such as Safe Mode, clean-boot or any others not stated here.

    Please let us all know if this guidance is helpful for you. This seems to be a thorn in the side of a lot of users out there.

Chris
Was this answer helpful?

0 comments No comments