How to fix .NET Framework error code 0x80072EE6 in Windows?

Error 0x80072EE6 means Windows tried to download the .NET Framework 3.5 files from an update server whose address it cannot use. Most often the PC has an old or badly written WSUS address in its update policy. Check that policy first (Fix 1), because cache resets and SFC do not change it.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What .NET Framework error 0x80072EE6 means

The code has two parts. 0x8007 marks a Windows system error, and 2EE6 is the number 12006 in hexadecimal. Numbers from 12000 up belong to WinINet, the library Windows uses to reach addresses on the internet. Microsoft's own article on 80072EE6 gives the practical meaning: the update server address on the PC is not a valid web address.

You see it most often with .NET Framework 3.5. Microsoft explains that on Windows 10 and Windows 11 this version is a Feature on Demand: Windows keeps only its metadata, and when you turn it on, it contacts Windows Update to download the files. If the PC is set to use an update server (WSUS) with a broken address, that request fails at once.

Why Windows cannot download .NET Framework 3.5

The error is about where Windows looks for the files, not about the files themselves. So the cause is almost always a setting that points Windows at the wrong place, and a few common repairs are pointless until that setting changes.

.NET Framework 3.5 on Windows 11 26H1 and later

Microsoft changed how .NET Framework 3.5 is delivered. Starting with Windows 11 26H1 (build 28000), it is only available as a standalone installer and can no longer be installed as a Windows component. The optional components that depend on it, such as ASP.NET 3.5 and WCF HTTP Activation, were removed too.

• Press Win + R, type winver and select OK. The window shows your version and OS Build.
• Build 28000 or higher: use Microsoft's standalone installer in Fix 5. The Windows Features route does not apply.
• A lower build, for example Windows 11 25H2 or Windows 10 22H2: .NET 3.5 is still a Windows feature, and Fix 1 to 4 apply.

How to fix .NET Framework error 0x80072EE6

Fix 1 shows in two minutes whether an update server address is set. Fix 2 corrects it on your own PC, Fix 3 lets a managed PC fetch the files from Windows Update, and Fix 4 installs from media with no server at all. Fixes 6 to 8 are the general repairs.

Fix 1. Check whether an update server (WSUS) address is set

2 minutesNo riskAlways first. It only reads settings and takes two minutes.

Microsoft names an invalid address in Specify intranet Microsoft update service location as the cause of 80072EE6. Seeing that address tells you at once whether the policy is the problem.

1. Right-click Start and open Terminal (Admin) on Windows 11, or Windows PowerShell (Admin) on Windows 10. Select Yes.
2. Run the command below. It lists the update policy values on the PC and changes nothing.
3. ERROR: The system was unable to find the specified registry key or value means no update policy is set: go to Fix 4.
4. A line WUServer with a value means a WSUS address is set. Read it: an address without http:// or https:// at the start is the invalid kind Microsoft describes.
5. On Windows 11 Pro or Windows 10 Pro you can see the same in the policy editor: press Win + R, type gpedit.msc and open Computer Configuration > Administrative Templates > Windows Components > Windows Update.
6. Look for Specify intranet Microsoft update service location. If you do not see it, open the subfolders under Windows Update. Enabled in the State column means an address is set.

reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate"

Fix 2. Correct or remove the WSUS address, then turn on .NET Framework 3.5

5 to 10 minutesRead the warningFix 1 found an address and the PC is yours, for example a former company laptop or a PC where a tool changed the update settings.

Windows follows the policy and asks only that server for the .NET 3.5 files. With the policy back to Not Configured, Windows downloads them from Windows Update. If the server is real, adding http:// or https:// is the fix Microsoft gives.

1. Pro editions: in the policy editor from Fix 1, double-click Specify intranet Microsoft update service location.
2. If the server still exists, add http:// or https:// in front of both addresses, for example http://corp.contoso.com, and select OK.
3. If the server is gone or you do not know it, select Not Configured and OK.
4. Home edition, or no policy editor: run the commands below in the admin terminal. They remove the two address values and tell Windows not to use a WSUS server.
5. Run gpupdate /force and restart the PC.
6. Select Start, search for Windows Features and open it. Select .NET Framework 3.5 (includes .NET 2.0 and 3.0), then OK, and choose Let Windows Update download the files for you if Windows asks.

reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v WUServer /f
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v WUStatusServer /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v UseWUServer /t REG_DWORD /d 0 /f

