Can't get Windows Update to scan for updates 8024402F

Thanks.

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 the attached fixlist.txt 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.
 

Attachments

I ran it successfully, the key was removed. I also was able to get approval to uninstall Cylance, rebooted, still having 8024402F. Here's another run of the FRST tool scan.
 

Attachments

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system 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.
i3yiUac.png


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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
Here's another run of the FRST x64 tool. Do note, Cylance does auto reinstall after a daily scan happens to ensure it stays protected. Let me know if I need to remove it again and run this.

Thanks!
 

Attachments

This pretty much confirms that the root cause of your issues is your DNS Server, so a networking issue. Once you fix that, everything should work again.

Code: 
Error: (12/24/2019 01:24:05 PM) (Source: Microsoft-Windows-GroupPolicy) (EventID: 1129) (User: NT AUTHORITY)
Description: The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
 
I don't believe that's totally correct, while this is actually a secondary Domain controller, you had me change the DNS for primary and secondary to Google, thus why this is still showing that. I'll change that back to the typical setup where this secondary DC points to the primary DC first, and then to itself second, and add Google in for a 3rd. Should I re-run the FRST scan after making those changes?
 
I have changed back DNS and retried twice, still same error.

And thanks again, this is driving me nuts. Like I said it's happening on all 3 servers in this domain... we've only been looking at one of them so it would make sense a GPO or network problem would make sense but I can't pinpoint it anywhere. Our network team says there isn't anything blocking it outbound on the firewall, which is a Meraki.
 
Are you connected wired or wirelessly?

Is the latest version of IE installed and is it set as a default browser?

Can you tell me if this downloads for you: download.windowsupdate.com/msdownload/update/common/2012/04/4969820_309b12a082084485c7715c9e3337faaead34d1bb.cab

Also, let's clear cache and import the proxy settings from IE (if applicable). Note that the fixlist will reboot the Server.

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 the attached fixlist.txt 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.
 

Attachments

Internet explorer 11 version 11.0.9600.19503 Update Version 11.0.147 - not set as the default but will try now. That file downloaded fine, however it won't open it says, not sure if that is typical or not. Ran the FRST fix and rebooted, same problem. I had to put the Kaseya CMS software back on it, but it's on all of our clients and never experienced any other issues. Also, this is a physical Dell server on a wired connection. Here's another FRST run and CBS logs.
 

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