Unable to install updates because of 800B0100

adverze said:

did you install and run the latest System Update Readiness Tool?

Download details: System Update Readiness Tool for Windows 7 (KB947821) [April 2010]

If not download and run this one and attempt to update again.

Hope it helps,

Adverze

It doesn't make sense,repeating Readiness Tool will never solve this problem.Built-in autofix tool can only fix the easiest issues.This one is very hard.

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.20738_none_69cd38af1d1dedd3.manifest
winsxs\manifests\amd64_b2db70fde4bba871099a6486474b10fe_31bf3856ad364e35_6.1.7600.16612_none_3fa3f1d c518b21de.manifest
winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20740_none_607b009642d9c626.manifest
winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.20733_none_0fd0b57e990e2079.manifest
winsxs\manifests\amd64_c7bd203987149def1c2c18717d81d5e6_31bf3856ad364e35_6.1.7600.16612_none_e9da73e 72f0f803d.manifest
winsxs\manifests\x86_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.20738_none_0dae9d2b64c07c9d.manifest
winsxs\manifests\x86_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_e877dfd2b7241dea.manifest
winsxs\manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.20717_none_a126b806c861ae6e.manifest
winsxs\manifests\x86_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.16617_none_0d399fee4b938b9a.manifest
winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16619_none_363c11500fe837b6.manifest
winsxs\manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_89f4ffc7bc568a83.manifest
winsxs\manifests\amd64_microsoft-windows-rasrtutils_31bf3856ad364e35_6.1.7600.16617_none_69583b7203f0fcd0.manifest
winsxs\manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_a0caa8fba2a7f4e4.manifest
winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16619_none_601ad629299bb698.manifest
winsxs\manifests\amd64_microsoft-windows-tcpip-binaries_31bf3856ad364e35_6.1.7600.16610_none_0f59b7ad7fe2fcc8.manifest
winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_891f9920bc49aaed.manifest
winsxs\manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_bf383e53d6b20cfc.manifest
winsxs\manifests\amd64_3b21d80f6ec46f3f54e45b47c5decd14_31bf3856ad364e35_6.1.7600.20735_none_311ba0b aba7f06d6.manifest
winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20740_none_369c3bbd29264744.manifest
winsxs\manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20740_none_36916bd1292e6335.manifest
winsxs\manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16619_none_363141640ff053a7.manifest
winsxs\manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_a862951ff060a29b.manifest
winsxs\manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.16597_none_b7fc613aaeb318cf.manifest
winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_7e53f0fd6ebdc541.manifest
winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_88a89b4fa31e873c.manifest
winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_7ecaeece87e8e8f2.manifest
servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
servicing\packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_2_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_2_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_3_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB978886_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB978886~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat
servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat
servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
servicing\packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB982799_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB982799~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat

@veggis

I attached to post files to replace,download & unpack them anythere

Two methods to replace these corrupted files:

METHOD I
1.Download attached to post FixPacks.zip file -in zip file is packed Packs folder -you have to unpack it and place directly on C: exactly as I show below:

Click this bar to view the full image.
2.Boot your Windows install disk (if you don't have Windows 7 install disk instead use special recovery disk)
Choose language>>Repair Computer>>WinRE>>command prompt

and type:

robocopy C:\Packs C:\ /E /IS

press ENTER

del C:\Windows\Logs\CBS\*.*

press ENTER

METHOD II (recomended if you have any another OS on your hdd)

1.Download & unpack attached to post file anythere
2.Run your second OS,from unpacked files choose only Windows folder and it's subfolders and copy to partition where you have corrupted system,during copying the second OS ask you "do you want to merge folders?" or likely,apply procedure.
3.Empty C:\Windows\Logs\CBS folder

When procedure is done run your system again and run again Readiness Tool and present new CheckSur.log - I doubt it will fix all issues at once,probably it will require second tour,although the second one shouldn't so hard.

You have better results than I thought before .So I attached another small pack.You need only replace two files in C:\Windows\Servicing\Packages and it won't be any problem to do on allive system

I attached to post files to replace,download them and unpack anywhere

1.Navigate to C:\Windows\Servicing\Packages,takeownership of this folder and add your account to have full control
2.Copy my files to this folder -if you have already any file then replace it.
3.Remove your account from permissions to Packages folder
4.Restore ownership of Packages folder back to "NT Service\TrustedInstaller" +restart
5.Try install updates rather from Microsoft Download Center Microsoft Download Center (from WU you may have any problems)

Useful links (please read them):Take Ownership of file
TrustedInstaller - Restore as Owner
Folder Permissions

titixyz said:

Kindly help me out as i am unable to install updates, i am unable to install an antivirus programme online and windows defender keeps bringing an alert on detection of harmful software after i have cleared the system> also wireless assistant cannot read information
I have downloaded and extracted access check and followed the steps but the file was empty when i opened it in notepd

Start your OWN new thread - this one is too far out of date.