lpto
New member
- Dec 19, 2019
- 3
So.. How would I start this thread.. I have been trying to fix this issue myself now for a while now. For several months I had been neglecting Windows updates on my machine, as I thought I would be upgrading to Windows 10 or Linux or something else soon anyway. Now it seems that I am going to need Win7 for the forseeable future, and will continue dual booting it. I know I would've already been able to make a Windows 7 in-place upgrade several times, and they would've most likely solved my issues. I still prefer to learn about Windows 7 fixes myself though, which is one of the reasons I have not wanted to do that, but instead just tried to troubleshoot the issue.
Let's cut to the chase. I have now realized that I was missing my COMPONENTS registry hive for around a year. That was the reason why SFC scan wouldn't work at all for the previous times I have tried to investigate my Win7 problems. Nevertheless, by following some tutorials on sysnative and elsewhere, I thought that there would be no harm done by doing something about the hive. First I tried getting the hive from a very similar machine, but with much newer Win7 installation. By this time I had already found SFCfix by sysnative, and found it to be of great use when troubleshooting. When using the hive from the similar machine I soon realized, that while I could get SFC scan and Windows update to work, the updates processes would take ages to run, and when running SFCfix, all I could see was something along the lines of:
After a while fiddling out with these, and actually replacing all the CORRUPT files listed above, I got not much further. After running SURT, I always got Windows update to a "working" state, since I could install Drivers, NET framework updates, Office updates etc from it. However what has persisted through all the SURT runs are the Win7 updates kb4474419-v2, kb4474419-v3 & kb4516065. I have received several error codes for them, but the most prevalent has now been just 80073712. After browsing solutions on the sysnative forum I thought to try some other COMPONENTS hive. This time I just got one from a Win7 installation disk from the appropriate install.wim archive. Following running SFC /scannow, SURT and then SFCfix, I was able to a seemingly better result. However the same 80073712 error with the same KBs still remains. The one remaining CORRUPT file I fixed manually, so it should be gone in the next run. (sfc /scannow runs without reporting integrity violations) After this I've probably hit the end of my abilities, which is why I am writing. Is there anything that can actually even be done after a completely gone COMPONENTS hive? Can I try something novel?
Let's cut to the chase. I have now realized that I was missing my COMPONENTS registry hive for around a year. That was the reason why SFC scan wouldn't work at all for the previous times I have tried to investigate my Win7 problems. Nevertheless, by following some tutorials on sysnative and elsewhere, I thought that there would be no harm done by doing something about the hive. First I tried getting the hive from a very similar machine, but with much newer Win7 installation. By this time I had already found SFCfix by sysnative, and found it to be of great use when troubleshooting. When using the hive from the similar machine I soon realized, that while I could get SFC scan and Windows update to work, the updates processes would take ages to run, and when running SFCfix, all I could see was something along the lines of:
Code:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-19 22:06:43.651
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component cxraptor_fm1216mk5_ibv64.inf and file cxraptor_FM1216MK5_IBV64.inf. File is reported as corrupt by SFC.
CORRUPT: cxraptor_FM1216MK5_IBV64.inf of component cxraptor_fm1216mk5_ibv64.inf.
WARNING: Manifest damage on component "x86_microsoft-windows-d2d.resources_31bf3856ad364e35_7.1.7601.16492_nb-no_45641a7fbc21db79". See CBS logfile for more details.
WARNING: Manifest damage on component "x86_microsoft-windows-d2d.resources_31bf3856ad364e35_7.1.7601.16492_nl-nl_43a365bdbd4de54e". See CBS logfile for more details.
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-a..xperience-inventory_31bf3856ad364e35_6.1.7601.24233_none_e8e2461cfea5b65f\diagtrackrunner.exe
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-i..odepage-iso2022core_31bf3856ad364e35_6.1.7600.16385_none_bc1ef2b789f7bb65\C_IS2022.DLL
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-rasconnectionmanager_31bf3856ad364e35_6.1.7601.17514_none_bd4644e077251730\cmmon32.exe
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-rasconnectionmanager_31bf3856ad364e35_6.1.7601.17514_none_bd4644e077251730\cmstplua.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-rasconnectionmanager_31bf3856ad364e35_6.1.7601.17514_none_bd4644e077251730\cmcfg32.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-s..oxgames-minesweeper_31bf3856ad364e35_6.1.7600.16385_none_fe560f0352e04f48\MineSweeper.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-usertiles_31bf3856ad364e35_6.1.7600.16385_none_f385bacaa98d1e8b\usertile22.bmp
CORRUPT: C:\Windows\winsxs\wow64_microsoft-windows-mulanttsvoiceenudsk_31bf3856ad364e35_6.1.7600.16385_none_75c520ccf1df00ca\M1033DSK.IDX
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-audio-mci_31bf3856ad364e35_6.1.7600.16385_none_1ce3af494d8b953d\mcicda.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-g..ppolicy-policymaker_31bf3856ad364e35_6.1.7601.23452_none_39acca09c07e22c1\gpprefcl.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-luainstaller_31bf3856ad364e35_6.1.7601.17514_none_1abddb61c68d6a07\luainstall.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-lz32_31bf3856ad364e35_6.1.7600.16385_none_9265d35e8abc9706\lz32.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-m..me-mctres-component_31bf3856ad364e35_6.1.7600.16385_none_4fa95be207d9d3bb\mctres.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-makecab_31bf3856ad364e35_6.1.7600.16385_none_f0a5d809ca926e4f\makecab.exe
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-mediaplayer-logagent_31bf3856ad364e35_6.1.7601.17514_none_ed47f623204af12a\logagent.exe
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-mobilepc-location-api_31bf3856ad364e35_6.1.7600.16385_none_10bde6f3d1b059c3\LocationApi.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-scheduleui_31bf3856ad364e35_6.1.7600.16385_none_74990c26730e98ea\loghours.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-t..alservices-lsmproxy_31bf3856ad364e35_6.1.7601.17514_none_0d939f26299f746c\lsmproxy.dll
CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-tcpip-utility_31bf3856ad364e35_6.1.7601.17514_none_34ce5d95ad203bbe\MRINFO.EXE
CORRUPT: C:\Windows\winsxs\amd64_display.inf_31bf3856ad364e35_6.1.7600.16385_none_dc4a31b0e7fffb2c\display.inf
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 53
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 4797
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2019-12-19 23:08:40.967
----------------------EOF-----------------------After a while fiddling out with these, and actually replacing all the CORRUPT files listed above, I got not much further. After running SURT, I always got Windows update to a "working" state, since I could install Drivers, NET framework updates, Office updates etc from it. However what has persisted through all the SURT runs are the Win7 updates kb4474419-v2, kb4474419-v3 & kb4516065. I have received several error codes for them, but the most prevalent has now been just 80073712. After browsing solutions on the sysnative forum I thought to try some other COMPONENTS hive. This time I just got one from a Win7 installation disk from the appropriate install.wim archive. Following running SFC /scannow, SURT and then SFCfix, I was able to a seemingly better result. However the same 80073712 error with the same KBs still remains. The one remaining CORRUPT file I fixed manually, so it should be gone in the next run. (sfc /scannow runs without reporting integrity violations) After this I've probably hit the end of my abilities, which is why I am writing. Is there anything that can actually even be done after a completely gone COMPONENTS hive? Can I try something novel?
Code:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-12-20 09:50:17.064
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_display.inf_31bf3856ad364e35_6.1.7600.16385_none_dc4a31b0e7fffb2c\display.inf
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 127
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2019-12-20 11:33:46.260
----------------------EOF-----------------------
Last edited:
