Windows System Errors
Name Not Resolved
0x80072EE7Reviewed for reference consistency: August 11, 2026
DNS could not translate the target hostname into an address
What 0x80072EE7 Means
The 0x80072EE7 error on the Windows System Errors indicates name not resolved — dns could not translate the target hostname into an address. This typically occurs due to the dns server cannot answer for the requested name or returns a negative response.
Before any HTTP exchange, a hostname has to become an address; when that translation fails, WinINet reports 0x80072EE7, error 12007, ERROR_INTERNET_NAME_NOT_RESOLVED — 'The server name could not be resolved'. The failure happens ahead of connecting entirely, so no server ever sees the request and no TCP probe to the destination can even begin.
How to fix 0x80072EE7
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Replay the lookup for the exact hostname
A direct DNS query outside the failing application shows the translation result the application received.
Resolve-DnsName download.windowsupdate.comReview the active resolver configuration
Adapter DNS settings and suffixes determine which server answers; the listing changes nothing while exposing the path.
ipconfig /all
Technical Background
Resolution is the first dependency in every name-based call, and its failure is total: nothing downstream — TCP, TLS, HTTP — is ever attempted. That makes the code one of the easiest to localize. The same request from the same machine either resolves or does not, and resolver tooling can replay the translation step directly, sidestepping the application layer where the error surfaced.
The Windows Update stack has its own parallel code for the same underlying event — 0x8024402C, WU_E_PT_WINHTTP_NAME_NOT_RESOLVED, documented as the proxy-or-target name failing to resolve. Seeing either one means the question is about DNS configuration: which resolver the client uses, whether that resolver holds a record, and whether policy or segmentation stands between them.
Common Causes
- The DNS server cannot answer for the requested name or returns a negative response
- A hosts-file or proxy auto-configuration points the name at a resolver path that fails
- VPN or network segmentation leaves the client without a resolver for internal names
Typical Scenarios
- An update scan or web request fails when the DNS resolver cannot answer for the endpoint
- A proxy auto-configuration script routes the name to a resolver that has no record for it
- VPN clients lose split-DNS coverage for internal endpoints and every request fails at resolution
What to Know
Replaying the lookup outside the failing application — a direct query for the exact hostname — confirms whether the resolver path or the application's configuration is at fault.
Frequently Asked Questions
Common questions about Windows 0x80072EE7 error
Name resolution, before any connection is attempted. WinInet.h lists 12007 as ERROR_INTERNET_NAME_NOT_RESOLVED, 'The server name could not be resolved'.
Both report unresolved names in update traffic; 0x8024402C is the update agent's WinHTTP-flavored version of the same event, documented as the proxy or target server name failing to resolve.
Yes. When a proxy or auto-configuration script handles the name, resolution follows the proxy's path, and a misdirected or stale entry fails there before the real destination is ever consulted.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
Git paused the merge because it cannot automatically resolve overlapping changes.
Git aborted the merge to protect uncommitted changes in your working directory.
Git prevented a branch switch because it would overwrite unsaved changes in your working directory.
Git aborted the merge because it would overwrite untracked files in your working directory.