Windows 7 SP1 64bit - Cannot update KB4474419 or KB4516065

Do you use some kind of cleaning tools, registry optimizers or so ?
It seems like registry fixes are removed again.
 
I don't use registry cleaning software (those are problematic). The only programs I use are MalwareBytes and Avast (but Avast is not presently installed, and hasn't been during this issue). Programs typically running in the taskbar are:
- Discord
- Google Hangouts
- Slack
- NVIDIA
- MalwareBytes
- Sades Gaming Headset
- VMWare
- Brother Printer stuff
- Intel Rapid Storage
- UltraMon
- Logitech WebCam

The only thing I do periodically is a disk clean using Windows Disk Cleanup, but I would be surprised if that is causing this issue.
Last week I installed more updates in Windows Update (most succeeded, except for the two listed on the title of this thread). That could have done something to the registry that affected this? Maybe? No clue.

Also play Call of Duty Warzone, which is always updating, but can't imagine that is doing anything for this (unless the anti-cheat software is doing something hokey).
 
Hmmm. It is possible that the Windows Update is restoring registry settings when the KB fails and reverts back. That might make sense here.
 
It is possible that the Windows Update is restoring registry settings when the KB fails and reverts back. That might make sense here.
Click to expand...
Maybe, but it would be weird if Windows removes legit keys.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Maybe, but it would be weird if Windows removes legit keys.
Click to expand...
Is it possible that its not so much removing legit keys as more its the modified keys aren't surviving a possible restore point after reverting from failed update? That's the only thing I can think of as there is no other software I am using that should be messing with this area of the registry. At any rate, the restore point in this last fixlist "should" prevent that from happening again, if that was it.

Fixlog attached
 

Attachments

the restore point in this last fixlist "should" prevent that from happening again, if that was it.
Click to expand...
Yes, that was my intention.

Please check Windows Update and report the result.
If it fails, attach the zipped cbs.log to your next reply.
 
Indeed, I'm almost out of options.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Please check Windows Update and report the result.
If it fails, attach the zipped cbs.log to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Please check Windows Update and report the result.
If it fails, attach the zipped cbs.log to your next reply.
 

Attachments

Failed. Logs attached.

Note: Sometimes the update is attempted through Windows update and sometimes it is attempted from the downloaded KB. The last two attempts were tried running the downloaded KB. Let me know if that matters to you (with investigating the logs or anything).
 

Attachments

FRST Registry Search
  1. Click the Start button and choose Control Panel.
  2. In the upper right corner ensure the View by: is set to Category.
  3. Select the Programs group.
  4. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog.
    Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  5. Right-click on the file FRST64.exe and choose Run as administrator.
  6. Copy and paste Microsoft-Windows-LSA/Operational;Microsoft-Windows-LSA/Diagnostic into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Perform the instructions in message #98 again.
 

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