Event ID 1014: What does it mean & how to fix this DNS issue

Disabling an important workflow feature can solve this problem

Reading time icon 5 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Key notes

  • Event ID 1014 occurs when the DNS on your computer fails to connect to a server.
  • This can happen because your CPU's Offload feature is enabled, out-of-date drivers or some router problem.
  • This guide will teach you how to solve this error by opening the Command Prompt and making adjustments, among other fixes.

Event ID 1014 is an error message that appears when a configured DNS server (Domain Name System) fails to respond to your Windows computer. More specifically, the network connection timed out.

When this occurs, the computer creates an event log detailing everything, but you’ll need a log viewer to read it. Reading the log should give you an idea of what to do, plus you can read this guide for extra help.

What causes Event ID 1014 to appear on my Windows computer?

According to an old Microsoft TechNet post from 2011, there are four main reasons why this error appears. From those four, we’ll point out the more likely culprits and add some of our own.

  • The TCP/IP Offload has been enabled on a network adapter. This is a technology that offsets CPU processing to the adapter and frees up the CPU so it can do another task, but can cause problems.
  • Your router and PC are on different Wi-Fi channels. Admittedly, this problem is pretty rare since modern routers will change automatically but older models might not.
  • Your computer’s drivers are out of date and it’s important that you update them as soon as possible.
  • There’s some kind of problem with your router and we recommend performing a power cycle. We have a guide on a similar 1014 error with instructions on how to safely power cycle.
  • Your internet service provider (ISP) is dealing with an outage. If this is the case, there’s nothing you can do but wait until your ISP fixes the problem.

How do I fix the 1014 error on my Windows computer?

Before going into the more complex solutions, it’s important to list out some of the simpler ones that you can try out.

  • As we mentioned, install the latest network drivers on your computer.
  • Change the power plan on your Windows machine. It is possible the power plan may act finicky and change at seemingly random times. You may have broken system files if this happens to you.
  • If you have a Windows 10 computer, we recommend performing a clean boot. It does require setting the computer up for it in a particular way, however.
  • Double-check that there aren’t any loose cables anywhere in your network. Sometimes problems can be solved by making sure things are properly plugged in.

1. Disable TCP Offload

  1. On your Windows computer, search for the Command Prompt and select Run as administrator.
  2. In the window that appears, select Yes.
  3. Type the following command: netsh int ip set global taskoffload=disabled. And hit the Enter key when you’re finished.
  4. Command Prompt will simply say Ok to indicate Offload has been disabled.

2. Reset the Hosts file to default

  1. On your Windows computer, open Notepad and enter the text you see in the image into the app.
  2. Select File, then Save As.
  3. Go to Desktop, name the file as “hosts” (make sure the quotes are included) and click Save.
  4. Close Notepad and open File Explorer.
  5. Go to C:\Windows\System32\drivers\etc.
  6. Right-click the hosts file and rename it as hosts.old. The User Account Control may appear asking if you want to make changes. Click Yes.
  7. Drag and drop the new hosts file from the desktop to the folder. Click Continue if you need to provide administrator permission.
  8. Close File Explorer and you’re done.
  1. In the Search bar, bring up Windows Administrative Tools. Select the entry that appears.
  2. Open the Registry Editor in the Administrative Tools folder.
  3. In the top bar, type in HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search.
  4. Right-click AllowCortana and select Modify. Set the value data to 0 and click OK.
  5. Do the same thing to DisableWebSearch.

If you get a log viewer and read a 1014 log, you may see “t-ring-fallback.msedge.net”. It looks like this relates to Microsoft Edge, but it doesn’t. It more closely relates to Search and Cortana.

After disabling those two, check if the 1014 error is gone.

4. Fix Wi-Fi connection issues

  1. On Windows 10, open the Settings app, click Network & Internet, then Status on the left-hand side.
  2. Select Network troubleshooter.
  3. Select which network adapter you want to diagnose. Click Next.
  4. Follow the on-screen instructions to solve the problem.
  5. On Windows 11, open the Settings app, select System on the left-hand side, and click Troubleshoot.
  6. Select Other troubleshooters. Click Run next to Internet Connections as well as any other problematic areas. Follow the direction on the screen to fix the 1014 problem.

Are there other Event ID errors that I should know about?

There are two particular Event ID errors that are particularly notorious. The first is Event ID 7000 which occurs a service on your computer doesn’t have the right credentials to run.

This is the result of an error with the Service Control Manager and has different variations of it like 7023. Solutions include restarting the offending service and using the Group Policy Editor to make adjustments.

The other error is Event ID 1000 which causes software to suddenly close. Culprits for this error involve malware and old versions of Windows OS.

To fix Error 1000, we recommend updating your drivers, reinstalling the problematic app, or performing a clean boot.

Feel free to comment below if you have any questions about all of these Event ID errors. Also, leave comments about what reviews you’d like to see or information on other Windows software.

More about the topics: DNS, event log viewers, windows 10 fix