[SOLVED] Windows Server 2012 Datacenter (clean install) error code 80072EFD

F

Filon

Member
Joined
Dec 13, 2021
Posts
10
I've got Windows Server 2012 Datacenter, I've installed dozen of systems (virtual machines) over the years, there where no windows update problems with it. What's more there are several system still running that version and they all update just fine.
But couple of weeks ago I've installed a new virtual machine with it and got error code 80072EFD when running windows update on a clean install. I'm not using proxy or WSUS., I've reinstalled it couple of times, I've tried everything I can find on the internet (restarting services, running scripts, deleting windows update folders) nothing works so far.
SFC scan found some corruption and fix it, SFCfix found no corruption. Still... 80072EFD :/
 

Attachments

It appears that a few things were claimed to have been repaired, could you please try installing updates again?
 
Filon said:
running scripts, deleting windows update folders)
Click to expand...
Do you know which folders you deleted or scripts you ran? It seems that something is blocking your connection to the update server(s).

Could you please run the log collection tool from these posting instructions? It'll provide some generic troubleshooting logs which might be helpful.
 
Okay, could you please provide the logs as suggested? It may be worthwhile comparing the firewall settings between your working VMs and the one which is not updating correctly.
 
Hmm "Sysnative BSOD Posting Instructions For Windows 10, Windows 8 / 8.1, Windows 7, Windows Vista Systems Only!!" and we're talking about win server 2012...

We use UTM and as I said before old instalations are working fine so I don't think it's a firewall problem.
 
Filon said:
Hmm "Sysnative BSOD Posting Instructions For Windows 10, Windows 8 / 8.1, Windows 7, Windows Vista Systems Only!!" and we're talking about win server 2012...
Click to expand...
It works with Windows Server 2012; Windows 8.1 and Windows Server 2012 are basically the same operating system. The only difference are which features are available.
 
Unfortunately, I couldn't find anything particularly interesting in your event logs. Could you please provide the WindowsUpdate.log file, it should be available in the following location:

Rich (BB code): 
%systemroot%\Logs\WindowsUpdate
 
Rich (BB code): 
2021-12-28    08:03:46:564     720    4bc    Report    REPORT EVENT: {FD8167D8-25E4-429F-9122-A21B998750F7}    2021-12-28 08:03:41:565+0100    1    148 [AGENT_DETECTION_FAILED]    101    {D67661EB-2423-451D-BF5D-13199E37DF28}    1    80072efd    SelfUpdate    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80072efd.
2021-12-28    08:03:46:564     720    4bc    Report    REPORT EVENT: {CC1D57BA-FF9B-4AB8-B057-929BF92034BB}    2021-12-28 08:03:41:565+0100    1    149 [AU_UNABLE_TO_CONNECT]    102    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Failure    Software Synchronization    Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.

There's quite a few errors for this file too:

Rich (BB code): 
2021-12-13    13:39:35:476     288    754    Misc    WARNING: WinHttp: SendRequestUsingProxy failed for <https://fe2.update.microsoft.com/v11/3/win8/windowsupdate/selfupdate/wuident.cab>. error 0x80072efd
2021-12-13    13:39:35:476     288    754    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2021-12-13    13:39:35:476     288    754    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efd
2021-12-13    13:39:35:476     288    754    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efd
2021-12-13    13:39:35:476     288    754    Misc    WARNING: DownloadFileInternal failed for https://fe2.update.microsoft.com/v11/3/win8/windowsupdate/selfupdate/wuident.cab: error 0x80072efd
2021-12-13    13:39:35:476     288    754    Setup    WARNING: SelfUpdate check failed to download package information, error = 0x80072EFD
2021-12-13    13:39:35:476     288    754    Setup    FATAL: SelfUpdate check failed, err = 0x80072EFD
2021-12-13    13:39:35:492     288    754    Agent      * WARNING: Skipping scan, self-update check returned 0x80072EFD
2021-12-13    13:39:35:492     288    754    Agent      * WARNING: Exit code = 0x80072EFD

As a little experiment, please boot into the VM and open a web browser, please enter the following URL:

https://fe2.update.microsoft.com/v11/3/win8/windowsupdate/selfupdate/wuident.cab

You should be able to download the file with no issues; at least I was able to on my machine.
 
Which browser did you use? I've just been reading through some old threads of users who've experienced the same issue, and one reported that it failed when attempting to download using Internet Explorer. It turns out for some reason the firewall settings were configured to block any connections through Internet Explorer.

I know, Internet Explorer used to be embedded into the operating system itself and was considered a "system" component.
 
If possible, could you please open an elevated command prompt and then enter the following command:

Rich (BB code): 
netsh advfirewall reset

This will reset the Windows Firewall to it's default settings. I understand that you mentioned that it's a clean install and previous VM installations were working with no issues, however, it's worth trying so we can rule it out as an issue.

If it doesn't work, then we can capture a Process Monitor trace and see if it shows us anything useful. Otherwise, I'll request some help from a more experienced helper with this issue.
 
Could you please provide a Process Monitor trace using the following steps:

Capture Process Monitor Trace
  1. You will need to run Process Monitor.
  2. Try to start Process Monitor as close as you can to when the failure occurs while attempting to install an update (within 1-5 minutes of failure).
  3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL + E) on the toolbar as shown below.
    ProcMon Capture.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. Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
OK I think I fixed.
I've installed KB2937636, which updated WU client and it downloaded and installed over 130 updates.

thx for help anyway!
 
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