INET_E_RESOURCE_NOT_FOUND: How to fix the Microsoft Edge error

Together with its operating system Windows 10, the software giant Microsoft released its own web browser Edge in July 2015. Like its pre­de­ces­sor, Internet Explorer, this browser is firmly in­te­grat­ed into the operating system by default, which is why it can display PDF documents without any ad­di­tion­al tools, for example, or use the Adobe Flash plugin im­ple­ment­ed in Windows 10 if cor­re­spond­ing content is to be displayed. Fur­ther­more, updates for the browser are au­to­mat­i­cal­ly installed via the Windows Update function – which is not always an advantage, however, as the “INET_E_RESOURCE_NOT_FOUND” error shows.

For years, Microsoft has au­to­mat­i­cal­ly provided its users with the latest system and software updates via the in­te­grat­ed update function. This ensures that both new features and important bug fixes reach the Windows community in a timely manner. However, the update process is not always as smooth as Microsoft would like it to be – problems during and after in­stalling new Windows updates are not uncommon. Since the release of the Windows Creators Update (V1703) in April 2017, for example, some users may ex­pe­ri­ence the “INET_E_RESOURCE_NOT_FOUND” error when using the Microsoft Edge browser, or when down­load­ing or in­stalling apps from the Microsoft Store.

The error message is usually ac­com­pa­nied by the in­for­ma­tion that the page accessed could not be reached. The Microsoft Edge error code “INET_E_RESOURCE_NOT_FOUND” usually specifies the alleged source of the error directly. For example, the detailed error report may contain, among other things, the following sentences that provide in­for­ma­tion about the problem:

"The con­nec­tion to the DNS server timed out."

"There was a temporary DNS error."

"The DNS server might be having problems."

"The DNS name does not exist."

"This website could not be found."

The various messages show that it is not just a simple con­nec­tion error resulting from an in­ter­rupt­ed Internet con­nec­tion. Rather, the in­cor­rect­ly func­tion­ing name res­o­lu­tion via the reg­is­tered or au­to­mat­i­cal­ly assigned DNS server is more likely the problem.

The above overview of possible error messages as­so­ci­at­ed with the Microsoft Edge “INET_E_RESOURCE_NOT_FOUND” error code il­lus­trates the com­plex­i­ty of the problem: While error analysis iden­ti­fies name res­o­lu­tion as a key problem, it is difficult to remotely determine why, for example, a timeout or temporary error could occur during this process. In some cases, the error dis­ap­peared just as suddenly as it first appeared – so it is often a good idea to just wait and see, and reload the page at a later point. If the problem persists for a longer time, the solutions presented below offer the greatest chances of success to rectify the “INET_E_RESOURCE_NOT_FOUND” error.

Microsoft Edge supports the TCP Fast Open (TFO) extension as part of Creator Update 1703, which ac­cel­er­ates the exchange of data over TCP (by combining the first two steps of the three-way handshake). However, since the per­for­mance feature can also be re­spon­si­ble for the “INET_E_RESOURCE_NOT_FOUND” error, it makes sense to disable it – at least on a trial basis – as soon as you receive the error message. To do this, access the hidden settings of the Microsoft browser by entering the following address in the browser line:

Confirm the new DNS server(s) by clicking the OK button.

DNS problems such as the “INET_E_RESOURCE_NOT_FOUND” message are not nec­es­sar­i­ly due to a mal­func­tion of the DNS server used, since in many cases the name server is not contacted at all. This is because Windows au­to­mat­i­cal­ly stores the resolved addresses of visited websites in the system's DNS cache in order to deliver the cor­re­spond­ing pages faster when they are accessed again. In principle, this cache, which also relieves the DNS servers, has a positive effect on web per­for­mance – outdated entries that do not match the current version of the pages, however, can lead to com­pli­ca­tions such as the Edge error.

The solution is then to clear the DNS cache to force the DNS server to resolve the name again. A DNS flush like this can be done in a few seconds via the command line. To do this, open the command prompt by pressing the Windows home button, type “cmd” in the search window, and then press the Enter key. Then enter the following command:

Enter the following command into the open command line to reset the TCP/IP stack to factory settings:

Af­ter­wards, it is rec­om­mend­ed to also reset the catalog of the Windows pro­gram­ming interface, Winsock (Windows Sockets). Windows au­to­mat­i­cal­ly creates entries for suc­cess­ful­ly es­tab­lished network con­nec­tions, which may also lead to network problems. The required command line command is:

If the desired success is not achieved even after resetting the Microsoft browser, you should contact Microsoft Support directly. Al­ter­na­tive­ly, you can contact your internet service provider to check if there may be a basic problem with internet access that is re­spon­si­ble for the “INET_E_RESOURCE_NOT_FOUND” message.