A Windows update error 80072ee2 is not hard to fix, but the process can be arduous and convoluted. That’s why we have a guide on how to go about this problem for you!
Errors are inevitable when using a computer, but some issues are harder to fix than others. Today, we will be examining Windows update error 80072ee2 – one of the most time-consuming faults you may encounter on your PC. Let’s learn how it happens and how to fix it in this article!
Why Do I Have This Error On My Windows?
Before you can even attempt to get rid of the error of your devices, you will need to find out what the roots of it are.
Have you recently tried to form a connection to a Windows server to bring your device to the newest running versions? If you have and you’ve failed, that can possibly be the root of the problem. Specifically, a notification will pop up when the connection fails and let you know that you need to look for this guide!
Different people may see different notifications displayed, such as “Windows can’t find any updates,” but the solution should be the same. Scroll down to get started!
Windows Update Error 80072ee2: How To Fix
Whether it’s failing to connect to Windows due to request timeout or the Internet is weak, you already have the error on your device. Now, let us get to fix it below.
Step 1: Check Your Windows Settings:
Look to the lower right corner of your screen, and see if your time and date settings are correct. You might want to check with a second device or your browser to the tee to get the right numbers. Surprisingly, incorrect time and date settings are possibly the most common causes as to why you have connection issues.
If you have identified this as the root of your error, head to Windows Settings and redo the numbers to fit your timezone. Additionally, you should also enable automatic updates so you do not have to go back here and do the task again.
Step 2: Check Windows Update:
We are sure that you do not have Internet connection issues because you are currently consulting this article (which is on the Internet). But we do advise towards double-checking, in case you have this website saved already. Please close this window and switch up the browser again if it runs smoothly.
If you have finished the step above and your computer still does not connect to update Windows, it can be the system’s failure instead of yours. In detail, you can log into “isitdownrightnow.com” to see if Windows Update’s services are still working.
If you happen to be one of the unlucky ones whose screen says that the server is down, there’s nothing left to do but try to do your work on a different device until Microsoft does their job properly again.
Step 3: Run Troubleshooter:
When Microsoft’s server is back on, the next step in this guide is to use the system to fix systematic errors. Specifically, Windows Troubleshooter is great at finding faults in itself and helping you with a guide to correct what is wrong as well.
The best thing about Troubleshooter, aside from its efficiency, is the fact that you already have it on your Windows 10. Those who use an older version of Windows like 80072ee2 Windows 7 will not have this built-in feature.
Here is how you can start the process:
- At Windows Settings (accessed through the key combo Win+I), you can click on the “Update and Security” – “Troubleshoot” tab. There will be a button that says “Windows Update” there, which will allow you to start running the troubleshooter!
- Once the troubleshooter does its round of checkups, you will need to wait for a while. Upon receiving the diagnosis/report of all the things corrected by the troubleshooter, you can download the updates once more.
Step 4: Check Proxy And Firewall Settings:
If you are currently using a proxy server, error code 80072ee2 is likely to come up, especially 80072ee2 Windows 7. Proxy servers usually do not ask you to input your login credentials before you can form a connection.
Once the server does so, you can disable it while you’re downloading Windows Updates. Moreover, if you allow the proxy server to interfere with the update process, your computer will show the error “Windows update client failed to detect with error 0x80072ee2” and refuses to let you through.
You can also work around this feature without manually switching off proxy by adjusting the settings you have on your current firewall. When you do, make sure these are the websites that can make their way to your PC:
- HTTP: //*.update.microsoft.com
- HTTPS: //*.update.microsoft.com
In case you can only surf the Internet with a proxy server, there are certain changes you can make to the servers’ current features. Login to the administrator’s role and punch this line into Command to check proxy settings:
“netsh winhttp show proxy
If you don’t use a proxy server, or the return goes as the image above, scroll down further to the next solution.
Step 5: Set Proxy Server Settings Again:
Check if the original adjustments you make to the server are still the same. The difference in your proxy server settings can signify that there is either spyware or malware on your device. Also, your antivirus should be able to pick this up and work the problem out for you just fine.
If the output from Step 4 matches with what you have set on your system, then that’s fine. All you have to do now is reset and readjust the features so “code 80072ee2 Windows update” can be solved. Below are the process of resetting proxy servers:
- Switch up Command Prompt like before.
- Punch in this command:
“netsh winhttp reset proxy
netsh winhttp import proxy source=ie”
- If you wish to manually inquire about a specific server’s settings, you can punch the server’s address in with the following command:
“netsh winhttp set proxy proxy-server=”192.168.1.11:3128″ bypass-list=”*.yourlocaldomain.com””
- The final step of this process is to restart Windows Update by entering this line:
“net stop wuauserv & net start wuauserv”
You can also troubleshoot proxy servers to solve windows 7 update error 80072ee2. However, that process is rather convoluted, so we decide to leave it out of this guide.
Step 6: Undo and Redo Register Windows Update DLL Files
Through your uses, the DLL (also known as dynamically linked libraries) files can expire due to the changes you make on your device. You will not necessarily lose the files; rather, they unregister themselves or become corrupted and no longer fit your system.
Corrupted DLL files can cause the error “Windows update client failed to detect with error 0x80072ee2”. If this is the case with your PC, open the Command Prompt window once more to get your files back into their former glory. To be more specific, the process will go like this: Paste every line of this list into the text box:
- regsvr32 oleaut32.dll
- regsvr32 jscript.dll
- regsvr32 vbscript.dll
- regsvr32 softpub.dll
- regsvr32 msxml.dll
- regsvr32 wintrust.dll
- regsvr32 initpki.dll
- regsvr32 cryptdlg.dll
After that entire fiasco, you should stop Windows Update from clearing its cache and relaunch the program. This gives you a clear view of whether or not the code 80072ee2 Windows update error has been fixed yet.
Here is the procedure on how to do that:
- Use the key combination “Windows + R” to open the Run window. From there, you can type “services.msc” in the text box.
- The command should give you a list, from which you can pick out “Windows Update” to prevent it from proceeding further.
- Next, at File Explorer, you can head to a folder called C:\Windows\SoftwareDistribution and delete everything inside there.
- Once you’re done, you can head back to the Services window and restart the Windows Update process again to make sure there’s no-fault this time round.
Step 7: Rewire Windows Update Agent Setting
If you’re familiar with the ResetWUENG script already, then you can rewire your agent and adjust Window Update services as well. You should download the cmd file from Microsoft TechNet Gallery (to prevent additional malware) and run the script after switching to the Administrator role.
You can select the second item that initiates “Resets the Windows Update Components” from the list above. You can safely restart your PC afterward with the 17th item on the list by following the procedure.
Step 8: Switch From MTU Settings to 1492
This could be the rarest reason behind “Windows could not search for new updates Windows 7”, but we cannot exclude it from this list. After opening the Command Prompt window, you can start to examine the MTU value in the settings with this line:
“netsh interface ipv4 show subinterfaces”
In our example screenshot, you can see that the MTU value for the main network is 1500 instead of the correct 1492. Type this line in to fix this fault:
“netsh interface ipv4 set subinterface “Ethernet” mtu=1492 store=persistent”
If any other number showed up in the spot, you should reset it instead of adjusting with this line:
“netsh interface ipv4 reset”
Step 9: Tackle Error 0x80072ee2 Before Updating Via WSUS
If you’re one of those people who got the updates from the internal server instead, you may have to head to the Registry Editor (regedit.exe) and use the main key:
From there, you might want to double-check if the server names are in their place to form connections to the servers.
But if you want to have direct updates without using the internal system itself, you can remove the WUServer and WUStatusServer straight from the table. After deletion, you can restart the service using this line:
“net stop wuauserv && net start wuauserv”
Step 10: Tackle Error 0x80072ee2 Before Updating Via WSUS
If you and your clients’ servers are having problems with WSUS, you can try adding more resources into the AppPool. More specifically, this can be done by deleting the limit on the memory functions.
The steps go as follows: IIS Manager Console > Application Pools > WsusPool > Advanced Settings. As a result, you can change the memory limit and restart the program.
Step 11: Check For Error 80072ee2 On Guest VM – Hyper-V
Occasionally, you will notice that Windows will refuse to update while using Hyper-V. The system will send you the same error as we’ve mentioned before as 80072ee2 and not a legitimate explanation.
If you want to solve this problem, you can run Device manager on Hyper-V and examine the features of the network card:
Step 12: Make Adjustments To Windows 7/2008R2 To Support SHA-2 Endpoints
- SHA-2 Code Signing Support Upgrade:
This update will prove its usefulness by allowing your PC to accommodate signatures by securing the SHA-2 hashing algorithms:
KB4474419 — SHA-2 code signing support update (Windows 7 SP1, Windows Server 2008 R2 SP1);
KB4484071 — SHA2 support for your WSUS server running Windows Server Update Services 3.0 SP1 or 3.2.
- Update 2: SHA-2 Related Servicing Stack Upgrades:
The rare cases where you have to manually install this update is where you have to allow SHA-2 signatures to affect Windows devices. This will also secure service endpoints for Window Update!
- KB4490628 — Servicestack update for Windows 7 SP1 and Windows Server 2008 R2 SP1;
- KB4493730 — WU Servicestack Updates for Windows Server 2008 SP2.
Step 13: Install Manual Updates Onto Windows
If all else fails, manuals are the solution! Just delete everything and try again.
Those are all the methods you can go to secure the Windows update error 80072ee2 from ever happening again. If you run into any problem during any solution runs, please do not hesitate to reach out and inform us about it. We wish you luck in your future endeavors!
Maybe you are interested in