Good Day,
And thank you to all those spending time to help on the forum, I do appreciate!
About a year ago my gaming computer went through a few intempestive reboots (possibly related to having moved it while it was in use). A number of system files were damaged (I have a C: SSD drive for system, separated from games and data).
Windows could boot but a many programs would not work. By the time I could work on the issue (I travel a lot) there was no restore point available anymore from before the corruption. I don't have a system backup (only data) so what I did was sfc /scannow (including the manual replacement of files between 2 machines with the same OS version as per the procedure: https://support.microsoft.com/fr-fr...er-tool-to-repair-missing-or-corrupted-system), then followed by the use of SCFix. As far as I understand the files got repaired but I could not adress the corrupted "manifests" (I don't know if these are actual files that I could copy from my other system).
I never ran scandisk, having had various cases in the past (on other machines) where it did worsen significanty the situation without ever providing complete logs permitting to trace its activity.
I used the Microsoft repair tool for Windows Installer (https://support.microsoft.com/fr-fr/help/2438651/how-to-troubleshoot-windows-installer-errors) which claimed to have fixed various issues but one.
I probably used a similar tool provided by MS for fixing the most common Windows update errors (I have not kept trace of that).
This repaired a good many problems, leaving the computer useable enough for my most immediate needs. I tried the Windows repair options from the Windows CD but the repair failed and rolled back. Then I had to travel again and now that I am back I would like to get to the end of the matter since the remaining corruptions still prevent the functionning of some programs, many installers/repair programs and most windows updates. So I ran Windows update (only 2 successful updates out of 20) and then just ran again sfc /scannow and SCFix successively to be able to provide fresh logs.
Here is the SFCFix log :
Here the CBS log : View attachment CBS.zip
I would be very grateful for any help that you may be able to provide.
Cheers
[Edited a few typos]
And thank you to all those spending time to help on the forum, I do appreciate!
About a year ago my gaming computer went through a few intempestive reboots (possibly related to having moved it while it was in use). A number of system files were damaged (I have a C: SSD drive for system, separated from games and data).
Windows could boot but a many programs would not work. By the time I could work on the issue (I travel a lot) there was no restore point available anymore from before the corruption. I don't have a system backup (only data) so what I did was sfc /scannow (including the manual replacement of files between 2 machines with the same OS version as per the procedure: https://support.microsoft.com/fr-fr...er-tool-to-repair-missing-or-corrupted-system), then followed by the use of SCFix. As far as I understand the files got repaired but I could not adress the corrupted "manifests" (I don't know if these are actual files that I could copy from my other system).
I never ran scandisk, having had various cases in the past (on other machines) where it did worsen significanty the situation without ever providing complete logs permitting to trace its activity.
I used the Microsoft repair tool for Windows Installer (https://support.microsoft.com/fr-fr/help/2438651/how-to-troubleshoot-windows-installer-errors) which claimed to have fixed various issues but one.
I probably used a similar tool provided by MS for fixing the most common Windows update errors (I have not kept trace of that).
This repaired a good many problems, leaving the computer useable enough for my most immediate needs. I tried the Windows repair options from the Windows CD but the repair failed and rolled back. Then I had to travel again and now that I am back I would like to get to the end of the matter since the remaining corruptions still prevent the functionning of some programs, many installers/repair programs and most windows updates. So I ran Windows update (only 2 successful updates out of 20) and then just ran again sfc /scannow and SCFix successively to be able to provide fresh logs.
Here is the SFCFix log :
Code:
SFCFix version 3.0.0.0 by niemiro.Start time: 2017-09-18 15:17:27.717
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
WARNING: SURT execution needed due to manifest damage on component "amd64_38ee8cfd180e86ca2648b343ccbbf864_31bf3856ad364e35_6.1.7601.23392_none_51baccc85cf57631". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_94708c4762c62d499e7179de5ea6c04f_31bf3856ad364e35_6.1.7601.18540_none_4053021558729d55". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_fe44bc38257129a60b9ba73847797a64_6595b64144ccf1df_1.0.7601.18658_none_f4e4ae3833bb65c3". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_5171a954e421e09e8f99c37499c90017_b03f5f7f11d50a3a_6.1.7601.18410_none_5d276070131d6b6f". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "x86_microsoft-windows-i..riptcollectionagent_31bf3856ad364e35_11.2.9600.18314_none_3c09ee25f5738a13". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "x86_microsoft-windows-i..rityzones.resources_31bf3856ad364e35_11.2.9600.18314_fr-fr_97482a9b311b8f43". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_281d3ee1318c3323d3ec20e178ccf837_31bf3856ad364e35_6.1.7601.23392_none_e7b18dd7d003343c". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_317fa7425b4d165d418cae130516b7c0_6595b64144ccf1df_1.0.7601.18658_none_7dba3280ca82416e". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_6ebcdb808c20117bc06ae362df33a21d_b03f5f7f11d50a3a_6.1.7601.18586_none_0a060aecccbe70ba". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_a8ad7b4688813d238c9c634d30d4b8f3_b03f5f7f11d50a3a_6.1.7601.18586_none_fd5742bf08054890". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_cac5b49d18b52d795bd9d9300f0bf589_31bf3856ad364e35_6.1.7601.19045_none_cba5f51bc9c93e0c". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.1.7601.18637_none_ecb2935b6af13c52". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_b1f2726e53d00a2b24cb2b7134d58f9e_31bf3856ad364e35_6.1.7601.23392_none_30aeb295e9565ee4". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_2c239495608e2f84975364e69a5ed158_b03f5f7f11d50a3a_6.1.7601.19108_none_52d6c9bee05b8bfa". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_90d700dae0425f8cb1e66642d8d7d73d_31bf3856ad364e35_7.1.7601.18658_none_c4c321db33069f9c". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_dda5bf894406544f4ec90cde55e7542c_31bf3856ad364e35_6.1.7601.23392_none_7f230bed04937394". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_2b9aff24e8ce17dc2a1250870fd8596f_b03f5f7f11d50a3a_6.1.7601.18410_none_b9fba2325a524d54". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "amd64_7dd783c7bbf9a5f7ee3a4776b1ed82ef_31bf3856ad364e35_6.1.7601.23392_none_ccdcebde8886444f". See CBS logfile for more details.
WARNING: SURT execution needed due to manifest damage on component "x86_microsoft-windows-i..rityzones.resources_31bf3856ad364e35_11.2.9600.18314_en-us_f4c557b83e22873c". 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: 76
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 3.0.0.0 by niemiro has completed.
Currently storing 126 datablocks.
Finish time: 2017-09-18 15:36:06.118
----------------------EOF-----------------------
Here the CBS log : View attachment CBS.zip
I would be very grateful for any help that you may be able to provide.
Cheers
[Edited a few typos]