How to Fix Windows Update Error 0x80072ee7

By ErrorFix · Updated October 25, 2026 · 7 min read

What error 0x80072ee7 means

Error 0x80072ee7 is Windows telling you that a server name could not be resolved. Every time your PC contacts Microsoft's update servers, it first has to translate a server name into a network address, the same way you look up a phone number before making a call. With this error, that lookup fails: your PC asks for the address and gets no usable answer, so the connection never starts and no update files ever download. Settings then reports that there were problems installing updates and that it will try again later, but retrying alone rarely helps, because the same failed lookup happens every time.

The confusing part is that the rest of your internet can work perfectly. You can browse websites, stream video, and download files while Windows Update keeps failing with this code. That happens because the lookup failure is specific to the path Windows Update uses. System services like Windows Update can use a system-wide proxy and a DNS configuration that your browser does not share, and a proxy left behind by uninstalled software or a DNS cache full of stale entries can break that one path while everything else works. The fixes below therefore focus on that path: the proxy, the VPN, the DNS cache, and the update components themselves.

Common causes

• A proxy or VPN that cannot reach Microsoft's servers: a manual proxy configured in Settings that no longer answers, a proxy left behind by old software, or a VPN tunnel that blocks or misroutes Microsoft traffic will leave Windows Update with nowhere to connect. This is the most common trigger for 0x80072ee7.
• Stale or incorrect DNS answers: if your DNS cache or your DNS resolver returns an outdated, wrong, or unreachable address for Microsoft's servers, every update attempt fails at the lookup stage. This often shows up after changing internet providers, switching DNS services, or joining a new network.
• Windows Update services stuck in a bad state: when the Windows Update, BITS, or Cryptographic services are stopped or wedged, downloads cannot start properly, and the attempt collapses before a connection is ever made.
• A corrupted update cache: damaged files in the SoftwareDistribution folder or the catroot2 security catalog can stall the update engine, and a stalled engine eventually reports the failure as a connection problem rather than a file problem.
• Firewall, security software, or a modified hosts file: third-party security tools can intercept update traffic, and entries in the hosts file can redirect Microsoft's server names to addresses that do not answer. Either one breaks the lookup or the connection that follows it.

How to fix error 0x80072ee7 — step by step

Work through these fixes in order. Steps 2 and 4 together resolve most cases.

1. Confirm your connection and fix the date and time Open your browser and load two or three ordinary websites to confirm the internet connection itself works, then open Settings, go to Time and language, then Date and time, turn on Set time automatically, and click Sync now. A clock that is months or years out breaks the secure handshake with Microsoft's servers, so this quick check rules out a surprisingly common cause.
2. Disconnect the VPN and turn off any proxy Open Settings, go to Network and internet, then Proxy, and make sure Use a proxy server is turned off and no setup script is listed. Then disconnect your VPN entirely and try the update again. A proxy that no longer answers, or a VPN tunnel that cannot reach Microsoft's servers, is the single most common reason Windows reports this error.
3. Run the Windows Update troubleshooter Open Settings, go to System, then Troubleshoot, then Other troubleshooters. Click Run next to Windows Update and follow whatever it suggests, letting it repair the update components on its own. When it finishes, restart your PC and check for updates again.
4. Flush DNS and reset the WinHTTP proxy Right-click Start and choose Terminal (Admin). Type ipconfig /flushdns and press Enter to clear old DNS answers, then type netsh winhttp reset proxy and press Enter to remove any hidden system-wide proxy left behind by uninstalled software. Restart your PC and check for updates again.
5. Reset the Windows Update components Right-click Start and choose Terminal (Admin). Stop the update services one at a time with net stop wuauserv, net stop cryptSvc, net stop bits, and net stop msiserver. Rename the SoftwareDistribution folder to SoftwareDistribution.old and the catroot2 folder to Catroot2.old. Restart the services with net start wuauserv, net start cryptSvc, net start bits, and net start msiserver, then check for updates again.
6. Switch to a reliable DNS server Open Settings, go to Network and internet, open the properties of your Wi-Fi or Ethernet connection, and change the DNS setting from Automatic to Manual. Enter 8.8.8.8 as the preferred DNS server and 8.8.4.4 as the alternate, save the change, disconnect and reconnect to the network, and try the update again. A DNS resolver that returns bad answers for Microsoft's servers is a frequent hidden cause of this error.
7. Repair system files, then install the update manually if needed Open Terminal as administrator and run sfc /scannow to repair protected system files, then run DISM /Online /Cleanup-Image /RestoreHealth to repair the component store. Restart your PC and check for updates once more. If automatic downloads still fail, note the KB number of the failed update in Settings, then Windows Update, then Update history, search for that KB number in the Microsoft Update Catalog, and install it directly.

Did this fix it? Quick checklist

• Windows Update checks for updates without 0x80072ee7
• No proxy configured in Settings and the VPN disconnected
• DNS cache flushed and DNS set to a reliable resolver
• No failed or stuck downloads remain in Update history

If the error survives all seven steps, test a different network: tether through your phone's hotspot and retry the update. If the update works there, the block sits on your router or ISP, so restart the router and try again with your ISP's default DNS for the test. On a work or school network, ask your IT admin whether Windows Update traffic is allowed through the corporate firewall or proxy, since some networks only permit it on managed devices. Also worth a look is the hosts file: open it with Notepad as administrator and remove any lines mentioning Microsoft update or activation servers that you did not add yourself, since a stray entry there can redirect those names to dead addresses.