[SOLVED] Windows 7 x64 failing to install updates

A

Amarix

Active member
Joined
May 12, 2018
Posts
25
Hey, I've been having some trouble lately updating my PC. As of now I have 13 important updates that won't install, I've tried to rename and delete SoftwareDistribtution and Catroot2 to no effect. Also tried to manually install some of the updates, no hope there either. Here's my CBS log Dropbox - CBS.zip
Error Code: 80070308
Help is very much appreciated.
 
Hello and welcome!

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and 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.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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
 
Thanks!

Retrieve Components Hive
 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload toa file sharing service and just provide the link here.
 
Is it the COMPONENTS.LOG1 you mean? COMPONENTS file is just a 1kb txt file.
Nevermind found the one you meant :)
 
FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

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 file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - 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 SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Like this? :)
Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-05-13 14:09:15.280
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Stumpen\Desktop\SFCFix.zip [1]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuauclt.exe
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuaueng.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wups2.dll


WARNING: File C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuauclt.exe was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Stumpen\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuauclt.exe to C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuauclt.exe.
WARNING: File C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuaueng.dll was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Stumpen\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuaueng.dll to C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuaueng.dll.
WARNING: File C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wups2.dll was not backed up as that would replace the current backup.
Successfully copied file C:\Users\Stumpen\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wups2.dll to C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wups2.dll.


Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuauclt.exe
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuauclt.exe
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuaueng.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wuaueng.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wups2.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-w..wsupdateclient-core_31bf3856ad364e35_7.6.7601.23453_none_e7c00c697e579911\wups2.dll
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2018-05-13 14:09:15.491
Script hash: AxrpFA+KrMqs8ESSHdNFdp2iQBpcIGpoa8jwFGXqvQ4=
----------------------EOF-----------------------
 
FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 12.05.2018
Ran by Stumpen (13-05-2018 14:34:55) Run:2
Running from C:\Users\Stumpen\Desktop
Loaded Profiles: Stumpen (Available Profiles: Stumpen)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-w..ent-internalupgrade_31bf3856ad364e35_7.6.7601.23453_none_2bf9304da1a930d5]
"f!wu.upgrade.ps.dll"=hex:77,00,75,00,2e,00,75,00,70,00,67,00,72,00,61,00,64,\
00,65,00,2e,00,70,00,73,00,2e,00,64,00,6c,00,6c,00
EndRegedit:
*****************


Restore point was successfully created.


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========


Handlingen er gennemf›rt.




========= End of CMD: =========




====> Registry


==== End of Fixlog 14:34:59 ====
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and 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.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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
 
Thanks. That helped!

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 12.05.2018
Ran by Stumpen (13-05-2018 15:28:05) Run:3
Running from C:\Users\Stumpen\Desktop
Loaded Profiles: Stumpen (Available Profiles: Stumpen)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-directx-d3dcompiler_31bf3856ad364e35_6.1.7601.23796_none_eb8e769493af6438]
"f!d3dcompiler_47.dll_0491c69350b74c72"=hex:44,00,33,00,44,00,43,00,6f,00,6d,\
00,70,00,69,00,6c,00,65,00,72,00,5f,00,34,00,37,00,2e,00,64,00,6c,00,6c,00
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-directx-d3dcompiler_31bf3856ad364e35_6.1.7601.23796_none_47ad12184c0cd56e]
"f!d3dcompiler_47.dll_0491c69350b74c72"=hex:44,00,33,00,44,00,43,00,6f,00,6d,\
00,70,00,69,00,6c,00,65,00,72,00,5f,00,34,00,37,00,2e,00,64,00,6c,00,6c,00
EndRegedit:
*****************


Restore point was successfully created.


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========


Handlingen er gennemf›rt.




========= End of CMD: =========




====> Registry


==== End of Fixlog 15:28:09 ====
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top