Update fail w7 x64: KB2758857. Error code 8000FFFF

[silkman]

Hi all,

Instructed to create a new thread for this error.

I am running w7 x64 ultimate.

As per the instructions http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html here are my results

1) SURT
still running

2) sfc /scannow
No problems, nothing in log (no CSI entries)

3) Error code is 8000FFFF, additionally two errors are logged in event viewer when trying to run the update file manually (Windows6.1-KB2758857-x64.msu)

-a- Error: Windows update client
Installation Failure: Windows failed to install the following update with error 0x8000ffff: Security Update for Windows (KB2758857).

-b- Error: WUSA
Windows update "Security Update for Windows (KB2758857)" could not be installed because of error 2147549183 "Catastrophic failure" (Command line: ""C:\Windows\system32\wusa.exe" "D:\Users\xxxxxxx\Downloads\Windows6.1-KB2758857-x64.msu" ")

4) CBS.rar attached

5) Other things tried

Apart from running various microsoft fixit utilities suggested elsewhere, I also tried to run the update with msconfig, selective startup, only windows services active, and of course failed.
http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

 

[NoelDP]

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.

 

[silkman]

Thanks for the fast reply

1) Run chkdsk /r - this took a while (didn't notice any errors because it rebooted)
2) Run sfc /scannow - it completed without errors

Attaching cbs.log (log only, not the same folder as before) and sfcdetails.txt (which is essentially the same file filtered for [SR] entries as per kb929833.

Update still wont install (thank god I had copied cbs.log BEFORE I ran the update because it overwrote all log data)...

 

[NoelDP]

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.

 

[silkman]

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?

 

[NoelDP]

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

 

[davidnnn]

I have a similar problem (8000FFFF) no updates work except a few. I have checked for viruses with AVG IS 2012, MBAM and SB S&D. I have tried every other "solution" and nothing works. I have downloaded it manually as well and it just says it couldn't be installed. HELP.

 

[NoelDP]

David
Please start a NEW thread of your own, before everyone gets confused
Include the data requested in http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html in your initial post.

 

[silkman]

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...

 

[silkman]

Any update on this? I still have this error although other updates install fine through windows update....

PS: happy new year in a few hours

 

[NoelDP]

Sorry - I got side-tracked by the thread hijack, and forgot to come back!

The CBS log you posted shows a huge number of errors in various patch sessions - I think it's a problem with the UpdateAgent. Unfortunately my skills on that re limited, and it's not a patch that can be either uninstalled or repaired easily.
The only thing I can think to do, if you've not tried already, is to rename the SoftwareDistribution Folder, and see if that fixes the problem.

Open an Elevated Command Prompt window, and run the following commands

NET STOP WUAUSERV
REN C:\Windows\SoftwareDistribution SDOLD
NET START WUAUSERV

WAIT 10 minutes - or until you see any disk activity die down - then reboot.

I would recommend disabling SpyBot's TeaTimer if it's running, as well - it can create problems with all sorts of things.

 

[silkman]

Didn't really work

There was another update available which installed ok but the "old" one still won't install...



How is wuauserv relevant if I try to install the update manually via the .msu file and this doesn't work?

Any other ideas maybe?

 

[NoelDP]

Downloading for offline install is always worth a try
That error message is so unspecific that it's no help in troubleshooting.

 

[silkman]

I now have another update that won't install

kb 2726535

Other updates (eg ones for windows defender) install just fine.

I read somewhere that I should use windows dvd, boot with it and select the repair option. Should I try it?

Heeeeelp!

 

[NoelDP]

Defender updates install by a different route - defender pulls them through rather than WU.

OK - so what updates are currently showing in WU after a new Check for Updates, and what are the error messages on the failed updates in Update History?

What error message do you get if you try using the standalone installer for each of the updates that's failed?

 

[silkman]

PART A
From Update History - 2 updates currently showing and these two always fail:

1)Update for Windows (KB2726535)

Installation date: ‎12/‎1/‎2013 2:33 μμ

Installation status: Failed

Error details: Code 8000FFFF

Update type: Important

Fix for KB2726535

More information:
An update is available that adds South Sudan to the list of countries in Windows Server 2008, Windows 7, and Windows Server 2008 R2

Help and Support:
Microsoft Support
***

2)Security Update for Windows 7 for x64-based Systems (KB2758857)

Installation date: ‎10/‎1/‎2013 7:01 μμ

Installation status: Failed

Error details: Code 8000FFFF

Update type: Important

