It’s worth reading these recovery methods when you get a Windows 2003 error with error number 0x80072ee2.
Recommended: ASR Pro
Windows R2 2003 Update Crashes With Error Number 0x80072EE2
How do I fix error 0x80072EE2?
Check your Internet connection.Turn off the firewall.Use an unobtrusive antivirus program.Add exactly the Windows Update servers to the whitelist.Run the Windows Update troubleshooter.Reset Windows 10 update components.Run an SFC scan.
After mounting Windows Server R2 2003 in a virtual machine for a quick test, I applied SP2, rebooted, and then went to Windows Update to download the expected number of Windows fixes. However, Windows update failed several times and the browser window displayed “Error number 0x80072EE2”. Windows Update How to update “Microsoft Update” but withIE6 on IE 8 didn’t really help, neither did deleting the SoftwareDistribution folder.
Surprisingly, disabling Windows Firewall solved the problem. Below is a specific link to an article that describes how *turning on* the firewall solves exactly the same problem. With well-patched servers and after re-activating the firewall software, I still see the same behavior (117 patches have been installed since SP2). Not yet sure if automatic updates (no browser) duplicate the problem with the firewall enabled.
I can’t use Windows Update or Microsoft Update. Error 80072ee2. The operating system is a Windows 2003 R2 x86 server with Slipstreaming SP2. The server was freshly installed, sometimes only additional software was installed, usually “VM Ware Tools” KB923845 and (MSI 4.5). not for WSUS, no PROXY, all DNS caches flushed (there is a DC due to DNS and now no DNS forwarders are configured)
I tried to solve this problem by searching microsoft.com and other sites.Max within the last 26 hours. nothing is compatible. so please help if you have any ideas. I also used http://support.microsoft.com/kb/836941/en-us and removed C:WINDOWSSoftwareDistribution.
2010-02-05 17:27:05:952 808 de0 Report * Bios Name=4 phoenixbios.0 Release 6.0
2010-02-05 17:48:37:085 84 Installation update 304 NOT required for C:WINDOWSsystem32wuweb.dll: target version = 7.4.7600.226, required variant = 7.4.7600.226
2010-02-05 17:48:37:382 304 84 install update DO NOT prompt for .dll C:WINDOWSsystem32cdm: target version implies 7.4.7600.226, required version = 7.4.7600.226
02/05/2010 17:48:37:382 304 84 Update installation NOT required C:WINDOWSsystem32wuapi for .dll: select target=7.4.7600.226, version 7.4.7600.226 is required
2010-02-05 17:48:37:382 304 84 installation update NOT required C:WINDOWSsystem32wuapi for.dll.mui: target version = 7.4.7600.226, production required = 7.4.7600.226
2010-02-05 17:48:37:382 304 84 Updated install to NOT get C:WINDOWSsystem32wuauclt.exe: target version means 7.4.7600.226, required version = 7.4.7600.226 < /p>
2010-02-05 17:48:37:382 84 Install update 304 NOT required for C:WINDOWSsystem32wuaucpl.cpl: rendering target=7.4.7600.226, required version implies 7.4.7600.226
2010-02-05 17:48:37:382 84 Device updateNew 304 is NOT required for C:WINDOWSsystem32wuaucpl.cpl.mui: target version = 7.4.7600.226, plan required = 7.4.7600.226
2010-02-05 17:48:37:382 304 84 Update NOT required C:WINDOWSsystem32wuaueng for .dll: target version is 7.4.7600.226, required version is 7.4.7600.226
2010-02-05 17:48:37:382 304 84 update NOT required C:WINDOWSsystem32wuaueng for.dll.mui: target version = 7.4.7600.226, required version implies 7.4.7600.226< / p>
2010-02-05 17:48:37:382 304 84 Update required for installation, not for C:WINDOWSsystem32wucltui.dll: target version = 7.4.7600.226, model required = 7.4.7600.226
2010-02-05 17:48:37:382 304 84 Installation update required not only for C:WINDOWSsystem32wucltui.dll.mui: target version 7.4.7600.226, required version = 7.4.7600.226< / p>
2010-02-05 17:48:37:382 304 84 Update installation NOT for C:WINDOWSsystem32wups.dll required: other target = 7.4.7600.226, required version is 7.4.7600.226
2010-02-05 17:48:37:382 304 84 Install update NOT for C:WINDOWSsystem32wups2.dll required: target version = 7.4.7600.226, required product = 7.4.7600.226
02/05/2010 17:48:44:400 808 Agent 4v4 * Online is Yes; Ignore download priority enables agent check 808 4c4 no
2010-02-05 17:48:44:463 for updated auth-cab for service 7971f918-a847-4430-9279-4a52d1efe18d at
2010-02-05 17:49:46:821 808 4c4 Miscellaneous WARNING. Error sending request with hr=80072ee2. Proxy list used: <(null)> Bypass list used: <(null)> Authentication schemes used: <>
2010-02-05 17:49:46:821 808 4c4 PT+ Last proxy transfer request failed, hr is 0x80072EE2, HTTP status code = 0
2010-02-05 17:49:46:821 808 4c4 PT WARNING: error, sync error = 0x80072EE2, cleaning soap client error = 5, detergent error code = 0, area code d ‘HTTP status = 200< /p>
2010-02-05 17:49:46:837 Agent 808 4c4 WARNING: WU client could not check for updates due to fault 0x80072ee2
2010-02-05 17:49:46:852 304 7ec COMAPI – WARN: exit code 0x00000000, result code = 0x80072EE2
Is Windows 2003 still supported?
Microsoft is ending purchase support for the Windows Server 2003 operating system on J.  As a result of this incident, this product will no longer have: Security fixes that protect PCs from harmful viruses, spyware, and other malware. Help with technical support outside of Microsoft.
2/05/2010 17:49:51:849 808 4c4 Report REPORT EVENT: 4EDFF7D4-3EDC-4231-B875-BDC9A52EBB5C 02/05/2010 17:49:46:821+0100 1,000-0.00 .00 – 0 -0000 000000000000 0 80072ee2 MicrosoftUpdate error Windows Update client software synchronization could not be detected with error 0x80072ee2.
Error 0x80072ee2 is a common error that occurs when, for whatever reason, the Update Center portalWindows is blocked. But this fact does not make it a complication of web hosting as it is limited to PC only.
Causes Of Error 0x80072ee2
- The router’s MTU settings are too low or incredibly low.
- If you are using Norton Security 2003, access may be inconvenient.
- A firewall that is blocking your computer or your local network may be preventing you from connecting to the Windows Update site.
- Proxy realms are interfering with your connection, which helps the Windows Update site.
Method 1: Optimize Your Firewall Settings
Update or possibly reconfigure your firewall to ensure that the firewall is not blocking your access to the Windows Update site. Sometimes it happens that the firewall is probably preventing the system from connecting to an active connection and crashing the site.
If the problem persists today, you may need to disable your firewall for a while. For this:
- Click Start.
- From the Start menu, select Control Panel.
- In the Control Panel window, find the search field. If you find,Enclose the firewall in double quotes.
- Once you see specific Windows firewalls in the search results, select them.
- Typically, click the “Turn Windows Firewall on or off” link you see on the left.
- If prompted for an administrator username and password, enter them.
- Now some public network settings.
- Click OK to apply the changes.
- If you are still experiencing the same error, your firewall is fine, so please activate the software following the same steps.
Speed up your computer for free today with this powerful download.