Windows
Always wait for the network at computer startup and logon can transform a 5-minute boot into a frustrating 15-minute delay—especially when you’re just checking email or launching a quick app.
Frustrated by the endless delay when your Windows PC waits for a network connection at startup? This annoying pause can add minutes to your boot time—and there’s a simple way to disable it permanently.
Whether it’s a misconfigured Group Policy, a lingering service delay, or an outdated network driver, the root cause is often hiding in plain sight.
Below, I’ll walk you through the safest ways to force-disable this wait, from tweaking Windows settings to registry edits (with caution), so you can reclaim that time every morning.
You’ll also learn how to troubleshoot potential fallout—like offline file access issues—so you can speed up your boot without breaking anything critical.
How to disable 'Always wait for the network' in Windows startup settings
If your Windows 10/11 system pauses at startup waiting for a network connection, you’re not alone. This network delay can add 10-30 seconds to your boot time, but it’s easy to disable.
Below, I’ll show you three methods: using Group Policy Editor, Registry Editor, or Local Group Policy. Each method is safe for Pro/Enterprise editions but requires admin rights.
The Always Wait for the Network setting is controlled by Group Policy or the Registry. Disabling it forces your PC to boot faster, but be aware—some network-dependent apps (like mapped drives or cloud sync) may fail if offline. I’ll cover workarounds for those later.
Before proceeding, back up your registry (File > Export in Registry Editor) and note your Windows version. These steps work for Windows 10 (1909+) and Windows 11, but Home editions lack Group Policy—use the Registry method instead.
Step-by-Step Guide to Disable Network Wait
-
Method 1: Group Policy Editor (Pro/Enterprise)
- Press Win + R, type gpedit.msc, and hit Enter.
- Navigate to Computer Configuration > Administrative Templates > System > Logon.
- Double-click "Always wait for the network at computer startup and logon".
- Select Disabled or Not Configured, then click Apply > OK.
-
Method 2: Registry Editor (All Editions)
- Press Win + R, type regedit, and hit Enter.
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
- Right-click > New > DWORD (32-bit) Value, name it WaitToKillServiceTimeout.
- Double-click it, set Value data to 2000, and click OK.
- Create another DWORD: WaitToKillServiceTimeout (if missing), set to 2000.
- Restart your PC.
-
Method 3: Local Group Policy (Alternative)
- Open Run (Win + R), type gpedit.msc, and press Enter.
- Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
- Find "Network security: Configure encryption types allowed for Kerberos" (irrelevant here—scroll to bottom).
- Use the Registry method above if this path is missing.
After applying any method, restart your PC to test the changes. Your system should now boot without the network delay. However, if you rely on network drives or cloud sync tools, you may need to manually reconnect them post-boot or adjust Group Policy for those services.
For Windows Home users, the Registry method is your only option. If issues arise (e.g., offline file errors), revert the changes by restoring your Registry backup or running System Restore.
Pro tip: Combine this fix with Fast Startup (enable in Control Panel > Power Options) to further reduce boot times. Just ensure your SSD is healthy—a failing drive can mask performance gains.
If you’re using Windows 11, Microsoft may reintroduce this delay in updates. Monitor Windows Update for changes and reapply the fix if needed.
Potential risks and fixes when disabling network startup delay
Disabling the network startup delay can shave off crucial seconds during boot—but it’s not without risks. When Windows skips waiting for a network connection, you might encounter offline file access errors or mapped drive failures.
These issues often arise when applications or services rely on network resources that aren’t immediately available. For example, Microsoft Office or Slack may fail to sync if their cloud dependencies aren’t ready at startup.
Another common problem is Group Policy misconfigurations. If your organization enforces domain policies that require network access during login, disabling the delay could trigger authentication errors or policy enforcement failures.
Even on personal PCs, some third-party apps (like Dropbox or OneDrive) may behave unpredictably if they can’t connect to their servers immediately.
If your system relies on network-dependent apps (e.g., VPNs, cloud sync tools, or domain-joined machines), forcing a faster boot may cause login failures or data corruption. Always test changes in a safe environment first.
To mitigate these risks, start by adjusting Group Policy settings. Open the Local Group Policy Editor (press Win + R, type gpedit.msc, and hit Enter). Navigate to: Computer Configuration > Administrative Templates > System > Logon.
Here, enable "Always wait for the network at computer startup and logon" if you later realize you need it. For Windows 10/11 Home users, use the Registry Editor (Win + R > regedit) to toggle the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System key.
For mapped drive issues, create a manual network reconnection script. Use a PowerShell script or batch file to delay network-dependent tasks. For example, add a 10-second pause before launching apps that need network access: Start-Sleep -Seconds 10 Then, manually map drives or launch critical applications.
Store this script in your Startup folder (C:\Users\[YourUsername]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup).
If you’re on a domain-joined PC, consult your IT admin before making changes. Some organizations enforce mandatory network policies during login, and disabling the delay could violate compliance requirements. In such cases, ask about alternative optimizations, like pre-boot network services or Group Policy exceptions.
For offline file access, consider using local caching tools like Microsoft’s Offline Files or third-party sync clients that prioritize local storage. Enable this feature via Control Panel > Sync your settings > Offline Files.
This ensures critical files remain accessible even if the network is delayed or unavailable during startup.
