[SOLVED] Win7 x86 will not install security updates after interrupted update install

[Sysnative Windows Update]

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, please run SURT again and attach CheckSUR.log.

Thank you.

 

[controlfreq]

Here is the output from the sfcfix script:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-12-18 12:31:44.542
Microsoft Windows 7 Service Pack 1 - x86
Using .txt script file at C:\Users\basil\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6902e241755..64f84ddd5c0_31bf3856ad364e35_6.1.7601.21890_21ba0a8d450d81c2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\11f03560434..78836335661_31bf3856ad364e35_6.1.7601.17755_f3362e29ab50b857.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\046cdb18b6d..b5ebf1d8455_31bf3856ad364e35_6.1.7601.21890_2ad4ea8518d5ea57.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ed726b6e4e..a5b0a0dfda7_b77a5c561934e089_6.1.7601.17755_99fc8494ad9fcf15.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1a3e0387af3..d718dc3fc44_b77a5c561934e089_6.1.7601.21890_0250e8c7f2263b61.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6902e241755..64f84ddd5c0_31bf3856ad364e35_6.1.7601.21890_21ba0a8d450d81c2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\11f03560434..78836335661_31bf3856ad364e35_6.1.7601.17755_f3362e29ab50b857.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\046cdb18b6d..b5ebf1d8455_31bf3856ad364e35_6.1.7601.21890_2ad4ea8518d5ea57.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ed726b6e4e..a5b0a0dfda7_b77a5c561934e089_6.1.7601.17755_99fc8494ad9fcf15.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1a3e0387af3..d718dc3fc44_b77a5c561934e089_6.1.7601.21890_0250e8c7f2263b61.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 20 datablocks.
Finish time: 2018-12-18 12:31:44.963
Script hash: qqNS2vKTvuNojelEwobcoli5dFpATIIAyjVWc04VsLY=
----------------------EOF-----------------------

And attached is the CheckSUR.log file:

View attachment checksur181218.log

Thanks for all your help with this :)

Richard

 

[Sysnative Windows Update]

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put
   tags around the log to break up the text.

Afterwards, please run SURT again and attach CheckSUR.log.

Thank you.

 

[controlfreq]

Here is the latest results from the sfcfix and checksur log is below:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-12-19 12:33:42.066
Microsoft Windows 7 Service Pack 1 - x86
Using .txt script file at C:\Users\basil\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\38053612b8a..2734be08766_31bf3856ad364e35_6.1.7601.21890_c7854bb1cf4ec54d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\068d86b5f84..476b244cc28_31bf3856ad364e35_6.1.7601.17755_4fc10870c143895e.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6951941dcfe..2449c86450f_b03f5f7f11d50a3a_6.1.7601.17755_95b7bbef29f9d602.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\233ae0eae3e..ee44cfcbe2f_31bf3856ad364e35_6.1.7601.17755_cdaccb341c0752f3.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0d0ad5b5a44..35015c853ab_31bf3856ad364e35_6.1.7601.21890_b4d1f06915d82d13.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\89ff0f8d6c7..332470364df_b03f5f7f11d50a3a_6.1.7601.21890_5ebdee172a8dabe7.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\777e9a2a2b7..15cb737657b_b03f5f7f11d50a3a_6.1.7601.21890_bec4c2cb5134f74a.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5789a43f079..6aa04352011_b77a5c561934e089_6.1.7601.21890_06cf94c38c73fc0b.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\cbb695b4db9..974af73df76_b77a5c561934e089_6.1.7601.21890_6e2c227e7d09b11b.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4cf5ed4ffbc..68e961eeb74_31bf3856ad364e35_6.1.7601.17755_1575c2ff221f0406.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\38053612b8a..2734be08766_31bf3856ad364e35_6.1.7601.21890_c7854bb1cf4ec54d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\068d86b5f84..476b244cc28_31bf3856ad364e35_6.1.7601.17755_4fc10870c143895e.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\6951941dcfe..2449c86450f_b03f5f7f11d50a3a_6.1.7601.17755_95b7bbef29f9d602.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\233ae0eae3e..ee44cfcbe2f_31bf3856ad364e35_6.1.7601.17755_cdaccb341c0752f3.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\0d0ad5b5a44..35015c853ab_31bf3856ad364e35_6.1.7601.21890_b4d1f06915d82d13.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\89ff0f8d6c7..332470364df_b03f5f7f11d50a3a_6.1.7601.21890_5ebdee172a8dabe7.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\777e9a2a2b7..15cb737657b_b03f5f7f11d50a3a_6.1.7601.21890_bec4c2cb5134f74a.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5789a43f079..6aa04352011_b77a5c561934e089_6.1.7601.21890_06cf94c38c73fc0b.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\cbb695b4db9..974af73df76_b77a5c561934e089_6.1.7601.21890_6e2c227e7d09b11b.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4cf5ed4ffbc..68e961eeb74_31bf3856ad364e35_6.1.7601.17755_1575c2ff221f0406.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 30 datablocks.
Finish time: 2018-12-19 12:33:42.722
Script hash: 3hsvErAxHMXrXPJ23Icy3++WBmhPdqQCG5L1DQNypKw=
----------------------EOF-----------------------

