Solved Error codes 800B0100 and 8007065E

[monday69]

Having done a clean install with my win 7 64-bit desktop and cured a problem I now have Windows update problems and keep getting error codes 800B0100 & 8007065E
NoelDP gave a successful solution for someone else 720 days ago. It looks extremely complicated and involved many questions and answers between NoelDP and Siansheric, so I wonder if there is now an easier answer? The computer seems ok but 4 important updates will not install
Thanks

 

[monday69]

I have found out a little more. (I'm the one with the problem!) I spotted that Windows.microsoft.com recommended checking CheckSUR.log located in C:\Windows\Logs\CBS after running the SURT (several times) I found the following in the log:

Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-04-04 02:28

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat

Then a bit later:
Summary:
Seconds executed: 393
Found 18 errors
CSI Manifest All Zeros Total count: 8
CBS MUM Corrupt Total count: 5
CBS Catalog Corrupt Total count: 5

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_f27bfa1981fd5c4e.manifest
winsxs\manifests\amd64_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_b3d45a96e36fc54b.manifest
winsxs\manifests\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.22913_none_73597611f579c664.manifest
winsxs\manifests\x86_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_57b5bf132b125415.manifest
winsxs\manifests\x86

Can I do anything about this? I have a laptop with WIN7 64-bit on it. Could I copy files across, or would it be easier to re-install?

 

[NoelDP]

Please post the ENTIRE CheckSUR.log file - there are large sections missing.
I can then post a fix protocol for you.

 

[monday69]

Good to hear from you. Having done plenty of internet searching I see that this problem has come up quite often and you are THE expert on it! Entire log file coming up shortly.

 

[monday69]

Here it is:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-04-04 02:28

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_f27bfa1981fd5c4e.manifest amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_f27bfa1981fd5c4e
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_b3d45a96e36fc54b.manifest amd64_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_b3d45a96e36fc54b
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.22913_none_73597611f579c664.manifest amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.22913_none_73597611f579c664
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_57b5bf132b125415.manifest x86_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_57b5bf132b125415
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_965d5e95c99feb18.manifest x86_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_965d5e95c99feb18
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.18706_none_72dda82adc515987.manifest amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.18706_none_72dda82adc515987
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-webdavredir-clientonly_31bf3856ad364e35_6.1.7601.22913_none_35f3367c25772c2d.manifest amd64_microsoft-windows-webdavredir-clientonly_31bf3856ad364e35_6.1.7601.22913_none_35f3367c25772c2d
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\wow64_microsoft-windows-webdavredir-clientonly_31bf3856ad364e35_6.1.7601.22913_none_4047e0ce59d7ee28.manifest wow64_microsoft-windows-webdavredir-clientonly_31bf3856ad364e35_6.1.7601.22913_none_4047e0ce59d7ee28

Summary:
Seconds executed: 393
Found 18 errors
CSI Manifest All Zeros Total count: 8
CBS MUM Corrupt Total count: 5
CBS Catalog Corrupt Total count: 5

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_f27bfa1981fd5c4e.manifest
winsxs\manifests\amd64_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_b3d45a96e36fc54b.manifest
winsxs\manifests\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.22913_none_73597611f579c664.manifest
winsxs\manifests\x86_microsoft-windows-webdavredir-webclient_31bf3856ad364e35_6.1.7601.22913_none_57b5bf132b125415.manifest
winsxs\manifests\x86_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.1.7601.22913_none_965d5e95c99feb18.manifest
winsxs\manifests\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_6.1.7601.18706_none_72dda82adc515987.manifest
winsxs\manifests\amd64_microsoft-windows-webdavredir-clientonly_31bf3856ad364e35_6.1.7601.22913_none_35f3367c25772c2d.manifest
winsxs\manifests\wow64_microsoft-windows-webdavredir-clientonly_31bf3856ad364e35_6.1.7601.22913_none_4047e0ce59d7ee28.manifest
servicing\packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_1_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_2_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_3_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB3019215_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat
servicing\packages\Package_for_KB3019215~31bf3856ad364e35~amd64~~6.1.1.1.cat

 

[NoelDP]

I've uploaded a file - m69aa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder m69aa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[monday69]

Thank you for your efforts. All went well until I tried to open C:\Windows\Temp I constantly got the Access is denied message. Before that it would show, "An error occurred while applying security information to C:\Windows\Temp, Access is denied" I tried everything, I think. Even when it accepted my changes to security selections it would allow me to progress then report "Unable to save permission changes on Temp". However I restarted in Safe Mode and found I could get into Temp. I could copy and paste so I think I could carry out your instructions in Safe Mode. But I lost my nerve! Would it be ok to copy into Packages and Manifests in Safe mode then return to normal mode to use the CheckSUR tool?

 

[NoelDP]

It's certainly worth trying!
This is the second case of this problem inside a week - what Anti-Virus are you using?
What other security software is installed?

 

[monday69]

According to action Center "WIN firewall is actively protecting your computer; avast! Antivirus reports that it is up to date and virus scanning is on; Windows Defender and avast! Antivirus both report that they are turned on. Note: Running two or more antispyware programs at the same time can cause your computer to run slowly; All internet security settings are set to their recommended levels; Network Access Protection Agent service is not running"

I will try the Safe mode approach shortly and let you, but I may have to go and be sociable for a few hours!

 

[NoelDP]

Hmmm - it's unusual for both WinDefend and another anti-virus to be running at the same time, and the other case I've had of this problem this week is also showing the same AV, and having Defender active.
Try disabling Windows Defender - does the system then allow access?

 

[monday69]

Turned Windows Defender off; still no access, even after rebooting

 

[NoelDP]

OK, turn Avast off as well - does that enable access?

 

[monday69]

Unfortunately not. Both off still no access.

 

[NoelDP]

Have you ever had any other AV installed? (Norton? McAfee??) - turn Avast back on!

 

[monday69]

Haven't paid for a long time. Previously I had AVG free. I have recently done a clean install to get rid of a problem, successfully. My first re-install left me with the same problem (computer running slowly at first) so I installed WIN7 temporarily on Disk 1, used that to format disk C that happened to be a SSD then installed WIN 7 on C. I was pleased to see the problem had gone. I formatted Disk 1 and disk 1 reverted to being a data disk. With so many steps it is possible that I became impatient with lengthy updating and pressed the on/off button on the computer. I do not remember, but some corruption might have been generated. I still haven't tried the safe mode approach. If that doesn't work I am happy to do another re-install as I am getting more used to the procedure. If I do that I have a question. If I add a drive letter to my System Reserved partition can I then access it and format it so that Disk 0 (drive C) becomes completely 'cleansed'?

 

[Layback Bear]

I'm lurking again.

I noticed this in your post #15

With so many steps it is possible that I became impatient with lengthy updating and pressed the on/off button on the computer.

Did you or did you not shut down the computer in the middle of things??

Yes that can cause problems.

 

[monday69]

Have now used safe mode and pasted your files into Packages and Manifests as instructed. Restarted in normal mode and ran Windows6.1-KB947821-v34-x64.msu again Still can't update. When I get the warning message 'Some updates were not installed' I get it twice; that is 2 copies at the same time. Is this significant? I have 2 boot processes in my System Reserved partition. However I am quite prepared to do another clean re-install, very carefully!

 

[monday69]

I clearly have some corruption and some other possible problems
Here is my plan. My computer has one SSD, with the OS on it, and another conventional drive we will call Main drive. I will disconnect other unneeded equipment.
• I will save data from Main onto something external
• I will format Main
• I will disconnect the SSD and clean install WIN 7 64-bit on Main
• I will reconnect the SSD, start the computer and format the SSD
• Here is my first question. I have only recently learnt about System Reserved. If I add a drive letter can I format that partition? If I do so will WIN 7 later re-install the special files in that same partition or would it be better to delete the partition and let WIN 7 start afresh, so to speak?
• Continuing my plan I will disconnect the Main drive and start the computer
• I will install WIN7 on the SSD getting a perfect uncontaminated installation and live happily ever after.

So my second question is whether this is a good plan, and finally any advice about System Reserve would be appreciated?

 

[monday69]

And a note to layback bear; I might have. I know it is wrong but if the computer seems to be just hanging with no progress indicator I think I have some excuse. Some expert recently commented scornfully that he had known people leave their computers updating for days! Anyway if I embark on another clean install I will be warned. Thanks for your comment. And thanks to NoelDP for your efforts. I am still hoping for a comment to my plan in post #18 but I have a little laptop to receive any advice so will start the plan now.

 

[NoelDP]

You can delete the System Reserved partition when you Install Windows - go to the Brink's tutorial here... http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html