(SOLVED) Event ID 1014 on Windows 11 causes WiFi to disconnect for a few seconds then reconnect

Dear dom,

To address this issue, please consider the following:

1. Verify DNS Server Configuration Run ipconfig /all to confirm the correct DNS server IPs are configured. If only one DNS server is listed, consider adding a secondary for redundancy.
2. Check Network Connectivity Ensure UDP port 53 is open between the client and DNS server. Use ping and nslookup to test connectivity and resolution manually.
3. Review DNS Client Behavior Windows clients retry DNS queries up to five times with increasing delays (1s, 1s, 2s, 4s, 2s) before timing out. If the DNS server is slow or intermittently unreachable, this may result in timeouts.
4. Inspect DNS Forwarders and Root Hints On your DNS server, verify that forwarders or root hints are properly configured to resolve external domains. Use PowerShell
5. Check for Conditional Forwarders If specific domains consistently fail, consider configuring conditional forwarders for those domains.
6. Monitor DNS Server Health Ensure the DNS service is running and responsive. Review event logs for any service interruptions or errors.

I hope this helps,

Domic Vo

For people who have the same issue:

I believe I managed to solve the issue (or at least significantly reduce it) by disabling update services. and adding an Inbound Rule and Outbound Rule to my firewall. Here's how to do that.

To disable update services for apps:

1: Press Win + R, then type msconfig in the prompt.

2: Navigate to Services.

3: Check Hide all Microsoft services.

4: Look for the following programs:

• Anything that says "Update Service" or "Updater", e.g., ASUS Update Service
• Anything that says "Telemetry Service" (not sure what this means)
• "Client Web Helper"
• "Network Service" with vendor names

Disable 2-3 at a time by clearing the tickbox next to it and then hit Apply and OK.

5: Reboot and monitor Event Viewer. If the issue persists, try disabling more if applicable.

To add an Inbound Rule to your firewall (MAKE SURE YOU REPEAT THIS WITH OUTBOUND RULES TOO!):

1: Go to Windows Security.

2: On the left pane, click Firewall & network protection.

3: Click Advanced settings at the bottom.

4: On the left pane, right click Inbound Rules.

5: Click New Rule.

6: On the new prompt, click Custom rule and Next.

7: All Programs.

8: Protocol type: UDP, specify ports 53.

9: Any IP address.

10: Allow the connection.

11: Check Domain, Private, Public.

12: Title and description are at your discretion; make it something memorable, e.g., Allow DNS.

Do the same thing for Outbound Rules.

If this doesn't work, try changing wireless mode.

1: Search up Device Manager.

2: Select your network adapter under Network Adapters.

3: Go to the Advanced tab and search for "Wireless Mode".

4: Experiment with different options and restart to see if it works. In my case, switching it to A worked.

One of these steps managed to work for me but I'm not entirely sure which one.

Hello. Could you let me know your current Wi-Fi adapter model and the driver version listed in Device Manager?

Event ID 1014 points to a DNS resolution timeout, which doesn’t always mean there’s a Wi-Fi dropout. Still, if the DNS lookup fails because your adapter is losing its connection, the root cause is usually deeper, such as power management settings, a faulty driver, router behavior, or issues with DHCP lease renewals.

You mentioned you’ve already tried some troubleshooting steps. Could you share what you’ve done so far? That way, I won’t suggest anything you’ve already tried.

If you don’t mind, we can review a few foundational steps, just to be thorough. First, I recommend setting your DNS servers manually:

1. Go to Control Panel > Network and Sharing Center > Change adapter settings.
2. Right-click your Wi-Fi adapter, select Properties, then select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
3. Enter these DNS servers:
   • Preferred: 1.1.1.1
   • Alternate: 8.8.8.8
4. Apply the changes and restart your computer.

This is the "going to the basics" steps for this type of error. Let me know what you find.