View attachment checksur181219.log

Thanks again for all your help with this!

Richard

 

[Sysnative Windows Update]

Let's see if update will install now. If they don't provide CBS.log.

 

[controlfreq]

I tried installing one of the security updates on its own and it failed with the same error as before.

Here is the CBS.LOG file as requested

http://cottage.on.ca/components/cbs181220.zip

Thank you!

Richard

 

[Sysnative Windows Update]

Are there any language packs installed besides English?

 

[controlfreq]

Interesting that you mention that. The system behaves as if there are not any language packs installed, although I know I installed a group of language packs a long time ago for testing purposes (we develop language teaching software). Looking at the "Uninstall Langauges" window, it has listed Arabic, Chinese, Chinese (Simple), Hebrew, Japanese, Korean, and Thai but they do not appear to be selectable as input methods or displays. I have not tried uninstalling them or re-installing them as I have not had any need for any of them lately.

Richard

 

[Sysnative Windows Update]

Thank you. That explains a lot. Actually some of them are causing issues. Will provide more info as soon as I've had enough time to investigate.

 

[controlfreq]

I can uninstall them if needed. They are not being used right now for testing.

Richard

 

[Sysnative Windows Update]

I need a bit more info: What's the edition of the W7-32 Bit you're running?

 

[controlfreq]

It is Windows 7 Ultimate
Version 6.1.7601 Service Pack 1 Build 7601

 

[Sysnative Windows Update]

When checking for updates which are listed right now?

 

[controlfreq]

I went through the whole update process showing the missing updates as described below



I then ran the update and this is the (usual) result



After reboot, here is the update history



which brings the machine around to the starting point with the failed security updates



If you would like me to remove the language packs, I can do that as I don't need them.

Thanks!

Richard

 

[Sysnative Windows Update]

Attach CBS.log now please.

 

[controlfreq]

Here is the most recent CBS.LOG file:

http://cottage.on.ca/components/cbs190108.zip

Thanks for checking this for me.

Richard

 

[Sysnative Windows Update]

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log

 

[controlfreq]

Here are the files as requested

http://cottage.on.ca/components/logfile190108a.zip

http://cottage.on.ca/components/cbs190108a.zip

Thanks again !

Richard

 

[Sysnative Windows Update]

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

 

[controlfreq]

Ok, here is the output

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-10 11:36:40.130
Microsoft Windows 7 Service Pack 1 - x86
Using .txt script file at C:\Users\basil\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.23505 (win7sp1_ldr.160722-0600)\ComponentFamilies\x86_microsoft-windows-rdbss_31bf3856ad364e35_none_5c8570dc0c069136\v!6.1.7601.17514.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.23505 (win7sp1_ldr.160722-0600)\ComponentFamilies\x86_microsoft-windows-rdbss_31bf3856ad364e35_none_5c8570dc0c069136\v!6.1.7601.17514.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.23505 (win7sp1_ldr.160722-0600)\ComponentFamilies\x86_microsoft-windows-rdbss_31bf3856ad364e35_none_5c8570dc0c069136\v!6.1.7601.17514.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.23505 (win7sp1_ldr.160722-0600)\ComponentFamilies\x86_microsoft-windows-rdbss_31bf3856ad364e35_none_5c8570dc0c069136\v!6.1.7601.17514.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 31 datablocks.
Finish time: 2019-01-10 11:36:40.286
Script hash: 9vglPCejUAt/NBF40T+xQUie869h9AdyU2zjIlfqBjI=
----------------------EOF-----------------------

Thanks for all your help so far.

Richard