Windows Update fails repeatedly. Codes 8007054F, 9C59, 800F0826

NickFrancis · 13 Apr 2014

Hi
Just wondering if there's any update, or whether we've reached a dead-end with this one? Still having no luck installing updates.

I really appreciate the time you've put into this. If it's time to do a fresh install then I guess that's what I'll have to do.

Thanks

Nick :)

NoelDP · 13 Apr 2014

Ooops! sorry - your thread got buried on my list

The WIndowsUpdate log is as usual, totally impenetrable - but has lots of errors of this sort...

Code:

2014-03-31 22:49:21:541  740 129c PT WARNING: Initialization failed for Protocol Talker Context: 0x80248014
2014-03-31 22:49:21:541  740 129c PT WARNING: PTError: 0x80248014

There's not a lot about it on the internet that makes sense

(at least, to me!)

The conventional response is to rename the SoftwareDistribution folder... which we don't appear to have done yet, so now would be a good time :)

Open an Elevated Command Prompt
Run the following commands

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

reboot
then wait 10 minutes, and open Windows Updates, and run a Check for Updates.

Install only the oldest update found - and reboot once installed
then go back to Windows updates and install the others.

NickFrancis · 13 Apr 2014

Thank you - don't worry about the post getting lost. I understand! Thank you for replying so promptly. Sorry I've been slow getting back to you - playing with the kids :)

Tried your suggestiongs, updates failed again

Code:

Update for Windows 7 for x64-based Systems (KB2592687)

Installation date: ‎13/‎04/‎2014 17:01

Installation status: Failed

Error details: Code 8007054F

Update type: Optional

The Remote Desktop Protocol 8.0 update enables you to use the new Remote Desktop 
Services features. These features are introduced in Windows 8 and in Windows Server 
2012 and are available for computers that are running Windows 7 Service Pack 1 or 
Windows Server 2008 R2 Service Pack 1. After you install this item, you may have to 
restart your computer.

I've attached the Windows Update log if it's useful.

Thanks

Nick

NickFrancis · 13 Apr 2014

Quick update - looked on the MS Website which said there was a dependency needed for that update - checked that & I do have it (manually downloaded & it wouldn't install as it was already installed)

NoelDP · 13 Apr 2014

The CBS log is a bit of a minefield...

Code:

 Line 192831: 2014-04-13 17:03:42, Error                 CSI    00000001 (F) Logged @2014/4/13:16:03:42.384 : [ml:322{161},l:320{160}]"events installer: online=1, install=0, component=amd64_Microsoft-Windows-TerminalServices-USBRedirectorClient_31bf3856ad364e35_6.1.7601.17514_neutral_release__."
 Line 192833: 2014-04-13 17:03:42, Error                 CSI    00000002 (F) Logged @2014/4/13:16:03:42.416 : [ml:200{100},l:198{99}]"EventAITrace:Provider {ae5cf422-786a-476a-ac96-753b05877c99} is missing the name in the registry.
 Line 192837: 2014-04-13 17:03:42, Error                 CSI    00000003 (F) Logged @2014/4/13:16:03:42.431 : [ml:294{147},l:292{146}]"EventAITrace:Provider Microsoft-Windows-Direct3D11{{db6f6ddb-ac77-4e88-8253-819df9bbf140}} is missing the channel name for the index key (null).
 Line 192841: 2014-04-13 17:03:42, Error                 CSI    00000004 (F) Logged @2014/4/13:16:03:42.494 : [ml:200{100},l:198{99}]"EventAITrace:Provider {ae5cf422-786a-476a-ac96-753b05877c99} is missing the name in the registry.
 Line 192845: 2014-04-13 17:03:42, Error                 CSI    00000005 (F) Logged @2014/4/13:16:03:42.494 : [ml:294{147},l:292{146}]"EventAITrace:Provider Microsoft-Windows-Direct3D11{{db6f6ddb-ac77-4e88-8253-819df9bbf140}} is missing the channel name for the index key (null).
 Line 193052: 2014-04-13 17:03:47, Error                 CSI    0000000c (F) Logged @2014/4/13:16:03:47.439 : [ml:322{161},l:320{160}]"events installer: online=1, install=1, component=amd64_Microsoft-Windows-TerminalServices-USBRedirectorClient_31bf3856ad364e35_7.1.7601.16398_neutral_release__."
 Line 193054: 2014-04-13 17:03:47, Error                 CSI    0000000d (F) Logged @2014/4/13:16:03:47.470 : [ml:200{100},l:198{99}]"EventAITrace:Provider {ae5cf422-786a-476a-ac96-753b05877c99} is missing the name in the registry.
 Line 193058: 2014-04-13 17:03:47, Error                 CSI    0000000e (F) Logged @2014/4/13:16:03:47.486 : [ml:170{85},l:168{84}]"WmiCmiPlugin wevtcfg.cpp(1856): InstrumentationManifestAssert failed. HR=0x8007054f."
 Line 193060: 2014-04-13 17:03:47, Error                 CSI    0000000f (F) Logged @2014/4/13:16:03:47.486 : [ml:166{83},l:164{82}]"WmiCmiPlugin eventloghandler.cpp(192): ProcessEventsInstall failed. HR=0x8007054f."
........................
........................
 Line 193913: 2014-04-13 17:07:41, Error                 CSI    0000000e (F) Logged @2014/4/13:16:07:41.121 : [ml:170{85},l:168{84}]"WmiCmiPlugin wevtcfg.cpp(1856): InstrumentationManifestAssert failed. HR=0x8007054f."
 Line 193915: 2014-04-13 17:07:41, Error                 CSI    0000000f (F) Logged @2014/4/13:16:07:41.121 : [ml:166{83},l:164{82}]"WmiCmiPlugin eventloghandler.cpp(192): ProcessEventsInstall failed. HR=0x8007054f."
 Line 193917: 2014-04-13 17:07:41, Error                 CSI    00000010 (F) Logged @2014/4/13:16:07:41.121 : [ml:170{85},l:168{84}]"WmiCmiPlugin eventloghandler.cpp(212): EventLogHandlerInstall failed. HR=0x8007054f."
 Line 193919: 2014-04-13 17:07:41, Error                 CSI    00000011@2014/4/13:16:07:41.153 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR)
 Line 193926: 2014-04-13 17:07:41, Error                 CSI    00000012@2014/4/13:16:07:41.153 (F) CMIADAPTER: AI failed. HRESULT = HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR)
 Line 193995: 2014-04-13 17:07:41, Error                 CSI    te>
 Line 194070: 2014-04-13 17:07:41, Error                 CSI    ror" message="$(string.event_TRACE_DUMP)" symbol="TRACE_DUMP" task="TSUSBFLT" template="debugTrace" value="0x00000008" />
 Line 194094: 2014-04-13 17:07:41, Error                 CSI    00000054@2014/4/13:16:07:41.153 (F) d:\win7sp1_gdr\base\wcp\cmiadapter\installers.cpp(352): Error HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR) originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::ResolveAndInvokeInstaller expression: hr
 Line 194096: 2014-04-13 17:07:52, Error                 CSI    00000013@2014/4/13:16:07:52.790 (F) CMIADAPTER: Exiting with HRESULT code = HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR).
 Line 194098: 2014-04-13 17:07:52, Error                 CSI    00000055@2014/4/13:16:07:52.790 (F) d:\win7sp1_gdr\base\wcp\cmiadapter\installers.cpp(123): Error HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR) originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::Install expression: hr
 Line 194104: 2014-04-13 17:07:53, Error      [0x01802b] CSI    00000058 (F) Failed execution of queue item Installer: Events ({3bb9fd2b-351e-4b9c-b1fc-ed0758805998}) with HRESULT HRESULT_FROM_WIN32(ERROR_INTERNAL_ERROR).  Failure will be ignored: The failure was encountered during rollback; installer is reliable (2)[gle=0x80004005]

