[SOLVED] Windows 7 PRO SP1 64-Bit Multiple Windows Update Failures from Dec 2018 On

Sysnative Windows Update · Mar 18, 2019

Who knows what really happened?

MEGA
MEGA
MEGA

malletKATman · Mar 18, 2019

softwaremaniac said:
Who knows what really happened?

“The answer, my friend, is blowin’ in the wind.
“The answer is blowin’ in the wind.”

Bob Dylan, 1962

Run for IE11-Windows6.1-KB3058515-x64.cab failed. See the IE11-Windows6.1-KB3058515-x64.cab Failure Logs.zip attachment.

The other two ran successfully.

Sysnative Windows Update · Mar 18, 2019

Hi!

Please run the following and then retry the update that failed.

Restart Windows in Safe Mode.

Download Windows Repair (All-in-One) Portable

Extract the tweaking.com_windows_repair_aio.zip to c:\Windows\TEMP the zip will extract to a folder called Tweaking.com - Windows Repair
Execute the file Repair_Windows.exe from the Tweaking.com - Windows Repair folder, accept the Security warning and the EULA
Click the button Jump To Repairs
Click the Open Repairs button to access the following screen:
Click the box All Repairs to uncheck all the boxes
Check only the following boxes:
- 16 - Repair Windows Updates
Check the box Restart/Shutdown System When Finished > Restart System
Click the Start Repairs button

malletKATman · Mar 19, 2019

Did your “Windows Repair (all-in-one) Portable” scenario, which was a bitch on this custom box because the F8 key during bootup does not go to a Windows Mode selection menu. Nonetheless I got it done using msconfig which doesn’t allow as many Safe Mode selections as F8 is advertised to allow. I had to use Minimum which meant I had to do the download and unzip before initiating Safe Mode. No matter, that could always be done safely as long as you don’t run Repair_Windows.exe until you get to Minimum Safe mode. It ran and I saw a few errors flash by in the small CMD screen; I don’t see any log that was created for that run.

Then I reran the IE11-Windows6.1-KB3058515-x64.cab dism run. It failed with probably the same overall 8-byte hexadecimal code, to wit:

CBS.log and DISM.log for that run, and the subsequent SURT run CheckSur.log are in the ZIP file.

malletKATman · Mar 22, 2019

malletKATman said:
[Repair_Windows.exe] ran and I saw a few errors flash by in the small CMD screen; I don’t see any log that was created for that run.

I see by further searching in the "Tweaking..." folder under C:\Windows\TEMP that there is a Logs folder. Sorry, any information that was there about the Repair_Windows.exe run is gone now; I should have looked in that folder before posting my last and included any files in that directory.

Sysnative Windows Update · Mar 23, 2019

Time to try some other stuff:

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a log should be created on your Desktop: SFCFix.txt.
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.

malletKATman · Mar 23, 2019

Code:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-03-23 09:25:50.503
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at E:\Users\Dick\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_0bfc08bf3ea166ba.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_0bfc08bf3ea166ba.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_0bfc08bf3ea166ba.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 2664 datablocks.
Finish time: 2019-03-23 09:25:51.611
Script hash: vS3nBwTRfFOR9RPUI73ZM60D9ItXhn99eVKqydy3qAo=
----------------------EOF-----------------------

Good hunting.

Sysnative Windows Update · Mar 23, 2019

Good job. Please run SURT again.

malletKATman · Mar 23, 2019

I asSURT

that there has been no change in the overall results since the previous SURT run on 03/18, despite running Repair_Windows.exe and your SFCFixScript.txt script in between, to wit:

-------------------------------------------------------------------------------

3/18 run:
Seconds executed: 272
Found 733 errors
CSI Missing Deployment Key Total count: 731
CSI Missing Winning Component Key Total count: 2

3/23 run:
Seconds executed: 323
Found 733 errors
CSI Missing Deployment Key Total count: 731
CSI C Mark Deployment Missing Total count: 2

-------------------------------------------------------------------------------

Sysnative Windows Update · Mar 23, 2019

But there has been a change in the results themselves and I can confirm that my latest fix has indeed been successful. Standby.

malletKATman · Mar 23, 2019

Oops, I was a little hasty. Running the marvelous File Comparator in Altap Salamander shows that the 03-18 and 03-23 CheckSURT.log files, neglecting trivial differences such as run date and run time, differ in only lines 750-751,757 in each file: a total Delta of only 3 lines (there are exactly 760 lines in both files), to wit:

Sysnative Windows Update · Mar 24, 2019

Yup!

Next fix

malletKATman · Mar 24, 2019

Code:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-03-24 23:06:30.611
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at E:\Users\Dick\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 imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\83df4998421..1e01bc60f57_31bf3856ad364e35_6.1.7601.23505_b473f4cfb35ad192.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\466e94be62b..55eba4b950e_31bf3856ad364e35_6.1.7601.23505_edde9cce537e65c5.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\83df4998421..1e01bc60f57_31bf3856ad364e35_6.1.7601.23505_b473f4cfb35ad192.
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\466e94be62b..55eba4b950e_31bf3856ad364e35_6.1.7601.23505_edde9cce537e65c5.
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.1.0 by niemiro has completed.
Currently storing 2667 datablocks.
Finish time: 2019-03-24 23:06:31.859
Script hash: LgbAji3Izvi8pv7csS0LRGezExO86K7n4OAq+O0tFmw=
----------------------EOF-----------------------

There 'tis, Boss, minus a few uneccessary [CR][LF]'s. Oops, forgot the SURT run you want after one of these. Coming right up.

Sysnative Windows Update · Mar 24, 2019

SURT :)

malletKATman · Mar 24, 2019

OK, your turn again. This looks like real progress.

Snickers · Mar 27, 2019

As expected

Sysnative Windows Update · Mar 31, 2019

You have not been forgotten, I'm just having trouble with some of the keys.

malletKATman · Mar 31, 2019

softwaremaniac said:
You have not been forgotten, I'm just having trouble with some of the keys.

No problemo.

malletKATman · Apr 7, 2019

Here is the link to a ZIP of my C:\Windows\system32\config\components file: Components 04-07-2019.zip . Note that the file in the ZIP file is named "components.xxx" in order to allow the ZIP file to be created, but in fact what I stated above at the time specified in the ZIP file. Note also that each time I send you a new ZIP file version it will replace the previous version, so you must download the current version before requesting a later copy.

malletKATman · Apr 12, 2019

[SOLVED] Windows 7 PRO SP1 64-Bit Multiple Windows Update Failures from Dec 2018 On

Inactive

Contributor

Attachments

Inactive

Contributor

Attachments

Contributor

Inactive

Attachments

Contributor

Inactive

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Attachments

Contributor

Inactive

Contributor

Attachments

Registered Member

Inactive

Contributor

Contributor

Contributor