Some Windows users are reporting that they end up seeing the error code 0x80072EE6 when attempting to update their virus signature on Windows Security, when attempting to install a pending Windows Server update or when attempting to update or install Windows Live Installer.
After investigating this particular issue, it turns out that there are several different underlying causes that might be causing this particular error code. Here’s a list of potential culprits that are likely responsible for this particular Windows error code:
- Incorrect Date and Time – In case you’re seeing this error while attempting to engage in data exchange with the WSUS Server Update Service, you need to start by ensuring that the correct time & date is set accordingly. If your date & time is off, the WSUS will simply refuse the connection.
- MSXML3.dll is not Registered – In case you’re encountering this issue while checking for new updates on your Windows or Windows Server computer, you’re likely dealing with a missing DLL dependency (msxml3.dll). If this scenario is applicable, you should be able to fix this problem by using an elevated Command prompt to re-register the missing dependency.
- Badly configured Group Policy for WSUS – According to a lot of affected users that were encountering this issue while attempting to download Windows Updates via WSUS, you can expect to see this error occurring in those instances where the Group Policy responsible for specifying the Microsoft download address is incorrectly configured. In this case, you can fix the issue by ensuring that the download address is correctly stored.
- Process conflict – As it turns out, you can expect to see this issue occurring after a major driver installation, after an important Windows update, or after the installation of a conflicting 3rd party service. Since there are a lot of potential culprits that might cause this issue, you should start by using a previously created System Restore snapshot.
- System File Corruption – According to some affected users, you can also expect to see this error in instances where you’re actually dealing with some underlying case of system file corruption that is affecting your computer’s ability to connect to the WSUS servers. In this case, resetting your Windows components with procedures like clean installing or repair installing should allow you to take care of the issue.
Now that you are familiar with every potential culprit that might be responsible for the 0x80072EE6 error code, here’s a list of methods that other affected users have successfully used to get to the bottom of the issue.
Method 1: Set the Correct Time and Date
Keep in mind that if you’re encountering this problem while attempting to engage in data exchange with a WSUS (Windows Server Update Services) server, the first thing you need to do is ensure that your computer is using the correct time & date.
This is important because WSUS is extremely picky when ensuring that the machine trying to connect to the server bypasses every requirement. And one of the requirements that are very important is date, time, and timezone.
As it turns out, if the time & date is older than what it should be, you can expect to encounter this problem because the WSUS is refusing the connection.
Several affected users have confirmed that they managed to fix the issue after modifying the time, date, and timezone values to the correct values via the Date & Time utility:
- Open up a Run dialog box by pressing Windows key + R. Next, type ‘timedate.cpl’ inside the text box and press Enter to open up the Date and Time window.
Opening the Date & Time window - Once you’re inside the Date & Time window, access the Date and Time tab, then click on Change date and time.
Changing the Date and time values - When you’re prompted by the UAC (User Account Control), click Yes to grant admin access.
- Inside the Date and time settings, set the correct values for Time and Date using the calendar and the digital clock before clicking Ok to save the changes.
Modifying the Date and Time Note: Optionally, if your timezone is off, return to the Date and Time tab and click on Change Time Zone in order to modify the timezone to the correct UTC value.
- Click Apply to save the changes, then restart your computer and see if the issue is fixed once the next startup is complete.
If this particular issue is still not resolved, move down to the next potential fix below.
Method 2: Re-registering the MSXML3.dll (if applicable)
As it turns out if you’re encountering this problem while attempting to check for new updates on your Windows or Windows Server computer, chances are you might be seeing this error due to a missing Microsoft XML Core Service file dependency (msxml3.dll).
Several affected users that were previously dealing with the same problem have confirmed that the problem was finally resolved after they used an elevated Command Prompt to re-register the problematic Dynamic Link Library file.
If you haven’t tried this method yet and this scenario looks like it could be applicable, follow the instructions below:
- Press Windows key + R to open up a Run dialog box. Next, type ‘cmd’ inside the text box and press Ctrl + Shift + Enter to open up a Run dialog box. When you’re prompted by the UAC (User Account Control), click Yes to grant admin access.
Opening an elevated CMD prompt - Inside the elevated CMD prompt, type the following command and press Enter to re-register the problematic DLL file:
regsvr32 MSXML3.dl
- If the operation is finished successfully, you will get a success message telling you that the operation was completed.
- Restart your computer and see if the issue is resolved once the next system startup is complete.
In case the same problem is still occurring, move down to the next potential fix below.
Method 3: Adding ‘https://’ to Microsoft update service location (if applicable)
If you receive the 0x80072EE6 error when you attempt to download an update from Windows Server Update Services (WSUS) and you have previously configured WSUS via the Group Policy editor, chances are you’re seeing this error because the location of the Microsoft Update Service location is not correctly set up.
If this scenario is applicable, there’s a very big chance that this problem is occurring because the URL under the Group Policy setting ‘Specify intranet Microsoft update service location‘ is invalid.
In case you find yourself in this particular scenario, follow the instructions below to access the Group Policy editor and modify the value of Specify Intranet accordingly so that the Microsoft Update service location is correct.
Here’s what you need to do:
- Press Windows key + R to open up a Run dialog box. Next, type ‘gpedit.msc‘ inside the text box and press Enter to open up the Local Group Policy Editor. When you’re prompted by the UAC (User Account Control) prompts, click Yes to grant admin access.
Accessing the Gpedit Utility - Once you’re finally inside the Local Group Policy Editor, use the menu on the left to navigate to the following location:
Computer Configuration\Administrative Templates\Windows Components\Windows Update\
- After you’re inside the Windows Update policy folder, move over to the right-hand pane folder and double-click on Specify Intranet Microsoft Update Service.
Accessing the Specify intranet Microsoft update service location - Next, ensure that the policy is Enabled, then scroll down to the Options tab and ensure that the address specified inside the Set the alternate download server starts with ‘HTTP://‘ or ‘HTTPS://‘.
- If the download server starts directly with the address, make the necessary modifications before clicking Apply to save the changes.
Ensuring the the ‘Specify intranet Microsoft update service location’ has the correct location - Once the policy has been correctly modified, restart your computer and see if the issue is fixed once the next computer startup is completed.
If the same 0x80072EE6 error is still occurring, move down to the next potential fix below.
Method 4: Using a System Restore Snapshot
If none of the methods above have allowed you to fix the 0x80072EE6 error, you should start considering the fact that this issue started occurring after an important update, a major driver installation or an unexpected machine shutdown ended up messing up with your computer’s ability to connect to the WSUS servers.
Since there are a lot of different potential culprits that might be responsible for this issue, one ‘cure-all’ is to use a previously created System Restore snapshot to restore your computer back to a healthy state in which this issue was not occurring.
Keep in mind that the System will allow you to revert your computer back to a healthy state in which the current circumstances that are causing the 0x80072EE6 error were not occurring.
Important: By default, the System Restore utility is configured to regularly save new restore snapshots during important system events. Unless you modified the default behavior, you should have plenty of snapshots to choose from.
If you haven’t tried using the System restore until now, here’s a guide that will walk you through using a previously saved System Restore snapshot.
Note: Keep in mind that once you restore your computer state to an old one, every change you made since the restore snapshot was created will be lost.
If this problem still did not fix the 0x80072EE6 error in your case or you didn’t manage to find a suitable snapshot, move down to the next potential fix below.
Method 5: Reset every Windows Component
In case none of the methods presented above have been effective in your case, you should seriously take into consideration that your computer might be dealing with some type of system file corruption that cannot be resolved conventionally.
If you find yourself in a scenario like this, the only thing you can do is reset every relevant Windows component and eliminate every potentially corrupted element – When it comes to doing this, you have two ways forward:
- Clean Install – This should be your first pick if you’re looking for a quick fix that can be deployed without the need to use compatible Windows installation media. You can initiate a clean install procedure directly from the GUI menu of your Windows installation, but keep in mind that unless you back up your data in advance, you will lose any personal data that’s currently stored on the OS drive.
- Repair Install – If you have important information on the OS drive that you plan on keeping, a repair install should be the way to go for you, even if the procedure is a bit tedious. You’ll need to use compatible installation media, but you will be able to keep your personal files, installed applications, games, and even some user preferences rooted on the OS drive.
.NET Framework on Windows 11 is a super important component of the operating system that generally runs in the background without any issues. But sometimes it can throw up errors out of the blue including error 0x80072EE6. This is primarily a network-related issue that prevents Windows from installing or updating the .NET Framework and one that can usually be solved fairly easily so work your way through the steps until you solve the issue.
Takeaways:
- Learn how to fix Microsoft .NET Framework Error Code 0x80072EE6 in Windows 11
- What is causing Microsoft .NET Framework Error Code 0x80072EE6 in Windows?
Table of Contents
Windows includes .NET Framework by default, but it may not always be enabled. Manually enabling it can resolve functionality issues. Before you start though make sure that your Internet is actually working and that your VPN or proxies aren’t blocking anything.
-
Open Control Panel and go to Programs > Uninstall a program.
-
Click Turn Windows features on or off.
-
Check .NET Framework 3.5 (includes .NET 2.0 and 3.0).
-
Enable .NET Framework 4.8 Advanced Services, then click the plus icon next to it.
-
Ensure ASP.NET 4.8 is also enabled.
-
Click OK, then restart your computer.
Reset Windows Update Components
Corrupt Windows Update services can cause issues with downloading and installing .NET Framework updates. Resetting these services is a good place to start if you are having a lot of issues with this problem.
Repair .NET Framework
If the .NET Framework installation is corrupted, Microsoft provides a repair tool to diagnose and fix issues automatically.
-
Download the Microsoft .NET Framework Repair Tool from the official Microsoft website
-
Run NetFxRepairTool.exe.
-
Accept the license terms and click Next.
-
Allow Windows to diagnose and repair issues automatically.
-
Restart your computer.
Manually Install .NET Framework
If Windows Update fails to install .NET Framework updates, downloading and installing them manually can help.
-
Visit the Microsoft .NET Framework download page
-
If a specific version is required for an application, download that version.
-
Otherwise, install the latest available version.
-
Restart your system after installation.
Run System File Checker (SFC) and DISM
Corrupted system files can interfere with .NET Framework installation. Running SFC and DISM can repair these files.
-
Type cmd in Windows search.
-
Right-click Command Prompt and select Run as administrator.
-
In the Command Prompt, enter the following command and press Enter:
sfc /scannow
-
After SFC completes, run these DISM commands one by one
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
-
If the last command gives an error, try:
Dism /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
-
Reboot your computer.
Steps to Reset Windows Update Components
-
Open Command Prompt as administrator.
-
Run these commands one by one, pressing Enter after each:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 Catroot2.old
-
Restart the services using these commands:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
-
Reboot your computer.
Download Windows Speedup Tool to fix errors and make PC run faster
The Windows operating system releases updates from time to time. These updates help protect your system from the latest security issues. But sometimes, Windows Update shows some unexpected errors, like 80072EE6. Windows displays this error code when a user tries to download a Windows Update using Windows Server Update Services (WSUS). This article guides you on how to fix the Windows Server Update Services Error Code 80072EE6.
What is the cause of WSUS Error 80072EE6?
The possible cause of the WSUS error code 80072EE6 is an invalid URL or wrong update service location. There is a group policy setting in Windows 11/10, named “Specify Intranet Microsoft Update Service Location.” When the URL under this setting goes invalid, you may receive the error code 80072EE6.
To fix this error, you have to open Group Policy Editor. The Windows Group Policy Editor allows network administrators to modify or change some advanced settings in Windows.
Follow the below-listed steps to fix the WSUS error code 80072EE6.
1] Press the “Win+R” key and write “gpedit.msc”. After that, click on the OK button. This will open the Group Policy Editor on your system.
2] On the left panel of Local Group Policy Editor, you will see an option, “Administrative Templates.” Click on it. After that, you will find a “Windows Components” folder in the right panel.
3] Double-click on the “Windows Components” section. Now, scroll down in the right panel and find the “Windows Update” folder.
4] Double-click on the “Windows Update” folder. Now, find the option, “Specify intranet Microsoft update service location.”
5] Double-click on “Specify intranet Microsoft update service location” and it will launch a window shown in the following screenshot.
This setting allows you to update your PC automatically on a particular network. Using it, you can specify a server on your network, which will work as an internal update setting.
To use this setting, you have to set two server name values:
- The server from which the automatic update client will download the updates.
- The server to which the workstations will upload the statistics.
If the user has not disabled the automatic updates and the status is set to ”Not configured” or “Disabled,” (as shown in the above screenshot), the Windows update client will connect to the Windows update site automatically on the internet.
If you set the status to “Enabled,” the automatic update client will connect either to “Specified Intranet Microsoft Update Service” or to “Alternate Download Server.”
You have to verify that the URL includes https://.
Enabling this service means you do not have to go through a firewall to get Windows updates. This service will also give you an opportunity to test the updates before they are deployed.
The alternate download server customizes the Windows update agent to download files and data from alternative download servers rather than intranet update service.
You can see in the above screenshot, there is a checkbox, “Download files with no URL in the metadata if an alternate download server is set.” You can use this option when the internet update service does not provide you with download URLs in the update metadata for the files already on the alternate download server.
Some points that you should note are:
- The Windows update policy has no effect on your system if the “Configure Automatic Updates” policy is disabled.
- Windows will use the “Intranet Update Service” to download the updates by default if the “Alternate Download Server” is not set.
- You should use the option “Download files with no URL…” only if the “Alternate Download Server” is set.
To ensure users’ highest security level, Microsoft Corporation recommends HTTPS-based intranet servers to keep their systems secure. Users should also configure the system proxy (if required).
We hope that this article helped you fix the WSUS error code 80072EE6.
How do I troubleshoot Windows Server Update Services (WSUS) issues?
You may need to troubleshoot Windows Server Update Services (WSUS). The Windows Server Update Services (WSUS) helps to assist administrators with managing updates and hotfixes that the company releases for its products. The WSUS is a crucial part of a Windows server. As and when Microsoft launches the updates on its website, WSUS downloads it and distributes it across the network. You may need to run the WSUS Server Cleanup Wizard.
Nishant is an Engineering graduate. He has worked as an automation engineer in the automation industry, where his work included PLC and SCADA programming. Helping his friends and relatives fix their PC problems is his favorite pastime.
If you receive a 80072EE6 error code when you download an update from Windows Server Update Services in Windows 7 or Windows Server 2008 R2, your update service location can be wrong. You have to control and change with true.
Error
80072EE6 error code when you download an update from Windows Server Update Services.
Solution
- Click on Start and then type gpedit.msc
- Go to Computer Configuration\Administrative Templates\Windows Components\Windows Update\
- From the right-side pane double-click on Specify intranet Microsoft update service location to open it
- Verify that the URL includes http:// or https://. For Example, http://corp.contoso.com or https://corp.contoso.com
Source : support.microsoft.com
В очередной раз настраивал WSUS в локальной сети организации. Этапы настройки описывать не буду. После установки роли сервера обновлений, внесения необходимых изменений в групповую политику и в DNS, на клиентах появилась ошибка 80072EE6. Честно говоря, меня это немного смутило, ведь сервер обновлений поднимаю уже не первый раз и все делаю по «накатанной». Справка по ошибке ничего хорошего не сказала.
|
Рисунок 1. Панель управления\Система и безопасность\Центр обновления Windows |
Решение оказалось очень простым. В групповой политике «Конфигурация компьютера\Административные шаблоны\Компоненты Windows\Центр обновления Windows\Указать размещение службы обновлений Майкрософт в интрасети» я ошибочно указал адрес сервера в формате «wsus.domain.ru». Когда начал разбираться, увидел пример, написанный прямо в редакторе групповой политики.
| Рисунок 2. Размещение службы обновлений Майкрософт в интрасети |
Честно говоря, когда увидел, удивился. Но все же заменил «wsus.damain.ru» на «http://wsus.damain.ru». Вот что получилось:
|
Рисунок 3. Исправленное значение |
Далее нужно применить изменения на компьютерах-клиентах. Для этого дожидаемся применения изменений в групповой политике, или выполняем на клиенте команду:
gpupdate /force
После описанных действий все сразу встало на свои места и клиенты начали получать обновления.
| Рисунок 4. Центр обновления работает исправно |
Чтоб в очередной раз не наступить на эти грабли, решил записать. Может быть, пригодится кому-нибудь еще.