Windows 7: Win7 x64 SP1 (KB976932) Update Code 80010108

I had 11 updates (and 1 optional) available today, some Windows 7, two for Office 2007.

All installed just fine, except SP1. To get the others to install, I left SP1 for last. So until SP1, Windows Update worked. The error info is at the bottom of the post.

Searching here, I found no matches for code 80010108. Searching Microsoft, there were hits related to Windows Update, and SP's, but the text talks about Vista, not Windows 7... thought the date of the posts are mostly 2011. The problem for the error code relates to needing the latest update agent. But other than SP1, all my other updates worked just fine today.... one of those updates should have been(?) the lastest update agent if I didn't have it already (or is this asking too much?)

Here is a link to one such post

Not the same error code(s): Windows Update Agent - Microsoft Answers


Here his the Windows Update Detals:

Windows 7 Service Pack 1 for x64-based Systems (KB976932)
Installation date: ‎3/‎12/‎2011 6:17 PM
Installation status: Failed
Error details: Code 80010108
Update type: Important
Windows 7 Service Pack 1 is a recommended collection of updates and improvements to Windows that are combined into a single installable update. The service pack can help make your computer safer and more reliable. A typical installation will take about 30 minutes to complete, and you will have to restart your computer about halfway through the process.
More information:
What's included in Windows 7 Service Pack 1 (SP1)
Help and Support:
Support for Windows 7 technical problems and troubleshooting

Current state of Windows Update: "Downloading 1 update 0 KB 0% complete"

It's been like that for 15+ minutes. I've canceled a few times, started again. Same results... this time I'll let it run for 'a beer... maybe two'.

I did run the troubleshooting tool (and let it fix the Windows Update problem it found)

I did run the SP1 Readiness Hotfix, the 64bit one in my case.

Downloading shouldn't be the hold up, as I am doing a manual download the .iso and the 64bit version of SP1 in other windows... just in case I need to go that route.

Can this fix I applied to get Office 2007 updates to play nice have anything to do with the problem?

How I fixed Office Update fails with error 646

I ask because, I let the troubleshooting "fix it" tool fix the problem it keeps finding with Windows Update. Then I re-run the tool, and find the same problem again. The problem reports the fix will "Change Windows Update Locations to default settings"

The troubleshooting fix was found via 'run troubleshooter" from this link:

Troubleshoot problems installing a service pack for Windows 7 and Windows Server 2008 R2

The hot fix / system reediness tools has already been applied.

Hello!

Can you please post your C:\Windows\Logs\CBS\CheckSUR.persist.log?

Thanks!

Richard

I'm having the same problem as BostonDriver -- as per niemiro's response, here's the log file I found at: C:\Windows\Logs\CBS (is this the right file?)

2011-03-26 15:00:05, Info CBS Starting TrustedInstaller initialization.
2011-03-26 15:00:05, Info CBS Loaded Servicing Stack v6.1.7601.17514 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17514_none_678566b7ddea04a5\cbscore.dll
2011-03-26 15:00:06, Info CSI 00000001@2011/3/26:22:00:06.587 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee992e94d @0x7fee9be9839 @0x7fee9bb34d3 @0xff0ce94c @0xff0cd769 @0xff0cdaff)
2011-03-26 15:00:06, Info CSI 00000002@2011/3/26:22:00:06.680 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee992e94d @0x7fee9c36806 @0x7fee9c02a9c @0x7fee9bb35a9 @0xff0ce94c @0xff0cd769)
2011-03-26 15:00:06, Info CSI 00000003@2011/3/26:22:00:06.680 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee992e94d @0x7fef0fe8728 @0x7fef0fe8856 @0xff0ce444 @0xff0cd7ae @0xff0cdaff)
2011-03-26 15:00:06, Info CBS Ending TrustedInstaller initialization.
2011-03-26 15:00:06, Info CBS Starting the TrustedInstaller main loop.
2011-03-26 15:00:06, Info CBS TrustedInstaller service starts successfully.
2011-03-26 15:00:06, Info CBS SQM: Initializing online with Windows opt-in: False
2011-03-26 15:00:06, Info CBS SQM: Cleaning up report files older than 10 days.
2011-03-26 15:00:06, Info CBS SQM: Requesting upload of all unsent reports.
2011-03-26 15:00:06, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2011-03-26 15:00:06, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2011-03-26 15:00:06, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2011-03-26 15:00:06, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2011-03-26 15:00:06, Info CBS No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
2011-03-26 15:00:06, Info CBS NonStart: Checking to ensure startup processing was not required.
2011-03-26 15:00:06, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x191f870
2011-03-26 15:00:06, Info CSI 00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
2011-03-26 15:00:06, Info CSI 00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x1f0
2011-03-26 15:00:06, Info CSI 00000007@2011/3/26:22:00:06.883 CSI perf trace:
CSIPERF:TXCOMMIT;104591
2011-03-26 15:00:06, Info CBS NonStart: Success, startup processing not required as expected.
2011-03-26 15:00:06, Info CBS Startup processing thread terminated normally
2011-03-26 15:00:06, Info CSI 00000008 CSI Store 1774864 (0x00000000001b1510) initialized
2011-03-26 15:00:06, Info CBS Session: 30141441_719678931 initialized by client WindowsUpdateAgent.
2011-03-26 15:00:11, Info CBS Archived backup log: C:\Windows\Logs\CBS\CbsPersist_20110326220005.cab.


Thanks for any help!

Well, problem solved itself -- I didn't do anything other than restart the system a couple more times.