Wndows 7 x64 Pro -- Security / Rollups always fail (0x80070057) -- Other types fine

softwaremaniac said:
Yes.
Click to expand...

I did the following:
1) Uninstalled MSE
2) Rebooted

Now Windows Update cannot search for updates.

Gives the error "Windows could not search for new updates" with the error code 8024402C.

I tried running the Windows Update Troubleshooter, letting it complete and rebooted again. I got the same error as above.
 
Restart Windows in Safe Mode w/networking.

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:
    WindowsRepair.png
  • 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
  • When the system reboots, attempt the updates again.
 
softwaremaniac said:
Okay.
Click to expand...

Partial success, the Security/Quality Rollups for the .NET Framework installed now when they did not in the past.

Am still getting failures with the Security Monthly Quality Rollup for Windows 7 (KB4480970) as well as the Cumulative Security Update for Internet Explorer 11 (KB4483187).
 
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.
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
 
For some reason, the latest ProcMon log wasn't particularly useful, please re-do it, but closer to failure + get my COMPONENTS hive:

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 to a file sharing service and just provide the link here.
 
softwaremaniac said:
For some reason, the latest ProcMon log wasn't particularly useful, please re-do it, but closer to failure + get my COMPONENTS hive:

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 to a file sharing service and just provide the link here.
Click to expand...

Components.zip
Logfile.zip
 
Step#1 - 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. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. 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).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.
 

Attachments

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