Random ERR_NETWORK_IO_SUSPENDED in Windows applications (network itself *is* working)

Anonymous
2022-01-18T18:49:57+00:00

Quite often Windows applications are stuck (frozen) with error ERR_NETWORK_IO_SUSPENDED.

(Typically observed in Chrome, but impacts also any other application, e.g. Edge)

When:

  • after returning from sleep mode
  • *but also* at random time

For how long:

  • several minutes
  • then the applications automagically resume to normal behaviour

What is impacted:

  • all Windows applications at the same time
  • except WSL, that is *not* affected (e.g. I can do a curl without any problem)

Network itself is not the cause!:

  • other devices in my LAN still have access to Internet during the incidents
  • WSL still has access to Internet too!

I had the impression I could have solved the issue after forcing a downgrade/upgrade of Windows, but the problem is there again (maybe since the last Windows update). Windows version is up to date. Already tried to reboot many times, of course. To no avail.

This issue is extremely frustrating, when you are are stuck in the middle of a sentence and have to look at your laptop during long minutes before being able to finish typing. (BTW, got stuck twice while typing the present question!)

I'm quite desparate with this. Don't even have a clue on how to investigate. Did not find anything interesting in Event Viewer.

Context:

  • Surface_Book_3_1900
  • Windows 10 Home 10.0.19044

Moderator note - Moved from Windows to Surface.

Surface | Surface Book | Network

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

54 answers

Sort by: Most helpful
  1. Anonymous
    2022-01-19T20:18:48+00:00

    Hi Arnauld Van Muysewinkel,

    Thank you for reaching Microsoft Community.

    May I know when did this behavior started and can you recall if there were any changes made on the device before it started?

    Just to make sure: the device is connected to your network through an Ethernet cable, correct?

    Kindly run these steps first on your Surface Book 3 then check if the issue persist:

    1: Run Surface Diagnostic Toolkit

    See: Fix common Surface problems using the Surface Diagnostic Toolkit (microsoft.com)

    2: Check for Windows Update

    Go to Windows Settings > Update & Security and select Check for updates

    Make sure all updates need are installed including Optional updates

    3: Update drivers and firmware

    Check what is the current OS Build of your Windows version by going to Settings > System > About

    Go to Download driver and firmware for Surface, choose Surface Book

    Then click the link next to Surface Book 3 then click Download on the next page.

    Choose the .msi file that matches your current OS Build and click Next.

    After downloading, run and install the .msi then Restart. 

    4: Run System File Checker Tool

    See: Using System File Checker in Windows (microsoft.com)

    If still the issue persist, try these steps below:

    1: Run network commands

    Open Command Prompt (Admin)

    Type and enter these commands:

    netsh winsock reset

    netsh int ip reset

    ipconfig /release

    ipconfig /renew

    ipconfig /flushdns

    Close Command Prompt windows then restart the Surface

    2: Uninstall/re-install network adapter

    Open Device Manager

    Expand Network adapters

    Right-click on Intel WiFi 6 and select Uninstall device

    Note: If prompted with a checkbox stating "Delete the driver software for this device", leave it uncheck then hit Uninstall.

    Restart the Surface

    Hope this helps.

    0 comments No comments
  2. Anonymous
    2022-02-07T17:11:36+00:00

    1: Run Surface Diagnostic Toolkit

    -> Did not find any issue

    2: Check for Windows Update

    ->

    • Was up to date at the time of opening the case.
    • Few days later, there was a new Windows 10 update
    • I installed the update.
    • Problem disappeared
    • A week or so after, the problem re-appears: system freeze once for a few minutes shortly after it as been awaken
    • More days passed, and the problem becomes worse (it freezes more than once, and the freezes last longer)

    Note that I already observed this behaviour before : it disappear when I install a windows update (or if I rollback then re-install the last update), then it progresively comes back.

    And, as already explained, the low level network stack *is* working since WSL2 has no issue with the network, even while Windows applications are freezing.

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-02-10T15:06:49+00:00

    Stumbled over this by accident ...

    I faced a very similar behavior on my HP Spectre x360 Intel Core i7-1065G7 since Dec 2021.
    I after wakeup from hibernate the affected application takes several minutes before it could be use network stack again (both wifi as well as cable are affected).

    Closing and restarting the affected application speeds this up a little but is no true™ workaround.

    0 comments No comments
  4. Anonymous
    2022-02-15T15:23:42+00:00

    I have the same issue.

    The solutions given by Marrion above are all standard solutions to very basic issues.

    Our issue at hand cannot be solved by those. The reason must be known first.

    Most of us have Windows updated. Uninstalling/reinstalling network adapter will not solve why applications freeze.

    In my case, when my computer wakes up from hibernation, Chrome freezes but also other Windows applications. BUT Microsoft Edge still works and also Firefox.

    Mail, MS Store, Xbox app, all freeze. Even my mouse application freezes.

    4 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2022-02-17T04:20:53+00:00

    Seems to be a known error and apparently started on Jan 2022... I got a brand-new ASUS laptop 2 days ago and facing this issue, the ASUS support apparently copied and pasted the instructions above provided by Microsoft agent... and Yes is fully updated.

    What I'm doing as a workaround is to every time that I've done with whatever I'm doing, just shut down the laptop, I used to hibernate like the rest of the users (That's how should be) on my previous laptop without having this issue, that being said until Microsoft provide a patch or a real solution rather than the good old "hit restart" you might need to consider turning off your laptop every time you are no longer using it.

    2 people found this answer helpful.
    0 comments No comments