A security issue has been identified that could allow an unauthenticated remote attacker to compromise your system and gain control over it. You can help protect your system by installing this update from Microsoft. After you install this update, you may have to restart your system.

More information:
Microsoft Security Bulletin MS12-081 - Critical : Vulnerability in Windows File Handling Component Could Allow Remote Code Execution (2758857)

Help and Support:
Microsoft Support
*****
PART B
Trying to install manually

1) KB2726535 - Windows6.1-KB2726535-x64.msu
*Event viewer: 4 "Information events" created in application log
a- Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601.17592
P2: Package_for_KB2726535
P3: 6.1.1.1
P4: amd64
P5: unknown
P6: 8000ffff
P7: Execute
P8: Staged
P9: Installed
P10: WindowsUpdateAgent

Attached files:
C:\Windows\Logs\CBS\CbsPersist_20130110040154.cab
C:\Windows\Logs\CBS\CbsPersist_20130110170056.cab
C:\Windows\Logs\CBS\CbsPersist_20130110171535.cab
C:\Windows\Logs\CBS\CbsPersist_20130110172858.cab
C:\Windows\Logs\CBS\CbsPersist_20130112172844.cab
C:\Windows\Logs\CBS\CBS.log
C:\Windows\servicing\Sessions\Sessions.xml
C:\Windows\winsxs\poqexec.log
C:\Windows\inf\setupapi.dev.log

These files may be available here:


Analysis symbol:
Rechecking for solution: 0
Report Id: a59d7e8d-5e8a-11e2-b6f9-005056c00008
Report Status: 0

b-Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601.17592
P2: Package_for_KB2726535
P3: 6.1.1.1
P4: amd64
P5: unknown
P6: 8000ffff
P7: Execute
P8: Staged
P9: Installed
P10: WindowsUpdateAgent

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_6.1.7601.17592_806c7ea442a47330f5d4f79013e84e3ae917eb2a_1ee6ff8b

Analysis symbol:
Rechecking for solution: 0
Report Id: a59d7e8d-5e8a-11e2-b6f9-005056c00008
Report Status: 4

c-Fault bucket , type 0
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601
P2: base\wcp\servicingapi\assembly.cpp
P3: Windows::ServicingAPI::CAssembly::AddUninstall
P4: 572
P5: 8000ffff
P6: 0x96c42cdc
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Logs\CBS\CbsPersist_20130110040154.cab
C:\Windows\Logs\CBS\CbsPersist_20130110170056.cab
C:\Windows\Logs\CBS\CbsPersist_20130110171535.cab
C:\Windows\Logs\CBS\CbsPersist_20130110172858.cab
C:\Windows\Logs\CBS\CbsPersist_20130112172844.cab
C:\Windows\Logs\CBS\CBS.log
C:\Windows\servicing\Sessions\Sessions.xml
C:\Windows\winsxs\poqexec.log
C:\Windows\System32\LogFiles\Scm\SCM.EVM
C:\Windows\Logs\CBS\FilterList.log

These files may be available here:


Analysis symbol:
Rechecking for solution: 0
Report Id: a59d7e8c-5e8a-11e2-b6f9-005056c00008
Report Status: 0

d-Fault bucket , type 0
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601
P2: base\wcp\servicingapi\assembly.cpp
P3: Windows::ServicingAPI::CAssembly::AddUninstall
P4: 572
P5: 8000ffff
P6: 0x96c42cdc
P7:
P8:
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_6.1.7601_1559957ffddbfd3dd4d5a7fcab49d99952accd5_1632fe82

Analysis symbol:
Rechecking for solution: 0
Report Id: a59d7e8c-5e8a-11e2-b6f9-005056c00008
Report Status: 4

*Event viewer: 2 "Information events" and 1 "error event" created in setup log

a-Package KB2726535 failed to be changed to the Installed state. Status: 0x8000ffff.
b-Initiating changes for package KB2726535. Current state is Staged. Target state is Installed. Client id: WindowsUpdateAgent.
c-Windows update "Update for Windows (KB2726535)" could not be installed because of error 2147549183 "Catastrophic failure" (Command line: ""C:\Windows\system32\wusa.exe" "D:\Users\George Silkman\Downloads\Windows6.1-KB2726535-x64.msu" ")

*Event viewer: 1 "Error events" created in system log

Installation Failure: Windows failed to install the following update with error 0x8000ffff: Update for Windows (KB2726535).

***

2)Security Update for Windows 7 for x64-based Systems (KB2758857) - Windows6.1-KB2758857-x64.msu

*as before, Event viewer: 4 "Information events" created in application log

