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.
Win 7 SP1 fails with E_FAIL 0x80004005
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.
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?
54 additional answers
Sort by: Newest
-
Anonymous
2011-02-24T21:59:22+00:00 Trying to install SP1 I get to 99% cofiguring service pack the failure configuring service pack.
Once its done I get service pack failed Unspecified error E_FAIL 0x80004005.
To top it off all my settings are hosed and I have NV drivers installed on my AMD chipset and a buch of bullshit network adapter I had removed like Wan miniport (Network Monitor) PPOE SSTP IPV6 ect.
I removed that garbage for a reason now after this failure they are all back.
This SP sucks, a few security updates my ____!
I might as well reinstall my whole OS and spend a week reconfiguring it, deleting all the bullshit I dont need.
What the F do I need NV storage drivers running on a AMD chipset?
There they were in legacy drivers, NV storage and NV disk.
-
Anonymous
2011-02-24T13:29:15+00:00 I too have had failures on 3 pcs using the Ultimate edition (2 with 32 bit and one with 64 bit).
Have gone through all the hoops as stated above but still end up with the failure error. I have now hidden the sp1 update till MS sorts this out.
-
Anonymous
2011-02-24T13:18:47+00:00 I tried the clean boot, Sfc /scannow, the system update readiness tool. None of this stuff worked. By the way I'm using 32bit windows. It looks to me like the hail mary plays aren't working and someone will have to start actually troubleshooting the problem.
As for "unspecified error" not being much help, I agree. That looks to me to be a substitute for good programing practices. The program should recognize the symptom that caused it to fail. It might not know the root cause but it could certainlyannunciate the operation that failed instead of the useless unknown error.