Resetting WU will never work if you damages in WinSxS or Packages folder and repair install is solution for cannibals,although I admitt you have seriously damages:
Quote:
Unavailable repair files:
winsxs\manifests\amd64_mscorlib_b77a5c561934e089_6.1.7600.20717_none_3dbbc63282d93e16.manifest
winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_7e53f0fd6ebdc541.manifest
winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20740_none_607b009642d9c626.manifest
winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_88a89b4fa31e873c.manifest
winsxs\manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.20717_none_a126b806c861ae6e.manifest
winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16619_none_363c11500fe837b6.manifest
winsxs\manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7600.16597_en-us_66b0e132757333e5.manifest
winsxs\manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_89f4ffc7bc568a83.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\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_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_7ecaeece87e8e8f2.manifest
winsxs\manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7600.20717_en-us_4fdb37fe8f21c984.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
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_1_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_1_for_KB983590~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_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB983590~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_4_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_4_for_KB983590~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_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_1_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_1_for_KB983590~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_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_2_for_KB983590~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_4_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_4_for_KB983590~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_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
I'll prepare files to replace,untill now don't do that anything.
EDIT
Your damages are very similar to this guy -interesting
Unable to install updates because of 800B0100
Here is instruction for you:
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
Packs.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.

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 -if log is empty that means WU should work now,if not present here new CheckSur.log file -above fix may not fix all issues at once