a-Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601.17592
P2: Package_for_KB2758857
P3: 6.1.1.0
P4: amd64
P5: unknown
P6: 8000ffff
P7: Execute
P8: Staged
P9: Installed
P10: WindowsUpdateAgent

Attached files:
C:\Windows\Logs\CBS\CbsPersist_20130110040154.cab
C:\Windows\Logs\CBS\CbsPersist_20130110170056.cab
C:\Windows\Logs\CBS\CbsPersist_20130110171535.cab
C:\Windows\Logs\CBS\CbsPersist_20130110172858.cab
C:\Windows\Logs\CBS\CbsPersist_20130112172844.cab
C:\Windows\Logs\CBS\CBS.log
C:\Windows\servicing\Sessions\Sessions.xml
C:\Windows\winsxs\poqexec.log
C:\Windows\inf\setupapi.dev.log

These files may be available here:


Analysis symbol:
Rechecking for solution: 0
Report Id: 21e74032-5e8c-11e2-b6f9-005056c00008
Report Status: 0

b-Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601.17592
P2: Package_for_KB2758857
P3: 6.1.1.0
P4: amd64
P5: unknown
P6: 8000ffff
P7: Execute
P8: Staged
P9: Installed
P10: WindowsUpdateAgent

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_6.1.7601.17592_463fa79ac05c2da7e679b3d5121873fb592d1c68_1c10b9a8

Analysis symbol:
Rechecking for solution: 0
Report Id: 21e74032-5e8c-11e2-b6f9-005056c00008
Report Status: 4

c-Fault bucket , type 0
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601
P2: base\wcp\servicingapi\assembly.cpp
P3: Windows::ServicingAPI::CAssembly::AddUninstall
P4: 572
P5: 8000ffff
P6: 0x96c42cdc
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Logs\CBS\CbsPersist_20130110040154.cab
C:\Windows\Logs\CBS\CbsPersist_20130110170056.cab
C:\Windows\Logs\CBS\CbsPersist_20130110171535.cab
C:\Windows\Logs\CBS\CbsPersist_20130110172858.cab
C:\Windows\Logs\CBS\CbsPersist_20130112172844.cab
C:\Windows\Logs\CBS\CBS.log
C:\Windows\servicing\Sessions\Sessions.xml
C:\Windows\winsxs\poqexec.log
C:\Windows\System32\LogFiles\Scm\SCM.EVM
C:\Windows\Logs\CBS\FilterList.log

These files may be available here:


Analysis symbol:
Rechecking for solution: 0
Report Id: 21e74031-5e8c-11e2-b6f9-005056c00008
Report Status: 0

d- Fault bucket , type 0
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 6.1.7601
P2: base\wcp\servicingapi\assembly.cpp
P3: Windows::ServicingAPI::CAssembly::AddUninstall
P4: 572
P5: 8000ffff
P6: 0x96c42cdc
P7:
P8:
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_6.1.7601_1559957ffddbfd3dd4d5a7fcab49d99952accd5_0ac8b95a

Analysis symbol:
Rechecking for solution: 0
Report Id: 21e74031-5e8c-11e2-b6f9-005056c00008
Report Status: 4

*As before 2 information and 1 error event(s) in setup log
a-Initiating changes for package KB2758857. Current state is Staged. Target state is Installed. Client id: WindowsUpdateAgent.
b-Package KB2758857 failed to be changed to the Installed state. Status: 0x8000ffff.
c-Windows update "Security Update for Windows (KB2758857)" could not be installed because of error 2147549183 "Catastrophic failure" (Command line: ""C:\Windows\system32\wusa.exe" "D:\Users\George Silkman\Downloads\Windows6.1-KB2758857-x64 (2).msu" ")

*As before 1 error event in system event log

Installation Failure: Windows failed to install the following update with error 0x8000ffff: Security Update for Windows (KB2758857).

***********Hope these are clear enough; I have also posted in microsoft answers where there are many others with the same issue

 

[NoelDP]

Historically, 0x8000ffff errors are one of the hardest to cure, and sometime require a repair install.

Before we do that - please run the following commands in an elevated command prompt, and post the results.


REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\PendingXmlIdentifier
REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\NextQueueEntryIndex
REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\AdvancedInstallersNeedResolving

