The VPN Still Said “Connected” After Sleep—But My Workday Was Offline

I opened my laptop seven minutes before a client review and saw every reassuring symbol Windows could offer. The hotel Wi-Fi was connected. The VPN icon was present. The battery had survived the train journey. Yet Teams remained on “Signing in,” Outlook would not refresh and the presentation in cloud storage showed an offline error. I blamed the hotel network, disconnected from Wi-Fi and joined my phone’s hotspot. Nothing changed.

I restarted Teams.

Still offline.

Only then did I open the VPN app. Its status said “Connected,” but the timer had stopped at the moment I closed the laptop lid nearly an hour earlier.

I disconnected the VPN and connected again.

My inbox filled immediately. Teams signed in, and the presentation began syncing while the client was already entering the meeting room.

The VPN could connect perfectly well. The problem was what happened after sleep: it left behind a tunnel that looked alive after it had stopped carrying traffic.

The new laptop exposed an old assumption

My trouble began after I replaced an ageing Windows 10 machine. Microsoft ended support for Windows 10 on October 14, 2025, so moving to a Windows 11 laptop had seemed like the responsible choice. (RFC 9000)

The old machine took so long to wake that I usually shut it down completely. The new one encouraged a different habit: close the lid, put it in a bag and expect everything to resume instantly.

Windows 11 is designed around that expectation. Modern Standby lets current laptops wake quickly while the system manages power and network access in the background. Depending on the device and its power state, networking may be reduced or disconnected during sleep.

The screen therefore returned almost instantly. The connection underneath it did not always return in the same condition.

That mismatch was easy to miss. Windows showed Wi-Fi as connected, and the VPN app often retained the same green status it had displayed before sleep. Only the applications exposed the failure: messages did not arrive, shared drives stayed offline and calls stalled before joining.

Other Windows users describe the same routine in simpler terms: wake the laptop, find the internet unusable, restart the VPN and watch everything return. The frustrating part is not the extra click. It is discovering that the click was necessary only after an email, upload or meeting has already failed.

For me, that failure was the client review. So I started with the most obvious response: fix the settings rather than replace a provider I already trusted.

The obvious fixes worked until I changed networks

I was using a major VPN with years of public history, mature infrastructure and servers in dozens of countries. I had relied on it during previous trips, so abandoning it after one bad morning felt premature.

I checked everything I could.

Automatic connection was enabled. The kill switch was active. The app started with Windows. I updated the VPN, installed the latest wireless driver and adjusted the laptop’s power settings so it would be less aggressive about suspending network access.

The next test appeared successful.

I connected the VPN, opened Outlook and closed the lid for ten minutes. When I woke the laptop on the same home Wi-Fi, email refreshed normally.

I assumed the problem was solved.

The following afternoon, I closed the laptop in a café, carried it to a coworking office and opened it on a different Wi-Fi network.

The VPN still displayed “Connected.” Teams did not.

I waited for the network to settle. The Wi-Fi icon recovered first. The VPN remained green. Outlook stayed offline until I manually disconnected and rebuilt the tunnel.

The settings had improved a controlled sleep test. They had not solved the situation that caused the real trouble: waking somewhere else, on a network the VPN had never seen before.

That changed the comparison. A fast tunnel before I closed the lid was not enough if it became an empty shell while the laptop was in my bag.

The green icon became part of the problem

Once I recognised the pattern, I started noticing it everywhere.

At home, the VPN usually recovered because the laptop woke on the same router. Hotels were less predictable. Weak signals, captive portals and several access points sharing one network name gave the tunnel more chances to lose its route.

Mobile hotspots made the failure impossible to ignore. I would close the laptop on hotel Wi-Fi, reopen it in a taxi and join my phone’s data connection. Windows had internet, but the VPN still behaved as though it belonged to the network I had left behind.

Sometimes it recovered after half a minute. Sometimes one manual reconnect fixed it. On two occasions, the app became stuck on “Disconnecting,” forcing me to close it completely.

Changing server countries did not help because the selected destination was not the immediate problem. The tunnel itself had failed to rebuild around the laptop’s new connection.

