[SOLVED] 80073712 on KB3121212 Windows 7 x64 Pro

JellyKid

New member
Joined
Jan 27, 2016
Posts
4
I should probably just reformat and reinstall but I really want to figure out what the problem is. The original error was received was 800B0100 for the KB3121212 update.

This system pulls updates from an internal WSUS and is the only one having a problem. The first thing I tried was the MS updated fix it and the troubleshooter. No luck. I tried manually downloading the update and installing. I tried running SURS.

After checking the CheckSur.log I followed a guide at MS technet to replace the the actual manifest folders and files under winsxs from a working machine. Ran CheckSur again and still was receiving 800B0100 but now I have only 2 CBS MUM Corrupt errors.

Then I tried to fix the packages by copying them from a working machine to the Windows\CheckSur\Packages directory(I guess I should have done the same with the manifests) :
Troubleshooting Error 800B0100, TRUST_E_NOSIGNATURE, during Service Pack 1 installation on Windows 7 or Windows 2008 R2 - Ask the Core Team - Site Home - TechNet Blogs

It would fix the errors but they kept coming back everytime I ran it. So I got desperate :banghead: and ran a stupid batch file that was supposed to reset all windows components.(attached is the batch) The batch didn't seem that terrible it, didn't even delete directories or files but it did do some weird stuff with the bits service that I still have know idea what it's doing. Also I did something else stupid :banghead: I followed a post about copying and renaming servicing\packages\servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum to include the neutral part since the checksur.log said
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name

Still having the same problem, then I ran "DISM /Online /Cleanup-Image /Scanhealth" to the WSUS server and to Windows update servers. Now I am getting the 80073712 error :( I then reverted all of the directories that were changed in the batch file from .bak to their normal names.... now I'm here. There is so much disinformation on the internet about MS updates it's mind boggling, I'm hoping to get some insight on to what I could have done in the future and if this is still fixable or not.

Link to registry hive component - https://onedrive.live.com/redir?resid=869FF6F78E577B89!947&authkey=!AHJgTTKDjjxgt5g&ithint=file,zip

PS Also I just found a system that is having problems starting the wuauserv service with "failed to read description. error code 193" but I'm not touching it until I get some advice here. Some forums are suggesting the uninstall and reinstall of SP1 which sounds crazy to me. I'll make another thread for that one.
 

Attachments

SFC corruption - "SURT execution needed due to manifest damage"

wuauserv service is failing to start with <Failed to Read Description. Error Code: 193 > and windows update won't launch

I'm hoping surt or dism can fix this but I'm guessing I'm out of luck. Any help would be much appreciated. So far I have done nothing since I found the error except run SFCFix.

:thud:


Code:
SFCFix version 2.4.8.0 by niemiro.
Start time: 2016-01-27 14:57:20.652
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-w..client-ui.resources_31bf3856ad364e35_7.6.7601.18979_en-us_4df36840278c45c4". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18979_none_7742ee3b1ebc297b". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.18979_none_e726f3ae65449e7c". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-winsetupui_31bf3856ad364e35_6.1.7601.18979_none_bcf6459fdc768dfe". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-windowsupdateclient-ui_31bf3856ad364e35_7.6.7601.18979_none_64d417590548e12d". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "wow64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18979_none_8197988d531ceb76". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-w..pdate-adm.resources_31bf3856ad364e35_7.6.7601.18979_en-us_965291bd7e6d14a9". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.18979_en-us_e6c8c0e414860748". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-w..ent-internalupgrade_31bf3856ad364e35_7.6.7601.18979_none_2b60179288963640". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.18979_none_cd382dfa7904f77f". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.6.7601.18979_none_a3b8aa93ce69cce4". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7601.18979_en-us_f11d6b3648e6c943". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7601.18979_none_d78cd84cad65b97a". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.6.7601.18979_en-us_3c9b613599de4e43". See CBS logfile for more details.








SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     112
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.8.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-01-27 14:58:25.391
----------------------EOF-----------------------
 
Hello and welcome!

It would appear that you are using an old version of the System Update Readiness Tool.
Let's try running the latest version to see if it finds any problems.

System Update Readiness Tool (SURT)

Download and run the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

This tool will take some time to complete - when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
 
zcomputerwiz, thanks for the speedy reply but I just did a repair install from an OEM disk I had. This morning the computer decided to not come on properly after a reboot.

Windows Update error 80073712 - Windows Help

running updates now and hopefully it doesn't happen again. Can you tell me what commonly causes WINSXS corruption and what can be done to prevent or catch it?
 
Can you tell me what commonly causes WINSXS corruption and what can be done to prevent or catch it?

There are a lot of interlinking components involved in the Windows Update process, so there are many things that can cause problems when installing or removing updates.
Often corrupt or missing files or registry entries can be attributed to hardware, software, or environmental issues such as bad ram, bad sectors on the hard disk, loss of power during update installation, or failing to resume from sleep/hibernation after an update.

It's probably a good idea to run some diagnostics to make sure that the system is healthy :smile9:
 

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

Back
Top