(It's likely that they will all come back with errors, unless you do this immediately after a reboot - and possibly even then, as the COMPONENTS hive is unloaded soon after booting is complete)

 

[silkman]

Thanks for taking the time to still try to make this work!!!

REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\PendingXmlIdentifier
ERROR: The system was unable to find the specified registry key or value.

REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\NextQueueEntryIndex
ERROR: The system was unable to find the specified registry key or value.

REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\AdvancedInstallersNeedResolving
ERROR: The system was unable to find the specified registry key or value.

**Edit
Thought about creating a batch file and running in on startup to write the results to a text file however for some strange reason this command doesnt write anything to the text file

REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\PendingXmlIdentifier >>c:\noel.txt

Should I try a repair install from dvd? I have backups in case something goes wrong...

 

[NoelDP]

No - it was just an off-chance try (I'm not even sure that key exists in Windows 7 - it may have been moved)

See if the C:\Windows\winsxs\poqexec.log file still exists - if it does, please attach it to a reply. (I have NO idea how to read it - but we'll see what we can find)
If it doesn't, see if you can find it in the Action Center Reliability history - find the install, and click on the link in the display.

 

[silkman]

poqexec.log

1cd08b30781a9de: 0, 0, 0, 0, StartTime ;
1cd08b307b3bb40: 0, 0, 0, 0, EndTime ;
1cd08919d083be6: 0, 0, 0, 0, StartTime ;
1cd08919eb7c588: 0, 0, 0, 0, CriticalPOQComplete ;
1cd0891b1274473: 0, 0, 0, 0, EndTime ;
1cd089713ef64d7: 0, 0, 0, 0, StartTime ;
1cd089719ab2886: 0, 0, 0, 0, EndTime ;
1cd08983e529ed9: 0, 0, 0, 0, StartTime ;
1cd089843a7911e: 0, 0, 0, 0, EndTime ;
1cd09061b923c8d: 0, 0, 0, 0, StartTime ;
1cd09061d2c5105: 0, 0, 0, 0, EndTime ;
1cd09a1fb6cd5f9: 0, 0, 0, 0, StartTime ;
1cd09a1fde242c9: 0, 0, 0, 0, EndTime ;
1cd17cba8749528: 0, 0, 0, 0, StartTime ;
1cd17cbaa1a9562: 0, 0, 0, 0, EndTime ;
1cd2debb4cae676: 0, 0, 0, 0, StartTime ;
1cd2debb587403c: 0, 0, 0, 0, EndTime ;
1cd499cbeb2d810: 0, 0, 0, 0, StartTime ;
1cd499cc425bdd0: 0, 0, 0, 0, EndTime ;
1cd51e14d4223a0: 0, 0, 0, 0, StartTime ;
1cd51e14d9ef940: 0, 0, 0, 0, EndTime ;
1cd5f526204e9e2: 0, 0, 0, 0, StartTime ;
1cd5f526838c806: 0, 0, 0, 0, EndTime ;
1cd7bad14f3dd32: 0, 0, 0, 0, StartTime ;
1cd7bad1c5685fc: 0, 0, 0, 0, EndTime ;
1cd910569ff56d0: 0, 0, 0, 0, StartTime ;
1cd91056b8819b0: 0, 0, 0, 0, EndTime ;
1cd931f394a5370: 0, 0, 0, 0, StartTime ;
1cd931f39e50cd0: 0, 0, 0, 0, EndTime ;
1cd98266830d4ba: 0, 0, 0, 0, StartTime ;
1cd98266d2ec12a: 0, 0, 0, 0, EndTime ;
1cda6fb604a41b6: 0, 0, 0, 0, StartTime ;
1cdc2d1b1a425c1: 0, 0, 0, 0, StartTime ;
1cdc2d1b61a2c27: 0, 0, 0, 0, EndTime ;
1cdc4b0cef3a512: 0, 0, 0, 0, StartTime ;
1cdc4b0cf4979ba: 0, 0, 0, 0, EndTime ;
1cdcfa9a452a28e: 0, 0, 0, 0, StartTime ;
1cdcfa9a46cdc6c: 0, 0, 0, 0, EndTime ;
1cdd9586b1733b4: 0, 0, 0, 0, StartTime ;
1cdd9586ec4f492: 0, 0, 0, 0, EndTime ;
1cddc78970414f6: 0, 0, 0, 0, StartTime ;
1cddc789c06c61a: 0, 0, 0, 0, EndTime ;
1cde14dbccd6255: 0, 0, 0, 0, StartTime ;
1cde14dbdc2f48b: 0, 0, 0, 0, EndTime ;
1cdef5010755f3d: 0, 0, 0, 0, StartTime ;
1cdef5011f9fe8b: 0, 0, 0, 0, EndTime ;