Loss of internet access about 3-4 minutes after powerup.

Dwight Curtis 20 Reputation points
2026-11-01T17:58:03.25+00:00

Why do I lose network access on my PC about 3-4 minutes after startup? This happens on both wired Ethernet and WIFI.

This issue appeared on about Oct 29 or 30 2026.

Windows update history is included below:

Update history.jpg

The system is currently running windows Ver. 25H2.

System info.jpg

I have tried updating the WIFI driver and the Ethernet driver to be at least what I believe to be current. The driver updates did not change the problem. The same problem is observed regardless of whether a WIFI on ETHERNET source is used for data.

WIFI driver.jpg

Ethernet driver.jpg

I have run a FORTECT on the system and no issues are found.

Fortect scan.jpg

After this started I thought SURSHARK was maybe causing the lockup. I removed it from the computer. No change was noted.

I was running Phone Link but It took it off auto start. No change was noted.

The failure is observed as follows:

Computer power on

Logon

Start IE then Youtube then bring up Advanced network settings.

Ethernet network info.jpg -- Advanced network setting page

After about 3-4 minutes after powerup the system loses access to internet. Youtube will freeze, Email and all internet access is lost.

On the Advanced network settings page the bytes send and received will continue to increment after lockup. The Duration counter will continue to increment after lockup.

I am about at the limit of what I know how to do. I need expert guidance from above. I could reload widows but am resisting unless I really have to. The computer in question appears to run normal in all other respects. I am very suspect the recent Microsoft updates loaded into the system.

Mod note: Edited pictures to remove IP addresses and MAC addresses.

Windows for home | Windows 11 | Internet and connectivity
0 comments No comments

Answer accepted by question author

AI answer

2026-11-01T18:12:52.7733333+00:00

Because both Ethernet and Wi‑Fi lose IP connectivity several minutes after sign-in, test with a clean boot first to determine whether a delayed third-party service—potentially including a remaining VPN filter—is disabling or redirecting networking.

1. Perform a clean-boot test

Removing Surfshark does not necessarily establish that all related services or network components were removed. A clean boot disables non-Microsoft services without reinstalling Windows.

  1. Press Start, type msconfig, and open System Configuration.
  2. Select Services.
  3. Select Hide all Microsoft services.
    Do not skip this checkbox.
  4. Select Disable all, then Apply.
  5. Open Startup → Open Task Manager.
  6. Disable every enabled startup item, recording what you disable.
  7. Restart the PC and leave it running for at least 10 minutes while testing Internet access.

Microsoft documents this procedure specifically for isolating background software conflicts.^1^

  • If connectivity remains working: re-enable half the disabled services, restart, and test again. Continue by halves until the responsible service is identified. Pay particular attention to VPN, firewall, web-filtering, traffic-monitoring, and security-suite services.
  • If it still fails: return to normal startup—System Configuration → General → Normal startup—and continue below.

2. Reset the shared Windows network stack

Because ping [IP Address] and ping microsoft.com both fail, this is not merely a DNS-name-resolution failure. Since both physical adapters fail, reset the Windows components they share.

Open Command Prompt as administrator, run these in order, and restart:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
shutdown /r /t 0

These are Microsoft’s documented commands for resetting Winsock and TCP/IP, renewing addressing, and clearing the DNS cache.^2^

If that does not resolve it, use the broader reset:

  1. Open Settings → Network & internet → Advanced network settings → Network reset.
  2. Select Reset now → Yes.
  3. Allow Windows to restart.

This removes and reinstalls all network adapters and returns their settings to defaults. It can also remove virtual networking configuration, so VPN software or Hyper‑V virtual switches might need to be configured again.^2^

3. Do not assume the October update caused it yet

Build 26200.9711 corresponds to KB5127648, released October 13, 2026.^3^

Microsoft’s Windows 11 25H2 release-health page does not list general loss of Ethernet and Wi‑Fi Internet connectivity as a known issue for that build. The listed October issues concern Remote Desktop, desktop loading, and AC-3 audio—not this symptom.^4^

The KB5133964/65/66 entries therefore should not be treated as the Windows cumulative update responsible for build 26200.9711. Check each entry’s category and publisher in Settings → Windows Update → Update history.

4. Repair Windows without wiping apps or files

If clean boot and network reset both fail, use Windows 11’s in-place repair before considering a full reload:

  1. Temporarily obtain stable Internet access if possible.
  2. Open Settings → System → Recovery.
  3. Under Fix problems using Windows Update, select Reinstall now.
  4. Complete the installation and restart.

This reinstalls the same Windows version, repairs system files and components, and preserves apps, files, and settings. It requires continuous power and Internet access.^5^

5. Roll back only after establishing an update correlation

If the problem also occurs in clean boot but disappears after uninstalling a specific Windows update, that provides a useful correlation. Back up important files first, then use:

Settings → Windows Update → Update history → Uninstall updates

Select only the update installed immediately before the first failure. Some updates cannot be removed, and uninstalling a security update temporarily removes its protections.^6^

A factory reset or clean Windows installation should remain the final option; the in-place repair above is substantially less disruptive.


References

  1. [Windows 11](https://support.microsoft.com/windows/experience/startup-boot/how-to-perform-a-clean-boot-in-windows)
  2. [Windows 11](https://support.microsoft.com/windows/experience/connectivity-networking/fix-ethernet-connection-problems-in-windows#on-your-pc)
  3. October 13, 2026—KB5127648 (OS Builds 26300.9711, 26200.9711 and 26100. ...
  4. Windows 11, version 25H2 known issues and notifications
  5. Fix issues by reinstalling the current version of Windows | Microsoft Support
  6. [Windows 11](https://support.microsoft.com/windows/deployment/updates-lifecycle/how-to-uninstall-a-windows-update#summary)
AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 person found this answer helpful.

2 additional answers

Sort by: Oldest
  1. Hendrix-V 20,785 Reputation points Microsoft External Staff Moderator
    2026-11-02T01:55:04.5033333+00:00

    Hi Dwight Curtis,

    Since both the Wi-Fi and Ethernet drivers have now been updated without changing the behavior, and the Ethernet adapter remains connected and continues exchanging bytes after Internet access stops, this does not look like a simple adapter-disconnect problem.

    At the moment the Internet stops working, please open Command Prompt and run these three commands:

    ping 10.77.1.1
    ping 8.8.8.8
    nslookup microsoft.com
    

    Please post the results from all three.

    • If 10.77.1.1 responds but 8.8.8.8 does not, the PC is still communicating with the local network but cannot reach the Internet.
    • If both pings work but nslookup fails, this points more specifically toward DNS.
    • If all three fail, we can investigate what is blocking network traffic after those first few minutes.

    These three results should give us a much clearer indication of where the connection is actually breaking.

    Was this answer helpful?

    0 comments No comments

  2. Dwight Curtis 20 Reputation points
    2026-11-02T02:03:08.03+00:00

    I found the problem. I had Tailscale software on the system that was the problem. I turned off Tailscale and the problem vanished. I think I have a tailscale exit node problem. For now everything is working.

    The problem isolation method suggested worked just fine.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.