The Windows 7 operating system, despite its attractiveness to ordinary users and system administrators who service server OS modifications, is not immune from the appearance of failures during the installation of important updates. One of the most common problems is the Windows 7 80072EE2 update error. It can appear in both server and desktop versions. You can fix the problem simply by taking into account the suggestions below.
Why is there a Windows 7 80072EE2 update error through WSUS?
First of all, it is necessary to find out the reason for the appearance of such a failure. First of all, note that for the proper operation of the WSUS service on the server where it is installed, several prerequisites must be met regarding additional software products and platforms.
This applies to the following components:
- ISS version 6 and higher;
- platform .NET Framework minimum of the second modification;
- SQL Server 2005 SP2 Express
- Report Viewer Redistributable 2008.
On the server itself, the following modules should be activated:
- ASP .NET
- Windows authentication
- IIS6 compatible management
- dynamic content compression.
Without observing the presented conditions, the server service for installing updates on child terminals will not work. And if it does, then the failure will appear in any case. But that is far from all. If we consider the situation when a Windows 7 update error occurs (code 80072EE2), in the general case (for both servers and child machines) its origin can be explained quite simply: when trying to access the Microsoft update server, the connection was broken. It’s hard to say what could block access, but there are several simple actions that, in most cases, help get rid of this failure.
Simple troubleshooting methods
Since it was originally a communication disruption, first you just need to check your Internet connection. If you use wireless, you may need to reboot the router with a complete reset.
If you use a proxy, you need to convince yourself that the settings are set correctly, and if necessary, configure the receipt of updates via IE. To do this, on the command line that started as administrator, you need to register the netsh command, then use the winhttp line, and then enter the import proxy import = source = ie command.
If such actions do not give the desired result, you can try to temporarily disable the antivirus, but it is better to go into its advanced settings and add to the exclusion list the entire directory in which updates are installed (WindowsUpdate).
If the Windows 7 80072EE2 update error still appears after that, you will have to use the firewall settings and, creating a new rule, add the following Microsoft servers to the exceptions:
- update.microrosoft.com (prefixed with http: //);
- download.windowsupdate.com (prefixed with http: //);
- update.microsoft.com (with the https: // prefix).
It is possible that a failure may occur after the above actions, so you have to move on to drastic measures.
Windows 7 update error 80072EE2 (WSUS): additional steps
First of all, you need to enter the programs and components section and view the list of installed updates. As you know, not all of them behave correctly, so unnecessary or failed updates must be removed.
This applies to package KB3072318. First, you need to uninstall it, and then specify a manual search for updates and exclude it from the list of updates to be installed so that it does not install in the future.
Finally, if the Windows 7 80072EE2 update error still appears after that, you can work with the update service itself. To do this, you must enter the system registry (regedit in the execution console) through the HKLM branch and through the SOFTWARE and Policies sections, find the WindowsUpdate directory and delete two parameters in the right part of the editor: WUServer and WUStatusServer. After this, a full restart of the system follows, and the failure, as practice shows, will not bother you anymore.
A few words in the end
It is by these methods that the Windows 7 80072EE2 update error is fixed. Immediately to say what was the reason for the failure, it is difficult enough, so you have to apply the solutions consistently. In some cases, you can try to restore the integrity of system files by setting the sfc / scannow line in the command console. If the system was exposed to a virus, an in-depth scan of the computer (server) can be used for threats. But usually, such actions are not required, and the failure is eliminated using the proposed methods.