Error 80072efe in Windows Update on Windows 7 and 2012

If you receive Windows Update error 80072efe while checking for updates, it might be caused by an interrupted connection between your computer and the Windows Update servers. Error 80072efe mainly occurs on Windows 7 and Windows 2012, but may also pop up on Windows 10.

Fix Windows Update error 80072efe on Windows 2012 and Windows 7

On Windows 2012, the error 0x80072efe occurs when you install Windows 2012 with an old(er) ISO or installation DVD. The error may also occur when restoring the OS. In these cases, just install KB2937636. This patch updates some Windows Update binaries that are necessary to continue the Windows Update process.

Many users report the same problem, when they try to install windows server 2012, Some follow the advice to wait a few hours or reboot the computer, but it doesn’t help. It is required to update the Windows Update engine by installing https://www.microsoft.com/en-us/download/details.aspx?id=43434

For Windows 7, you may also solve the issue by installing KB3138612 or 3159706.
https://support.microsoft.com/en-us/topic/windows-update-client-for-windows-7-and-windows-server-2008-r2-march-2016-31422d0a-8818-cfdd-140e-e27883c7a2c5
Several users have reported that their error 0x80072efe in Windows 7 was fixed after installing these updates.

Fix Windows Update error 80072efe on Windows 10

If you face error 80072efe on Windows 10, the cause differs from Windows 7/2012. You probably have a firewall installed, or proxy server configured, that is blocking connections to the Windows Update servers.

The error code indicates: The connection with the server was terminated abnormally.

Providing a “fix for all” is not possible, but you could try the following:

1. Click Start, type cmd. Right-click Command Prompt and click Run as administrator.
2. Type “net stop wuauserv” without the quotes at the command prompt, and press Enter.
3. Delete (or put in recycle bin) the contents of C:\WINDOWS\SoftwareDistribution
4. Type net start wuauserv at the command prompt, and press Enter.
5. In the same command prompt, type netsh winhttp show proxy
   If this returns a proxy address, then this could be the issue. You could try to reset the proxy settings with netsh winhttp reset proxy. But only do this if you know what you’re doing. You may need to consult your system administrator, or an IT expert to configure the proxy.
6. Try Windows Update again.

Further reference and logging

Windows Update logs may display these passages in the WindowsUpdate.log :

WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
WARNING: Send request failed, hr:0x80072efe
WARNING: WinHttp: SendRequestUsingProxy failed for HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/6.3.9600.0/0?CH=717&L=en-US&P=&PT=0x7&WUA=7.9.9600.19670. error 0x80072efe

WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe

FATAL: SLS:CSLSDownloader::GetUrlContent: DoFileDownload failed with 0x80072efe.
FATAL: GetResponse failed with hresult 0x80072efe…
FATAL: EP: CSLSEndpointProvider::GetWUClientData – failed to get SLS data, error = 0x80072EFE
FATAL: EP: CSLSEndpointProvider::GetEndpointFromSLS – Failed to get client data, error = 0x80072EFE
FATAL: Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir Reporting URL, error = 0x80072EFE