In this article, we will guide you through the most complete guide for solving the Windows update error 80072ee2.
Windows errors are notoriously difficult to solve, especially errors related to Windows updates because they all returning a general message without further information.
Error 80072ee2 is common in all versions of Windows, starting from Windows 7/Windows Server 2008 R2 to Windows 10/Windows Server 2019. This error can appear when you are installing updates via the local WSUS server or when downloading updates directly from the Windows Update Center over the Internet.
80072ee2: Why is This Error Occurs?
First of all, you have to know what causes this error. When you try to connect to the Windows server to download the latest updates, the system is unable to establish a connection, hence the error message that is displayed on your screen.
Windows could not search for new updates, An error occurred while checking for new updates for your computer. Error(s) found: Code 80072EE2
Possible Solutions for the Windows Update Error 80072ee2
Error code 80072ee2 according to the Windows Update error table on the MSFT site is interpreted as follows: ERROR_INTERNET_TIMEOUT (-2147012894) The request has timed out. This means that the system cannot access the Microsoft Update or WSUS sites.
Solution 0. Run Windows 10 Update Troubleshooter
If you face an error 80072ee2 in Windows 10, you can try to fix the Windows Update service and related components errors automatically. To do this, use Windows Update Troubleshooter – a powerful built-in Windows 10 error troubleshooting subsystem that has repeatedly helped me solve a problem with Windows Update.
Open the Control Panel > System and Security > Troubleshoot common computer problems > select Windows Update > press the button Run the troubleshooter.
Wait for the wizard to finish and check for the Windows Update.
Tip. You can download Windows Update Troubleshooter for Windows 7 and 8.1 here.
Solution 1. Check Your Internet Connection and Access to Windows Update Websites
First of all, it is recommended to check that your computer can access the Internet. Run your favorite browser app and try to open the following URL. If the access to the site is available, the following picture will appear:
Solution 2. Check Proxy and Firewall Settings
Check if you are using a proxy server. If you do, double check the settings in the Internet Explorer and make sure that the proxy does not require a username or password to connect. If it does, the easiest way is to disable the proxy server during the duration of the windows update, although you can also create a workaround by setting your firewall to allow the connection to the Windows Update directly without going through the proxy.
If you are connecting to the Internet through a firewall, make sure that the following websites addresses are allowed in its settings:
HTTP: //*.update.microsoft.com HTTPS: //*.update.microsoft.com http://download.windowsupdate.com
If you can access the Internet from your local network only through a proxy server, you can check the system proxy settings as follows.
List the current system proxy settings for WinHTTP:
netsh winhttp show proxy
If the previous command returned the following message:
Current WinHTTP proxy settings:
Direct access (no proxy server).
Go to the next solution.
Solution 3. Reset System Proxy Server Settings
If your computer has been infected with spyware in the past — or it is at the moment — then the spyware might have modified your Internet Explorer settings to use a proxy server.
If the netsh winhttp show proxy command returned the current proxy settings for WinHTTP and you see that they are incorrect, you can clear them. Open the cmd.exe utility (by typing CMD in the Start menu) and run the following command:
netsh winhttp reset proxy netsh winhttp import proxy source=ie
You can also specify the proxy server settings manually (if you know the proxy server address and the connection port):
netsh winhttp set proxy proxy-server="192.168.1.11:3128" bypass-list="*.yourlocaldomain.com"
It remains to restart the Windows Update service:
net stop wuauserv & net start wuauserv
Solution 4. Re-register WU dlls
Some dll files might have become unregistered—due to various factors—which could trigger the Windows update error 80072ee2. In this case, open elevated cmd.exe, and re-register some dlls by pasting the following lines:
regsvr32 oleaut32.dll regsvr32 jscript.dll regsvr32 vbscript.dll regsvr32 softpub.dll regsvr32 msxml.dll regsvr32 wintrust.dll regsvr32 initpki.dll regsvr32 cryptdlg.dll
- Open the services management console (Services.msc);
- Find the Windows Update service and stop it;
- Run the File Explorer, go to the C:\Windows\SoftwareDistribution directory and clear (delete) all contents in this folder (Ctrl+A -> Delete);
- Start the Wuauserv service.
Solution 5: Reset Windows Update Agent Setting
You can reset the current agent and Windows Update services settings using the ResetWUEng script. Download ResetWUEng.cmd from Microsoft TechNet Gallery (https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc) and run it as administrator.
Select the menu item 2 in the script (Resets the Windows Update Components).
After completing all the steps, restart the computer (item 17).
Solution 6: Change MTU Setting to 1492
A wrong MTU setting can also cause 80072ee2 error. This is the rarest occurrence that may cause the 80072ee2, but your computer’s MTU setting might be incorrect.
Check the current MTU value:
netsh interface ipv4 show subinterfaces
In our case, the default MTU value for the main network LAN interface (Ethernet 0) is 1500. You can change the MTU value to 1492 with the command:
netsh interface ipv4 set subinterface "Ethernet" mtu=1492 store=persistent
If another non-standard MTU value is used, you can reset it with the command:
netsh interface ipv4 reset
In this case, you simply have to set the MTU value to 1492 and try Windows Update again.
Solution 7. Fixing Error 0x80072ee2 Then Updating via WSUS
If you receive Windows Updates from the internal Windows Server Update Services (WSUS) server, open the Registry Editor (regedit.exe) and go to branch: HKEY_Local_Machine\Software\Policies\Microsoft\Windows\WindowsUpdate and check the WUServer and WUStatusServer. Verify that the correct WSUS server names are specified here.
If you don’t want to use internal WSUS (but you want to receive updates directly from Windows Update), remove these parameters from the registry and restart the “Windows Update” service with the command:
net stop wuauserv && net start wuauserv
Solution 8. Lack of Resources in the AppPool WSUS
If you are using the WSUS server to distribute Windows Update to your clients, perhaps the error is due to a lack of resources in the WSUS IIS AppPool on a server. The solution is to remove the limit on the consumed memory.
Open IIS Manager Console > Application Pools > WsusPool > Advanced Settings. Change Private Memory Limit to 0 and restart IIS.
Solution 9. Error 80072ee2 on a Guest VM on Hyper-V
Sometimes when using Hyper-V, you may encounter a situation where Windows does not want to update inside the virtual machine (we ran into this on Windows Server 2008 R2). The system gives an error 80072EE2 and does not give any explanation. As it turned out, the error is related to the transmission parameter of large packets in the properties of the host network card. As a host, we have a physical server on which Hyper-V is deployed.
To solve the problem, run the Device Manager on the Hyper-V host and open the properties of the physical network card:
Then go to the Advanced tab, find and disable 2 settings Large Send Offload V2 (IPv4) and Large Send Offload V2 (IPv6). These settings are responsible for segmenting the network adapter of large data packets.
Save the changes and perform a new update search on the virtual machine.
These are all possible solutions to the Windows update error 80072ee2. In case you still cannot fix the error, leave a comment below and we will try to assist you.