This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
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?
Follow-up, after MS patch Tuesday 5/10 which according to one blog post by Ed Bott, claims of MS fixing this issue or more accurately addressing this issue. Well, I just went through the SP1 upgrade once again, and once again it leaves one of my machines in a constant re-boot mode. Selecting an earlier restore point fixes the OS but naturally back to an install w/o SP1. Come on MS, keep those fixes coming.
Well, now it's July and I am still having the same problem reported by everyone in February! The official release of SP1 results in the same error messages on my 32-bit Win7 Home Premium installation. I even removed my antivirus software completely to make sure. The Checking System Update Readiness tool found no errors, but SP1 keeps failing. How this turkey got released I'll never know...
Same here, tried the latest update readyness tool. Same song and dance. Tried everything but a reinstall. aint about to do that. What a pain. If I added up the amount of time I spent on this at my current rate of pay as a IT Tech..................Wow $708. Like any other software vendor I have delt with. Focusing on the next thing with promises of how awesome it is and not fixing anything else they already have in production.
