Windows 7 Update error 800706BA

ptrthgr8 · 08 Nov 2014

Hi there. I've been dealing with a Win7 update issue for a few days now. Here's what happened...

On 4 November I attempted to install a new nvidia driver (344.60) for my GTX 970. It caused issues. I ended up needing to do a few reinstalls of older drivers and a couple of restores before I was finally able to get the new driver (344.60) up and running. Everything was fine as far as I could tell, until I checked my Windows updates and I noticed that the updates were no longer current - everything had been current up to the nvidia driver issues I encountered, but after all of the various driver reinstalls and system restores nothing was updated since 16 October. The update history now shows a ton of failed installation attempts from 17 October through today (8 November). I assumed there were some wonky registry entries after all of those driver installs and restores, so I ran the registry cleaner in CCleaner (v4.19.4867) and then to make sure I didn't have some weird virus or malware issues I ran complete scans with Malwarebytes (2.0.3.1025) and Trend Micro Internet Security 2015 - no issues were found.

There are 5 updates I'm trying to install. See updatelist.png

I've tried installing all 5 at the same time and also tried installing each individually, but they all error out and give me error code 800706BA. See update1.png.

I followed the instructions and ran SURT (KB947821). It appears to have installed successfully. See updatehistory5.png.

I ran sfc /scannow 4 times (twice in safemode) and it hangs at "Verification 100% complete." I let it hang at that point for an hour and nothing happened.

I've attached the zipped CBS log..

My machine appears to be running fine otherwise, but at this point I'm at a complete loss as to how to resolve this issue. Any help will be greatly appreciated.

Thanks!

~ Greg ~

NoelDP · 08 Nov 2014

Here's the beginning of a VERY long error chain...

Code:

2014-11-08 02:45:54, Info                  CBS    Appl: Evaluating package applicability for package Package_74_for_KB2923545~31bf3856ad364e35~amd64~~6.1.1.1, applicable state: Absent
2014-11-08 02:45:54, Info                  CBS    Plan: Skipping package since its start state and target state are both absent for package: Package_74_for_KB2923545~31bf3856ad364e35~amd64~~6.1.1.1, current: Absent, pending: Default, start: Absent, applicable: Absent, targeted: Absent, limit: Staged
2014-11-08 02:45:54, Info                  CBS    Perf: Resolve chain started.
2014-11-08 02:45:54, Info                  CSI    0000000f@2014/11/8:08:45:54.431 CSI Transaction @0x12032b0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [79]"TI1.30407472_1732183834:2/Package_for_KB2923545~31bf3856ad364e35~amd64~~6.1.1.1"
2014-11-08 02:45:54, Info                  CBS    Failed call to CryptCATAdminAddCatalog. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:45:54, Info                  CBS    Failed to install catalog file \\?\C:\Windows\SoftwareDistribution\Download\f494723c873b677476f3e1aa8354fabd\update.cat for package [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:45:54, Info                  CBS    Failed to install catalog for package: Package_for_KB2923545~31bf3856ad364e35~amd64~~6.1.1.1 [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:45:54, Info                  CBS    Failed to stage package manifest. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:45:54, Info                  CBS    Failed to add package. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]

... and the end...

Code:

2014-11-08 02:49:15, Info                  CBS    Failed to stage package manifest. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:49:15, Info                  CBS    Failed to add package. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:49:15, Info                  CBS    Failed to persist package: Package_2_for_KB2994023~31bf3856ad364e35~amd64~~6.1.1.1. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:49:15, Info                  CBS    Failed to update states and store all resolved packages. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:49:15, Info                  CSI    00000328@2014/11/8:08:49:15.677 CSI Transaction @0x17310b0 destroyed
2014-11-08 02:49:15, Info                  CBS    Perf: Resolve chain complete.
2014-11-08 02:49:15, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]
2014-11-08 02:49:15, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800706ba - RPC_S_SERVER_UNAVAILABLE]

Your SFC scans appear to have fallen off into the CBSPersist files - please post the last 2 or 3 of them.

ptrthgr8 · 08 Nov 2014

Hi, Noel.

Thanks for the quick reply. I may not have let SFC run long enough... I was letting it hang at the 100% complete status for nearly an hour. After I posted here I let it run again, but then I went to bed; it ran overnight and when I got to my machine this morning the output showed that it had completed, found some corrupt files, but was unable to fix some of them, etc. I've attached the new CBS log in case that has more info.

You're right - there were a few CBS persist logs (5 files total, about 58MB worth), but they all look to be from before the last scan completed. (See cbspersistlist.png) Please let me know if you still need these even though the scan completed. (I actually ran sfc again while I was drafting this and it completed again pretty quickly this time, though still unable to fix some of the corrupted files.)

Thanks again, Noel.

~ Greg ~

NoelDP · 08 Nov 2014

Here's the SFC results from this scan...

Code:

