Update fail w7 x64: KB2758857. Error code 8000FFFF

Your CBS logfiles are generating at a very high speed - and it's therefore likely that you have a huge amount of corruption.
There is no CheckSUR data in your upload - either you uploaded before it ran, or it failed before being able to generate a log.

please try again......

Please run a full CHKDSK and SFC scan....

Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - 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 Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - 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.


Copy the CBS.log file created (C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate it directly) and then compress the copy and attach it to your reply.

CBS.log data is never over-written - when teh file gets too big, it's archived in the persist file, and eventually deleted
The SFCDETAILS log is very uninformative - which is why I asked for the full CBS.log file. There are a very large number of failure points within that file, which probably indicates a Components failure.

I suggest that you run the CheckSUR tool again, and post teh CheckSUR.log amd CheckSUR.persist.log files and we'll see if there's anything there that we can deal with.

Hi

Copying from checksur.log (and checksurpersist.log which has the same information) in c:\windows\logs\cbs

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 17.0
2012-12-14 18:52

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 967
No errors detected

**eof

Apparently the way to run sur again is to reinstall it?

What should I do? Try to install sp1 again? Any other ideas?

There's not much pointinstalling from WU at the moment, as neither SFC nor CheckSUR found any problems to fix (although I have seen even negative runs produce positive results).

See what happens if you download the update from the KB, and try installing that....
Download Security Update for Windows 7 for x64-based Systems (KB2758857) from Official Microsoft Download Center

David
Please start a NEW thread of your own, before everyone gets confused :)
Include the data requested in Windows Update Posting Instructions in your initial post.

NoelDP said:

There's not much pointinstalling from WU at the moment, as neither SFC nor CheckSUR found any problems to fix (although I have seen even negative runs produce positive results).

See what happens if you download the update from the KB, and try installing that....
Download Security Update for Windows 7 for x64-based Systems (KB2758857) from Official Microsoft Download Center

Thanks but I have also tried that long ago - sorry if it's not clear in my initial post...

I also tried to install it manually with /log:c:\temp/log.txt , it creates a log file but it is not readable with a text editor, no idea how to open it... Attaching it in any case

Any other ideas? It's only this update, the others were working fine...