Starting with Windows 8 and Server 2012, you can more easily fix corrupted updates using the “DISM.exe /Online /Cleanup-image /Restorehealth” command, but what about on Windows 7 or on Server 2008? Well, to be honest, it is kind of a pain in the ass and quite a lengthy process.
This seems to be a prime candidate for some sort of automated batch or PowerShell script that could parse out the bad updates from the log file, extract the needed files from the KB .msu packages, move them to the temp directory, and then re-run the System Update Readiness Tool. Lord knows it would save a lot of people some time and headaches but I don’t know whether it is even worth the hassle of programming it all seeing as how mainstream support for Windows 7 will be up soon and extended support will be around until 2020. That and I’m sure a lot of people have been suckered into upgrading to Windows 10 for free as well. It’s ok, there’s nothing in that giant wooden trojan horse that they just carted into your living room. Your data is safe and there are absolutely zero privacy concerns, trust them. Go back to sleep zombie.
Anyways, if you have installed any Server 2008 or Windows 7 operating systems in the last say year or so, you probably have noticed that Windows Update gets broken almost every single freaking time and it is quite cumbersome. So here is the cliff notes version on how to repair your corrupted Windows Update files.
In my particular case that I am addressing specifically in this article, I had already fixed the other long, tedious Windows Update not working problems previously and still had one update left that would not install. I would get a Windows Update error 80073712 when trying install KB2943357, which is a .NET 3.5 update.
I was still having issues even after running “sfc /scannow”, which showed no problems, and I had already installed the system update readiness tool and had run it several times, so I had to dig a little deeper and check the error log located here:
%WINDIR%\Logs\CBS\CheckSUR.log
At the very bottom of the log file, you can find a list of all the corrupt or missing update files.
Unavailable repair files: winsxs\manifests\amd64_microsoft.transactions.bridge.dtc_b03f5f7f11d50a3a_6.1.7601.22733_none_65085bdd54b4a629.manifest winsxs\manifests\amd64_wcf-m_sm_ins_rc_dll_31bf3856ad364e35_6.1.7601.22733_none_2795328d79930284.manifest winsxs\manifests\amd64_wcf-system.runtime.serialization.ref_b03f5f7f11d50a3a_6.1.7601.22733_none_424d323c8e896dad.manifest winsxs\manifests\amd64_wcf-icardres_dll_vista_31bf3856ad364e35_6.1.7601.18523_none_6f276a738180cba8.manifest winsxs\manifests\amd64_wcf-smdiagnostics_b03f5f7f11d50a3a_6.1.7601.18523_none_f5ee0756c06c09cd.manifest winsxs\manifests\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7601.22733_en-us_787b5545d9776103.manifest winsxs\manifests\msil_smdiagnostics.resources_b77a5c561934e089_6.1.7601.18523_en-us_496526973f1e68f2.manifest winsxs\manifests\amd64_wcf-m_sm_ins_rc_dll_31bf3856ad364e35_6.1.7601.18523_none_271663c8606d49a2.manifest winsxs\manifests\amd64_microsoft-windows-wcfcorecomp.resources_31bf3856ad364e35_6.1.7601.22733_en-us_ff634b2369479517.manifest winsxs\manifests\amd64_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.18523_none_02011939c648dcfe.manifest winsxs\manifests\amd64_wcf-icardagt_exe_31bf3856ad364e35_6.1.7601.22733_none_907097fea175fea2.manifest winsxs\manifests\amd64_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.1.7601.22733_none_7d243f06e2816846.manifest winsxs\manifests\amd64_wcf-m_sm_cfg_ins_exe_31bf3856ad364e35_6.1.7601.22733_none_5eba49464cf449c9.manifest winsxs\manifests\msil_system.runtime.serialization_b77a5c561934e089_6.1.7601.22733_none_bff6ca10b626f70a.manifest winsxs\manifests\msil_system.identitymodel_b77a5c561934e089_6.1.7601.18523_none_f1b7e3b500b0dd75.manifest winsxs\manifests\amd64_infocard.resources_b77a5c561934e089_6.1.7601.18523_en-us_1c3528fb3f63ae97.manifest winsxs\manifests\amd64_microsoft-windows-wpfcorecomp.resources_31bf3856ad364e35_6.1.7601.18523_en-us_102e1681a6f8daa0.manifest winsxs\manifests\msil_system.servicemodel.washosting_b77a5c561934e089_6.1.7601.22733_none_7b9fe117b7a77077.manifest winsxs\manifests\msil_smsvchost.resources_b03f5f7f11d50a3a_6.1.7601.22733_en-us_b2b27b25e379631c.manifest winsxs\manifests\msil_system.servicemodel_b77a5c561934e089_6.1.7601.22733_none_627b1e3960ee4846.manifest winsxs\manifests\msil_smsvchost.resources_b03f5f7f11d50a3a_6.1.7601.18523_en-us_c97f21bfc9d2e96e.manifest winsxs\manifests\amd64_microsoft.transactions.bridge.dtc_b03f5f7f11d50a3a_6.1.7601.18523_none_7bd502773b0e2c7b.manifest winsxs\manifests\amd64_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.22733_none_230aba46aff3690d.manifest winsxs\manifests\msil_system.servicemodel.resources_b77a5c561934e089_6.1.7601.22733_en-us_0f4b4b63d0545797.manifest winsxs\manifests\amd64_wcf-infocard_api_dll_31bf3856ad364e35_6.1.7601.22733_none_027fe7fedf6e95e0.manifest winsxs\manifests\amd64_wcf-smsvchost_b03f5f7f11d50a3a_6.1.7601.22733_none_b0fabad924c43863.manifest winsxs\manifests\msil_microsoft.transacti..ridge.dtc.resources_b03f5f7f11d50a3a_6.1.7601.22733_en-us_ee690b9c8991e0b1.manifest winsxs\manifests\amd64_infocard.resources_b77a5c561934e089_6.1.7601.22733_en-us_05688261590a2845.manifest winsxs\manifests\msil_system.identitymodel.resources_b77a5c561934e089_6.1.7601.18523_en-us_d834c775e8e8bf5a.manifest winsxs\manifests\amd64_wcf-icardagt_exe_31bf3856ad364e35_6.1.7601.18523_none_8ff1c939885045c0.manifest winsxs\manifests\msil_system.servicemodel_b77a5c561934e089_6.1.7601.18523_none_7947c4d34747ce98.manifest winsxs\manifests\amd64_wcf-m_sm_cfg_ins_exe_31bf3856ad364e35_6.1.7601.18523_none_5e3b7a8133ce90e7.manifest winsxs\manifests\amd64_infocard_b77a5c561934e089_6.1.7601.22733_none_416efebeda587c2c.manifest winsxs\manifests\msil_system.servicemodel.ref_b77a5c561934e089_6.1.7601.22733_none_29f6a06ce8fccf4d.manifest winsxs\manifests\msil_smdiagnostics_b77a5c561934e089_6.1.7601.18523_none_72efc8f96ca487c3.manifest winsxs\manifests\msil_system.identitymodel_b77a5c561934e089_6.1.7601.22733_none_daeb3d1b1a575723.manifest winsxs\manifests\msil_smsvchost_b03f5f7f11d50a3a_6.1.7601.22733_none_cfea951b2aba8a29.manifest winsxs\manifests\msil_system.runtime.serialization.resources_b77a5c561934e089_6.1.7601.18523_en-us_8f47fbdfbfd0e755.manifest winsxs\manifests\msil_smdiagnostics_b77a5c561934e089_6.1.7601.22733_none_5c23225f864b0171.manifest winsxs\manifests\amd64_wcf-system.runtime.serialization_b03f5f7f11d50a3a_6.1.7601.18523_none_93f0e5a0c8daee98.manifest winsxs\manifests\msil_smdiagnostics.resources_b77a5c561934e089_6.1.7601.22733_en-us_32987ffd58c4e2a0.manifest winsxs\manifests\msil_system.runtime.serialization.ref_b77a5c561934e089_6.1.7601.18523_none_a6803b1074d97c29.manifest winsxs\manifests\amd64_microsoft-windows-wpfcorecomp.resources_31bf3856ad364e35_6.1.7601.22733_en-us_10ace546c01e9382.manifest winsxs\manifests\amd64_wcf-smsvchost_b03f5f7f11d50a3a_6.1.7601.18523_none_c7c761730b1dbeb5.manifest winsxs\manifests\amd64_wcf-system.identitymodel_b03f5f7f11d50a3a_6.1.7601.22733_none_9b8bf7be024ae1df.manifest winsxs\manifests\msil_system.runtime.serialization_b77a5c561934e089_6.1.7601.18523_none_d6c370aa9c807d5c.manifest winsxs\manifests\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.22733_none_0476f2837b6cca3b.manifest winsxs\manifests\amd64_microsoft-windows-wcfcorecomp.resources_31bf3856ad364e35_6.1.7601.18523_en-us_fee47c5e5021dc35.manifest winsxs\manifests\amd64_wcf-m_sm_evt_dll_vista_31bf3856ad364e35_6.1.7601.18523_none_d6844f55af0a470f.manifest winsxs\manifests\msil_smsvchost_b03f5f7f11d50a3a_6.1.7601.18523_none_e6b73bb51114107b.manifest winsxs\manifests\msil_system.identitymodel.resources_b77a5c561934e089_6.1.7601.22733_en-us_c16820dc028f3908.manifest winsxs\manifests\amd64_infocard_b77a5c561934e089_6.1.7601.18523_none_583ba558c0b2027e.manifest winsxs\manifests\amd64_wcf-m_sm_mof_31bf3856ad364e35_6.1.7601.18523_none_228beb8196cdb02b.manifest winsxs\manifests\msil_microsoft.transacti..ridge.dtc.resources_b03f5f7f11d50a3a_6.1.7601.18523_en-us_0535b2366feb6703.manifest winsxs\manifests\msil_system.servicemodel.washosting_b77a5c561934e089_6.1.7601.18523_none_926c87b19e00f6c9.manifest winsxs\manifests\msil_system.runtime.serialization.ref_b77a5c561934e089_6.1.7601.22733_none_8fb394768e7ff5d7.manifest winsxs\manifests\amd64_wcf-icardres_dll_vista_31bf3856ad364e35_6.1.7601.22733_none_6fa639389aa6848a.manifest winsxs\manifests\amd64_wcf-m_sm_evt_dll_vista_31bf3856ad364e35_6.1.7601.22733_none_d7031e1ac82ffff1.manifest winsxs\manifests\amd64_wcf-m_svc_mon_sup_dll_31bf3856ad364e35_6.1.7601.18523_none_03f823be62471159.manifest winsxs\manifests\amd64_wcf-system.runtime.serialization.ref_b03f5f7f11d50a3a_6.1.7601.18523_none_5919d8d674e2f3ff.manifest winsxs\manifests\amd64_wcf-smdiagnostics_b03f5f7f11d50a3a_6.1.7601.22733_none_df2160bcda12837b.manifest winsxs\manifests\amd64_wcf-system.identitymodel_b03f5f7f11d50a3a_6.1.7601.18523_none_b2589e57e8a46831.manifest winsxs\manifests\msil_system.servicemodel.resources_b77a5c561934e089_6.1.7601.18523_en-us_2617f1fdb6addde9.manifest winsxs\manifests\msil_system.servicemodel.ref_b77a5c561934e089_6.1.7601.18523_none_40c34706cf56559f.manifest servicing\packages\Package_100_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_100_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_5_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_5_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_6_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_6_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_7_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_7_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_8_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_8_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_97_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_97_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_98_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_98_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_99_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_99_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_for_KB2943357_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_for_KB2943357_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.mum servicing\packages\Package_100_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_100_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_5_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_5_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_6_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_6_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_7_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_7_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_8_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_8_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_97_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_97_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_98_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_98_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_99_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_99_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_for_KB2943357_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_for_KB2943357_SP1~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat servicing\packages\Package_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat
After doing some searching online, I found several articles on sevenforums.com where they were missing the exact same updates files and one person had posted a fix but the files were located on a Google Drive account and unfortunately they were no longer being hosted there.
After a more exhaustive search, I eventually found this MS article and followed the instructions on there to be able to finally resolve the issue. Basically, the fix consisted of the doing the following:
- Manually download the KB article .msu update package that is mentioned in the CheckSUR.log
- Extract the data from the .msu package to a folder somewhere using the expand command at the command prompt.
cd %SYSTEMROOT%\Users\%USERNAME%\Downloads mkdir updatefiles cd updatefiles expand ..\Windows6.1-KB2943357-x64.msu /f:* .
- Extract the update files from the .cab package to a folder somewhere using the expand command.
expand Windows6.1-KB2943357-x64.cab /f:* .
- Open a search window and one by one, find the missing .manifest, .mum, or .cat files and copy them to their respective temp folders.
The .manifest files should be copied to this folder:%WINDIR%\Temp\CheckSur\Winsxs\Manifests
The .cat and .mum files should be copied to this folder:
%WINDIR%\Temp\CheckSur\Servicing\Packages
As the Microsoft article mentions, when you come across root packages such as this in the log file:
Package_for_KB2943357~31bf3856ad364e35~amd64~~6.1.1.3.cat
You will have to find the files named update.cat or update.mum and rename them to exactly what was written in the log file (which an example was given directly above this sentence) and also move them to their respective temp folder.
- Re-run the System Update Readiness Tool and double check that there aren’t any more corrupted files in the log file.
- Re-run the KB installer .msu package and everything should install properly now.