Always Wait for the Network at Computer Startup and Logon: Disable It in 3 Clicks

Always wait for the network at computer startup and logon—turning a 30-second boot into a 5-minute slog—and it’s a setting you can disable in seconds.

Stuck watching the login screen freeze while your PC hunts for a connection that isn’t there? This delay isn’t just annoying—it’s a misconfigured dependency that forces Windows to wait for something it can’t find. The good news? You don’t need to be a tech expert to fix it.

Whether it’s a Group Policy quirk, a corrupted registry tweak, or a service stuck on "waiting," we’ll show you how to bypass the delay in three clicks or less. No command-line jargon, no guesswork—just a faster startup.

By the end, you’ll know exactly where the setting hides, how to verify it’s disabled, and when you shouldn’t turn it off (spoiler: it’s rarely needed). Let’s get your PC back to speed.

Why 'Always wait for the network' slows down your Windows startup

When you enable 'Always wait for the network at computer startup and logon' in Windows, your PC pauses booting to check network connectivity. This feature, controlled by Group Policy or Registry, forces Windows to wait up to 30 seconds for a network response—even if you're offline.

For remote workers or users on unreliable Wi-Fi, this translates to unnecessary delays every time you power on your device.

The delay occurs because Windows prioritizes network-dependent services like DNS resolution and domain authentication before completing the login process. If your router is slow, the connection drops, or DNS servers are unreachable, your startup time balloons.

This is especially painful on SSDs, where boot times should be sub-10 seconds but get bogged down waiting for a network that may never respond.

For domain-joined PCs or systems relying on network-based authentication, this setting ensures security—but for most home users, it’s pure overhead. Even a 1-second DNS delay compounds across multiple services, turning a 15-second boot into a 45-second slog.

The root cause lies in how Windows service dependencies interact with network availability during startup.

Under the hood, this setting triggers a Group Policy rule (Computer Configuration > Administrative Templates > System > Logon) that modifies the Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.

When enabled, Windows writes a DWORD value of 1 to WaitToKillServiceTimeout, effectively stalling the boot process until network-dependent services confirm connectivity.

For offline users, this becomes a major inconvenience. If you're working on a laptop without Wi-Fi or connected to a slow Ethernet link, the delay is avoidable. The setting also conflicts with local account logins, where network checks are irrelevant.

Even Windows updates may stall if the system waits for a network response before applying patches.

Technically, the delay stems from Windows' service startup order. Services like DnsClient and LanmanWorkstation are marked as network-dependent, meaning they must confirm connectivity before other services (like Winlogon) proceed. Disabling this setting removes the dependency, allowing Windows to bypass network checks entirely.

Remote workers often face this issue when switching between VPN connections and local networks. A VPN timeout or firewall block can trigger the 30-second wait, even if you’re already connected to a local network.

The same applies to domain-joined machines that rely on Active Directory for authentication—though in corporate environments, disabling this setting may break Group Policy enforcement.

If you frequently work offline or on unreliable networks, this setting is a hidden performance killer. The fix is simple: disable it via Group Policy Editor or Registry Editor.

Once removed, your Windows boot time will revert to being controlled by your storage speed (SSD/HDD) and CPU performance, not network latency.

For power users, the trade-off is clear: faster boots vs. potential network-dependent app failures (like Outlook or Slack). We’ll cover when you should keep this setting enabled—and how to work around it—in the next section.

Until then, ask yourself: why should your PC wait for a network that might not even exist?

3 Fast methods to disable 'Always wait for the network' in Windows (with screenshots)

If your Windows PC waits indefinitely for a network that isn't even connected, you're experiencing the Network Wait at Startup issue. This happens when Windows enforces Group Policy or Registry settings that require network availability before completing boot.

Below, I’ll show you three foolproof methods to disable this behavior—no technical expertise required.

Before diving in, note that these methods work for Windows 10/11 Pro, Enterprise, or Education. If you’re on Windows Home, skip the Group Policy Editor method and use Registry Editor or Local Security Policy instead. Always back up your system before making changes.

If you don’t see the Group Policy Editor or Local Security Policy options, your Windows edition might not support them. In that case, Method 2 (Registry Editor) is your best bet. For extra security, create a system restore point before editing the registry.

After applying any of these fixes, test your boot time by restarting your PC. If the issue persists, check for third-party antivirus or firewall settings that might enforce network delays. Some corporate networks also enforce this policy—contact your IT admin if needed.

Pro tip: If you frequently work offline, consider disabling network-dependent services like Windows Update or OneDrive during startup via Task Manager > Startup. This can further speed up your boot process. 🖥️