Fix 3. Let a managed PC download optional features from Windows Update

5 minutes, by an administratorLow riskA work or school PC that must keep its WSUS server, or the setting is managed by your organization.

Microsoft's fix for .NET 3.5 on WSUS-managed PCs is a second policy that sends only optional features and repairs to Windows Update, while normal updates still come from WSUS.

1. Open the policy editor: Open the Local Group Policy Editor
2. Go to Computer Configuration > Administrative Templates > System.
3. Open Specify settings for optional component installation and component repair and select Enabled.
4. Select the box Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS). Its wording can differ slightly between Windows versions.
5. Or fill Alternate source file path with a shared folder that holds \sources\sxs from the installation media, for example \\server_name\share\Win8sxs.
6. Select OK, run gpupdate /force in an admin terminal, and turn on .NET Framework 3.5 again.

Fix 4. Install .NET Framework 3.5 from Windows installation media with DISM

20 minutesLow riskFix 1 to 3 did not help, the PC has no internet, or you want a route that needs no update server at all.

With /Source and /LimitAccess, DISM takes the .NET 3.5 files from the sources\sxs folder of the media and does not contact any server, so a broken WSUS address cannot stop it.

1. Make a Windows ISO of the same version as your PC with Microsoft's Media Creation Tool, or use the installation USB you already have.
2. Right-click the ISO file and select Mount. Note the drive letter it gets in File Explorer, for example D:.
3. Open Terminal (Admin) or Windows PowerShell (Admin).
4. Run the command below. Replace D: with your drive letter.
5. Wait for The operation completed successfully and restart if asked.

Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess

Fix 5. Use the standalone .NET Framework 3.5 installer on Windows 11 build 28000 or later

10 minutesNo riskwinver shows OS Build 28000 or higher, for example Windows 11 26H1.

From build 28000, Microsoft ships .NET Framework 3.5 only as a standalone installer. The Windows Features and DISM route no longer installs it, so the download path behind 0x80072EE6 is not used.

1. Open Microsoft's page Install .NET Framework 3.5 on Windows 10 and Windows Server on learn.microsoft.com and find Developers and .NET Framework 3.5.
2. Select Download .NET Framework 3.5 for Windows 11 26H1. Add the language pack from the next link if you use Windows in another language.
3. Run the downloaded installer and follow its steps.
4. Restart the PC and start the program that asked for .NET 3.5.

Fix 6. Check the connection, proxy and VPN

5 to 10 minutesLow riskFix 1 found no update server address, and downloads from Microsoft fail.

Without a WSUS policy, Windows downloads the .NET 3.5 files from Windows Update. Microsoft says network, proxy or firewall settings can stop that download, so a leftover proxy or a VPN can make the feature fail.

1. Open Settings > Network & internet > Proxy and make sure Use a proxy server under Manual proxy setup is Off. On Windows 10 it is Settings > Network & Internet > Proxy.
2. In the admin terminal, run netsh winhttp show proxy. Direct access (no proxy server). is the normal answer.
3. Disconnect a VPN for the test and connect it again afterwards.
4. Try .NET Framework 3.5 in Windows Features again.

If websites also fail, check the connection itself step by step: How to check your internet connection in Windows

Fix 7. Reset the Windows Update components

15 minutesLow riskNo WSUS address is set, the connection works, and Windows Update itself also fails.

A damaged update database can keep a failed request in a loop. Renaming SoftwareDistribution and catroot2 makes Windows start over. It does not fix a broken WSUS address, so do it only after Fix 1.

1. Open Command Prompt as administrator. Type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Stop the update services. Type the commands below and press Enter after each one. If Windows says that other services depend on Cryptographic Services, it stops them too. A message that a service is not started is fine.

   net stop wuauserv
   net stop bits
   net stop cryptsvc

3. Delete the download queue files. This clears the list of downloads that the Background Intelligent Transfer Service keeps. If Windows says it cannot find the files, continue.

   del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"

4. Rename the update cache folders. Renaming keeps a copy in case you need it; Windows creates new, empty folders when the services start again. If you get Access is denied, a service is still running: repeat the previous step.

   ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
   ren %systemroot%\System32\catroot2 catroot2.old

5. Start the services again. Type the commands below and press Enter after each one. The requested service has already been started is fine: Windows started it on its own.

   net start cryptsvc
   net start bits
   net start wuauserv