2014-11-08 11:41:01, Info                  CSI    00000341 [SR] Repairing 1 components
2014-11-08 11:41:01, Info                  CSI    00000342 [SR] Beginning Verify and Repair transaction
2014-11-08 11:41:01, Info                  CSI    00000343 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-nlasvc_31bf3856ad364e35_6.1.7601.17964_none_c575f33221b24ff7\nlasvc.dll do not match actual file [l:20{10}]"nlasvc.dll" :
  Found: {l:32 b:a0/ddLuB4SvUslo+iuyw+nf6AHXUVN0dbcF5Ct8fKqg=} Expected: {l:32 b:4j8ySRNVSiPNBD3SfUMFr2L0jAVhoPx7eBHlW3Sxvnk=}
2014-11-08 11:41:01, Info                  CSI    00000344 [SR] Cannot repair member file [l:20{10}]"nlasvc.dll" of Microsoft-Windows-NlaSvc, Version = 6.1.7601.17964, 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
2014-11-08 11:41:01, Info                  CSI    00000345 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-nlasvc_31bf3856ad364e35_6.1.7601.17964_none_c575f33221b24ff7\nlasvc.dll do not match actual file [l:20{10}]"nlasvc.dll" :
  Found: {l:32 b:a0/ddLuB4SvUslo+iuyw+nf6AHXUVN0dbcF5Ct8fKqg=} Expected: {l:32 b:4j8ySRNVSiPNBD3SfUMFr2L0jAVhoPx7eBHlW3Sxvnk=}
2014-11-08 11:41:01, Info                  CSI    00000346 [SR] Cannot repair member file [l:20{10}]"nlasvc.dll" of Microsoft-Windows-NlaSvc, Version = 6.1.7601.17964, 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
2014-11-08 11:41:01, Info                  CSI    00000347 [SR] This component was referenced by [l:156{78}]"Package_4_for_KB2750841~31bf3856ad364e35~amd64~~6.1.1.3.2750841-21_neutral_GDR"
2014-11-08 11:41:01, Info                  CSI    00000348 Hashes for file member \??\C:\Windows\System32\nlasvc.dll do not match actual file [l:20{10}]"nlasvc.dll" :
  Found: {l:32 b:a0/ddLuB4SvUslo+iuyw+nf6AHXUVN0dbcF5Ct8fKqg=} Expected: {l:32 b:4j8ySRNVSiPNBD3SfUMFr2L0jAVhoPx7eBHlW3Sxvnk=}
2014-11-08 11:41:01, Info                  CSI    00000349 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-nlasvc_31bf3856ad364e35_6.1.7601.17964_none_c575f33221b24ff7\nlasvc.dll do not match actual file [l:20{10}]"nlasvc.dll" :
  Found: {l:32 b:a0/ddLuB4SvUslo+iuyw+nf6AHXUVN0dbcF5Ct8fKqg=} Expected: {l:32 b:4j8ySRNVSiPNBD3SfUMFr2L0jAVhoPx7eBHlW3Sxvnk=}
2014-11-08 11:41:01, Info                  CSI    0000034a [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"nlasvc.dll"; source file in store is also corrupted
2014-11-08 11:41:01, Info                  CSI    0000034b Repair results created:
POQ 143 starts:
 
POQ 143 ends.
2014-11-08 11:41:01, Info                  CSI    0000034c [SR] Repair complete

I'll post a fix a little later.

NoelDP · 08 Nov 2014

I've uploaded a file - pt8aa.zip - to my OneDrive at Noel'sOneDrive

Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract

Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced BootMenu, at the top of which should be the option'Repair my Computer'

Pick that

You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type

DIR C:\pt8aa

hit the enter key- if you get a 'Not Found' error try

DIR D:\pt8aa

or

DIR E:\pt8aa

The drive letterin use when you find the folder will need to be substituted (for<drive>)into the following command...

XCOPY <drive>:\hznaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPYP:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type

EXIT

and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt

then reboot and upload the new CBS.log file to your reply

ptrthgr8 · 09 Nov 2014

Thanks, Noel.

I just ran through the instructions. The xcopy step resulted in 4 files being copied over. When I ran scannow again it still found some corrupted files that couldn't be repaired. The new CBS log is attached.

Thanks again!

~ Greg ~

NoelDP · 10 Nov 2014

According to the SFC results, the file system should be fine now - it found and fixed one error - and nothing else was found..

Please post the CheckSUR.log file

ptrthgr8 · 10 Nov 2014

Hi, Noel.

I don't see a CheckSUR.log file in the CheckSUR directory. I've attached screenshots of the directory for your reference.

I also attempted to run the updates again this morning and it errored out again - but with a different error number this time. Screenshot attached.

Thanks!

~ Greg ~

NoelDP · 10 Nov 2014

The CheckSUR log is in the C:\Windows\Logs\CBS folder - or should be!

ptrthgr8 · 10 Nov 2014

Hmm... I swear I looked there, but I don't recall seeing it. But it *was* very early in the morning and I'm trying to get over a case of Space Ebola that my wife gave to me, so I wouldn't be surprised if I overlooked it. I'm at work at the moment and will check when I get back home later today.

Thanks, Noel.