Windows update error 800B0100 Windows 7 64 bit

P

polarisfff

Member
Joined
Oct 8, 2013
Posts
8
Hello guys,

windows Updates doesn`t work correctly in my VMWare View template. Got error code 800B010.
Please could you help me with it?

I have attached the CheckSUR.log

Thank you and greetings from germany!

Tobi



[h=2][/h]
 

Attachments

There's some interesting errors there - and I'm not certain that this is going to be fixable without a repair install, but we'll give it a try :)

Here's the list of damaged files that need to be replaced, from your log
Code: 
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7600.256_none_bc064e3e65514b79.manifest
 winsxs\manifests\amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7600.256_de-de_2ca60b2f11f44f7d.manifest
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-German~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-German~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-German~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-German~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.cat

I'll see what I can do to source them all, and post a fix later today.
 
NoelDP said:
There's some interesting errors there - and I'm not certain that this is going to be fixable without a repair install, but we'll give it a try :)

Here's the list of damaged files that need to be replaced, from your log
Code: 
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7600.256_none_bc064e3e65514b79.manifest
 winsxs\manifests\amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7600.256_de-de_2ca60b2f11f44f7d.manifest
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-German~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-German~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-German~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-German~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~de-DE~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.cat

I'll see what I can do to source them all, and post a fix later today.
Click to expand...

Hello NoelDP,

thank you very much. I will wait for your reply.

Thank your very much and greetings from germany,
Tobias
 
With any luck I've got 'em all now...

I've uploaded a file - pffaa.zip - to my SkyDrive at Noel's SkyDrive
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 pffaa 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.

The run another SFC /SCANNOW, in case that brings anything new to light.
 
NoelDP said:
With any luck I've got 'em all now...

I've uploaded a file - pffaa.zip - to my SkyDrive at Noel's SkyDrive
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 pffaa 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.

The run another SFC /SCANNOW, in case that brings anything new to light.
Click to expand...

Hello,

thank you very much for your fast answer.
I have implement the files and the tool is actually running. I will let you know!

Greetings,
Tobi
 
polarisfff said:
NoelDP said:
With any luck I've got 'em all now...

I've uploaded a file - pffaa.zip - to my SkyDrive at Noel's SkyDrive
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 pffaa 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.

The run another SFC /SCANNOW, in case that brings anything new to light.
Click to expand...

Hello,

thank you very much for your fast answer.
I have implement the files and the tool is actually running. I will let you know!

Greetings,
Tobi
Click to expand...

Hello,

that`s it. Now it works and Windows will download 166 Updates.
You saved my week :-) :rose:

Many, many thanks for your help!!!!!!!!!!!!!! :dance:
 
Great! - please post the new CheckSUR log so we can check that everything was fixed - and run the SFC, and post the new CBS.log as well



Good luck.
 
Hmm - there are some very hefty errors in there!

I suspect that you will have problems going forward :(

When (not if!) Windows Update starts complaining again, please run another CheckSUR scan/install, and post the new CheckSUR log.


Meanwhile I'll try and work out how to fix the new errors.
 
NoelDP said:
Hmm - there are some very hefty errors in there!

I suspect that you will have problems going forward :(

When (not if!) Windows Update starts complaining again, please run another CheckSUR scan/install, and post the new CheckSUR log.


Meanwhile I'll try and work out how to fix the new errors.
Click to expand...


Hello again,

all updates were installed successfully. :dance:
How can I run "CheckSUR scan/install" in a short way? Actually I run the "windows updates repair tool" Windows6.1-KB947821-v27-x64.msu and it needs very long time...

Thanks a lot!!!
 
That's the one :)
it's a tool, rather than an update/install, but because of the way it's constructed, it appears to be an update.
Simply double-click on the executable file again, and it will 'install' again.
 
NoelDP said:
That's the one :)
it's a tool, rather than an update/install, but because of the way it's constructed, it appears to be an update.
Simply double-click on the executable file again, and it will 'install' again.
Click to expand...



Hello,

ok have run the "windows updates repair tool Windows6.1-KB947821-v27-x64.msu" again and getting directly when setup starts: Error 0x80004002
Error in Windows\System32\wups.dll :banghead:

But Updates with WSUS works correctly...

Greetings!


 
That's I think is a registry equivalent of 'file not found'

I think you have some severe registry problems, and it's likely that your best way forward is going to be a repair install.

Please zip your CBS.log file up, and post that - and the new CheckSUR.log file
 
NoelDP said:
That's I think is a registry equivalent of 'file not found'

I think you have some severe registry problems, and it's likely that your best way forward is going to be a repair install.

Please zip your CBS.log file up, and post that - and the new CheckSUR.log file
Click to expand...


Hello,

do you mean "repair install" like booting from Windows 7 Setup DVD "start up repair" ?

THX!!!
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top