Note the last line!

The first line is preceded by these notes...

Code:

2014-04-13 17:03:41, Info                  CSI    0000000c Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:fe19abf03157cf010100000090017404} pathid: {l:16 b:fe19abf03157cf010200000090017404} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-t..usbredirectorclient_31bf3856ad364e35_6.1.7601.17514_none_0524abf5e1674c7c" pid: 190 starttime: 130418785949828360 (0x01cf5731e093c508)
2014-04-13 17:03:42, Info                  CSI    0000000d Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:bedcaff03157cf010300000090017404} pathid: {l:16 b:bedcaff03157cf010400000090017404} path: [l:238{119}]"\SystemRoot\WinSxS\amd64_microsoft-windows-t..usbredirectorclient_31bf3856ad364e35_7.1.7601.16398_none_f642bcff6c8b2640" pid: 190 starttime: 130418785949828360 (0x01cf5731e093c508)
2014-04-13 17:03:42, Info                  CSI    0000000e Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:83b5daf03157cf010500000090017404} pathid: {l:16 b:83b5daf03157cf010600000090017404} path: [l:220{110}]"\SystemRoot\WinSxS\amd64_microsoft-windows-wmi-cmiplugin_31bf3856ad364e35_6.1.7601.17514_none_1b28925642a756f7" pid: 190 starttime: 130418785949828360 (0x01cf5731e093c508)

This may be a permissions issue - possibly in the registry.

I'll see what I can work out.

NickFrancis · 13 Apr 2014

Thank you!

Just a thought: if it's regarding permissions would it have anything to do with me changing the admin account name & user folder name?

NoelDP · 13 Apr 2014

I don't think so - most of the actions are done by TrustedInstaller rather than the user themselves.

NickFrancis · 17 Apr 2014

Ok, just thought I'd mention it. Will wait to hear back. :)

NoelDP · 18 Apr 2014

With luck this will fix at least some of the problems....

I've uploaded a file - nfsaa.zip - to my OneDrive at Noel's OneDrive

Please download and save it to your desktop.

Right-click on the saved file and select Extract all...

Save it to the default location

This should create a file nfsaa.reg (in a folder nfsaa)

right-click on the file, and select Merge

Accept the warnings, - you should then get a 'Success' message.

Close all windows, and reboot.

attempt an SFC and CheckSUR (don't be surprised if they fail) and post the new CBS folder (compressed) - we'll see how that's worked.

NickFrancis · 18 Apr 2014

Thank you.

Have done as instructed - CBS zip file attached.

To get the CBS zip file to the required size I had to delete some files from the folder - they were Cabinet files - CBS.Persist.<timeanddate> - don't know if they're important but they were too large.