cannot update windows service pack 1 for x64 based system (kb976932)

[dede171]

I have tried manually, setting a different restore point, the fix it center. I do not know what else to try

 

[NoelDP]

First clean up the file system


Please run a full CHKDSK and SFC scan....
type in the Search box
CMD.EXE
right-click on the only file that is found
Select Run as Administrator
- the Elevated Command Prompt window should pop up
At the Command prompt, type
CHKDSK C: /R
and hit the Enter key.

You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, and then reboot.

The chkdsk will take a few hours depending on the size
of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally
(possibly after a second auto-reboot) - then run the SFC

SFC -System File Checker - Instructions
Click on the Start button
type in the Search box
CMD.EXE
right-click on the only file that is found
Select Run as Administrator - the Elevated Command Prompt window should pop up
At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages - and then reboot.


Download and install the CheckSUR tool from System Update Readiness Tool that fixes Windows Update problems is available for Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008
make sure that you get the right version


When complete, post the CheckSUR.log file, and the CBS.log file

 

[ScottR02919]

How do I view my CBS.log file? It says 'Access Denied'

 

[NoelDP]

If you want to read the raw CBS.log file you have to copy it to somewhere acessible - the desktop is the usual place. The file itself is in constant use by the system and so inaccessible for normal purposes.

 

[ScottR02919]

thanks, did that, now it just won't respond (notepad) so I can't read it. Any suggestions?

 

[Jacee]

Scott....
Let's see what may be preventing SP1 from installing correctly

clean up ALL temporary files ...download TFC by Old Timer TFC - Temp File Cleaner by OldTimer - Geeks to Go Forums and save it to your desktop.
Save any unsaved work. TFC will close ALL open programs including your browser!
Double-click on TFC.exe to run it. If you are using Vista/Windows 7 right-click on the file and choose Run As Administrator.
Click the Start button to begin the cleaning process and let it run uninterrupted to completion.
Important! If TFC prompts you to reboot, please do so immediately. If not prompted, manually reboot the machine anyway to ensure a complete clean.

Next, I'd like you to scan your machine with ESET OnlineScan

1. Hold down Control and click on the following link to open ESET OnlineScan in a new window.
   ESET OnlineScan
2. Click the
   
   button.
3. For alternate browsers only: (Microsoft Internet Explorer users can skip these steps)
   1. Click on
      
      to download the ESET Smart Installer. Save it to your desktop.
   2. Double click on the
      
      icon on your desktop.
4. Check
   
5. Click the
   
   button.
6. Accept any security warnings from your browser.
7. Check
   
8. Push the Start button.
9. ESET will then download updates for itself, install itself, and begin scanning your computer. Please be patient as this can take some time.
10. When the scan completes, push
    
11. Push
    
    , and save the file to your desktop using a unique name, such as ESETScan. Include the contents of this report in your next reply.
12. Push the
    
    button.
13. Push
    

 

[NoelDP]

Notepad is a lousy reader for anything larger than about 100KB - and your CBS.log file could esily be 10MB.
I use Notepad++ for this - it's very powerful and loads even large files in a snap.

 

[ScottR02919]

Thanks for the help. I ran the programs you mentioned, also did CHK DSK and SFC. Here are the files, if you have time and can offer more options that would help a lot, thanks.

 

[NoelDP]

The CBS log has an impressibely long 'failed' list - but no data from the SFC scan.
Please attach the latest C:\Windows\Logs\CBS\CBSpersistxxxxxxxx.cab file to a reply, and we may be able to see some specifics.

also....

Please run the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Then zip the CheckSUR.log and attach it to your reply

The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.

 

[ScottR02919]

Here is the latest CBSPersist file, there were 5 of them. I compressed it. I am d/l the utility you mentioned and will add that to my next post. Thanks again for the help.

 

[NoelDP]

a 110MB Log file - created in 4 hours!
Incredible.
...and still no SFC results.
can we have the next newest, please?

 

[ScottR02919]

There are 6 files in the CheckSUR folder, none of which are dated today and they are in a sub-directory. The hotfix installed completely, am I missing something?

 

[NoelDP]

Yep
It will have createda CheckSUR.log file in the same folder - please either attach it, or zip and attach it, to your response
Whats the latest CBSPersist.cab file (bear in mind they are named by timestamp - CBSPersistYYYYMMDDtttt )

 

[ScottR02919]

These are the latest results with sfc/scannow and est scanner. I can't make heads or tails out of this. Any suggestions? Is this update really that important? Thanks again.

 

[NoelDP]

The CheckSUR found no problems

I managed to find today's SFC results
There's only the one problem file -

2012-10-31 11:19:35, Info                  CSI    000002f0 [SR] Cannot repair member file [l:16{8}]"msoe.dll" of Microsoft-Windows-Mail-Core-DLL, Version = 6.1.7600.16543, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-10-31 11:19:35, Info                  CSI    000002f1 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-mail-core-dll_31bf3856ad364e35_6.1.7600.16543_none_b49cf6153edc812f\msoe.dll do not match actual file [l:16{8}]"msoe.dll" :
  Found: {l:32 b:PZ9ks7Qp7NKxY6VvxmvhatJtz7c3N66FbCpPp1MLRxI=} Expected: {l:32 b:ejT8LNy4JLgkGRQ8Ycnx3nQzJL6Dd5w/1NrqDQGHQRw=}

I can't honestly seeing that causing your problems - but before we fix it, please let me know if you're using one of the hacks that allows (Vista's) Windows Mail to work in Win7??

 

[ScottR02919]

Yes I am using Windows Mail on Windows 7. I had to do quite a bit to get it working.

 

[NoelDP]

It doesn't usually take very much to get it to work - just changing the msoe.dll is about it, as I recall (never bothered doing myself)
Assuming Windows Mail is currently working, it's probably best to leave this alone.


Please perform a Clean Boot, and then attempt to install SP1...
How to perform a clean boot to troubleshoot a problem in Windows Vista or Windows 7