I could not observe whether Windows had suspended the adapter, whether the session had expired during sleep or which internal step had stalled during recovery. The visible result was consistent: every time I opened the lid, I had to inspect and sometimes repair the VPN before trusting the applications above it.

At that point, “automatic connection” no longer described what I needed.

I needed automatic recovery.

The real test began when I closed the lid

Before the next trip, I installed OnlydogVPN.

The smaller app organised its choices around situations rather than opening with a large country map. I selected the option for weak and changing networks, connected and opened the same applications that had failed before: Outlook, Teams and the cloud folder containing the client presentation.

Then I closed the lid.

I left the laptop asleep for twenty minutes, moved it away from home Wi-Fi and enabled my phone’s hotspot. When I opened the laptop again, Windows found the new network.

The VPN recovered behind it.

Outlook refreshed before I opened the VPN app. Teams showed me as available, and the presentation finished syncing without the familiar disconnect-and-reconnect routine.

The result felt almost uneventful. That was exactly the point.

I repeated the test with a longer sleep. This time, the laptop went into my bag while connected to a train-station network. I woke it later in a hotel room, joined the hotel Wi-Fi and opened the shared folder.

The newest files appeared.

There was no stale green icon to investigate and no need to remember which network had existed before sleep. The service treated the new connection as something to recover onto, not as a reason to preserve a dead tunnel.

Recovery mattered more than the protocol lesson

The service uses an HTTP/3-based transport designed to recover cleanly when a device’s network changes.

That is the useful explanation. When sleep destroyed the old path, the service established a working one after wake instead of waiting for me to reset it manually.

HTTP/3 runs over QUIC, a transport built to handle changing network paths more gracefully than a connection tied rigidly to one address. For a travelling laptop, that means the VPN is better suited to a common sequence: hotel Wi-Fi before sleep, mobile data after wake and another access point later in the day.

I did not need a deeper protocol lesson to understand the benefit.

With the previous provider, every wake-up began with uncertainty. Was Teams slow, or was the tunnel dead? Should I wait, change networks, restart the app or choose another server?

With the smaller service, I opened the lid and returned to the application I had intended to use.

That was a more useful definition of automatic.

The meeting became the final test

The client review that had exposed the problem was rescheduled for the following week.

Ten minutes before it began, I was working in a library lounge. The Wi-Fi was strong, but the building was closing early. I packed the laptop, walked outside and reopened it on my phone’s hotspot while looking for somewhere quieter.

The VPN recovered before Teams finished opening.

I joined the meeting from a bench, then moved into a café when traffic became too loud. Near the entrance, the phone briefly changed mobile bands and the connection paused.

The client’s voice stopped for a moment.

Then it returned.

The shared presentation remained open, and I did not have to leave the meeting to repair the VPN.

That completed the task the previous setup had failed. The service did not merely reconnect during a controlled experiment. It remained useful through the messy sequence of closing the lid, changing locations, waking on a hotspot and joining a live call.

Recovery had stopped being something I checked. It had become part of the background.

The smaller service has less history

The service offers fewer server locations than the major provider I used first. It also has a shorter public history, fewer ratings and less independent testing.

Those limitations matter when someone needs a specific city, an unusual country or the reassurance of many years of published operational evidence.

The established provider remained stronger on geographic choice. It also offered more troubleshooting documentation.

But troubleshooting had become part of my daily routine.

Its large network could give me another server after I manually restored the connection. The smaller app restored the connection before I needed to think about servers at all.

For a desktop computer that rarely moves, that difference may be minor. For a laptop that sleeps whenever its lid closes, it determines whether work resumes when the screen does.

“Connected” was the wrong measurement

I began by judging VPNs at the moment they created a tunnel.

That made connection times, speed tests and server lists look important. It also ignored everything that happened after the laptop entered my bag.

The major provider connected quickly and offered many places to connect through. After sleep, however, its green icon sometimes represented a tunnel that no longer carried anything.

The smaller app solved the more valuable problem. It recovered after the original network disappeared, rebuilt a working path and let Outlook, Teams and cloud storage continue before I had to inspect the VPN.

A laptop VPN should not be judged when the lid closes.

It should be judged by what is already working when the lid opens again.