6. Restart and check for updates. Restart the PC. Then select Start > Settings > Windows Update > Check for updates. The first check can take longer than usual because everything is downloaded again.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Reset Windows Update components

Fix 8. Repair system files with SFC and DISM

20 to 30 minutesLow riskNothing above helped, or other Windows features also fail to install.

Damaged component store files can stop a feature from installing. DISM RestoreHealth downloads its repair files from the same source as .NET 3.5, so a broken WSUS address stops it too; fix that first.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

If error 0x80072EE6 is still there

Microsoft names the DISM log as the place to look: C:\Windows\Logs\DISM\dism.log. Open it with Notepad, search for 0x80072ee6 from the bottom up and read the lines just above the hit. They show which source Windows tried.

For support, send the code 0x80072EE6, your Windows version and build from winver, the output of the reg query command in Fix 1 and the last lines of dism.log. This error is not a hardware fault and not a licence problem: it is always about where Windows looks for the files.

How to keep error 0x80072EE6 from coming back

Frequently asked questions

What does error code 0x80072EE6 mean?

It means Windows could not use the address of the server it was told to download from. The last digits, 2EE6, are WinINet error 12006 from the Windows internet library. Microsoft's article on 80072EE6 ties it to the policy Specify intranet Microsoft update service location: when that WSUS address is invalid, for example without http://, updates and features such as .NET Framework 3.5 fail. Check the policy with Fix 1.

How do I fix 0x80072EE6 when installing .NET Framework 3.5?

First check whether an update server address is set (Fix 1). On your own PC, remove it or add http:// to it, then turn on .NET Framework 3.5 again in Windows Features (Fix 2). On a work PC, IT can let optional features come from Windows Update (Fix 3). If none of that is possible, install .NET 3.5 from Windows installation media with DISM (Fix 4), which needs no server.

Is 80072EE6 the same as 0x80072EE6?

Yes. Windows Update often shows the code without the 0x prefix, as 80072EE6, while Windows Features and DISM show 0x80072EE6. Small letters, as in 0x80072ee6, make no difference. Error 0x80072EE6 and error code 0x80072EE6 in forum posts are the same error too, so everything on this page applies to every spelling.

Does 0x80072EE6 happen on Windows 10?

Yes. The code and its cause are the same on Windows 10 and Windows 11, because both treat .NET Framework 3.5 as a Feature on Demand and download its files when you turn it on. The menu names differ only slightly. Windows 10 reached the end of support on 14 October 2025, but Fix 1, 2 and 4 still work on Windows 10 22H2.

Can 0x80072EE6 appear in Windows Update without .NET?

Yes. Microsoft's article describes 80072EE6 as a Windows Update error on PCs that use WSUS through the policy Specify intranet Microsoft update service location. The same broken address stops normal updates and optional features alike. The fix is the same as for .NET 3.5: correct the address or set the policy to Not Configured (Fix 2), or ask IT on a work PC.

What is error 0x80072EE5?

It is a neighbouring code from the same Windows internet library, number 12005. We could not confirm its exact Microsoft description in the sources we read today. In practice it shows up in the same places, mostly Windows Update. Check for an update server address with Fix 1 and the connection and proxy with Fix 6, because both errors come from Windows trying to reach an address.

Why does my PC have a WSUS address if I am not in a company?

Usually the PC was once managed by a company or school, and the policy stayed after it was sold or reset without a clean install. A tool that changes update settings can also write such values. Microsoft's article gives examples of invalid addresses, such as corp.contoso.com or a bare IP address. If the server means nothing to you, set the policy to Not Configured (Fix 2).

Can I download a .NET Framework 3.5 offline installer instead?

Not for Windows 10 or Windows 11 before build 28000. Microsoft says the classic .NET Framework 3.5 SP1 offline installer is for versions before Windows 10, and that from Windows 10 on, the supported offline route is the installation media. That is Fix 4 with DISM. On Windows 11 build 28000 and later, Microsoft offers a new standalone installer instead (Fix 5).

Will the .NET Framework Repair Tool fix 0x80072EE6?

Unlikely. The repair tool fixes damaged .NET Framework installations, but 0x80072EE6 happens before anything is installed: Windows cannot reach the source of the files. Fix the update server address or install from media first. If a program then still fails on .NET 4.x, the repair tool is described in How to repair Microsoft Visual C++ Redistributable and .NET Framework.