Windows Fast Startup (hybrid shutdown) saves the kernel session to disk instead of performing a full cold boot, which prevents the network interface card from re-initializing and sending new DHCP requests upon wake. This causes devices to retain stale IP configurations or fail to obtain leases when network conditions change, such as moving between different subnets or when a DHCP relay like pfSense is in hot-standby mode. To resolve this, you must either disable Fast Startup entirely or configure the network adapter to allow it to wake the system and send fresh requests.
Understanding Hybrid Shutdown Behavior
When you select "Shut Down" in modern versions of Windows 10 and 11, the operating system does not completely power off the hardware. Instead, it enters a state known as Fast Startup or hybrid shutdown. During this process, the user session is logged out, but the core kernel session, loaded drivers, and system state are compressed into a hibernation file calledhiberfil.sys. When the computer powers on again, Windows restores this saved state rather than performing a complete hardware initialization sequence.
This behavior significantly speeds up boot times because the OS skips many driver loading steps. However, for networking components, this shortcut creates a critical problem. The network interface card (NIC) is not reset during the resume process. It remains in the same state it was in before the shutdown occurred. If the device had an active DHCP lease at the time of shutdown, that lease is retained in memory. Upon waking, the NIC does not broadcast a new DHCP Discover packet because it believes its network configuration is still valid.
In environments where dynamic IP assignment is crucial, such as those using pfSense as a DHCP server or relay agent, this static retention of network settings leads to connectivity failures. If the IP address has expired, been revoked by the server, or if the device has moved to a different VLAN or subnet, the machine will attempt to communicate with an invalid or unreachable address. Since no new request is sent, the operating system never receives a new lease, leaving the network connection broken until manually corrected.
The Role of DHCP Relays
The issue becomes more pronounced when a DHCP relay agent is involved. A relay agent forwards DHCP broadcasts from clients on one subnet to a DHCP server on another. If Windows Fast Startup prevents the initial broadcast from being sent after boot, the relay agent never receives the request. Consequently, the DHCP server cannot assign an address. This is particularly problematic in hot-standby configurations where failover events might have changed the network topology. The client machine, unaware of these changes due to its frozen network state, continues to use outdated routing information. Related articles: Windows Dynamic DNS Update Issues at Boot provides context on how network services interact with system startup states, while Disabling Automatic DNS Configuration in Windows 11 without Disabling DHCP offers alternative management strategies for network parameters that do not rely on standard DHCP renewal cycles.How to Disable Fast Startup
The most reliable solution to ensure that every boot results in a full network re-initialization is to disable Fast Startup. This forces Windows to perform a cold boot, resetting all hardware drivers and triggering standard DHCP discovery processes. Follow these steps to turn off the feature:- Open the Control Panel. You can search for it in the Start menu or run
control panelfrom the Run dialog. - Navigate to Hardware and Sound and then click on Power Options.
- In the left-hand pane, select Choose what the power buttons do.
- If the options are grayed out, click the link at the top that says Change settings that are currently unavailable. This requires administrative privileges.
- Under the Shutdown settings section, uncheck the box labeled Turn on fast startup (recommended).
- Click Save changes to apply the setting.
Configuring Network Adapter Wake Settings
If disabling Fast Startup is not feasible due to performance requirements, you can attempt to configure the specific network adapter to handle wake events correctly. While this does not fully reset the NIC, it may help in scenarios where the system needs to respond to wake-on-LAN packets or trigger basic network checks.- Right-click the Start button and select Device Manager.
- Expand the Network adapters category and locate your primary Ethernet or Wi-Fi adapter.
- Right-click the adapter and select Properties.
- Go to the Power Management tab.
- Ensure that Allow this device to wake the computer is checked.
- Optionally, check Only allow a magic packet to wake the computer if you want to restrict wake triggers, though this may interfere with standard DHCP renewals depending on driver implementation.
Manual Renewal Workarounds
For users who cannot modify system-wide power settings immediately, manual intervention is required to restore connectivity. If you experience network loss after waking from sleep or shutdown, you can force a new DHCP lease without rebooting. Open Command Prompt as Administrator and execute the following commands:ipconfig /release
ipconfig /renewFrequently Asked Questions
Does restarting Windows disable Fast Startup?
No, selecting "Restart" performs a full cold boot regardless of the Fast Startup setting. Fast Startup only affects the "Shut Down" option. Therefore, if you restart your computer, the network adapter is fully reset and DHCP requests are sent normally. This is why restarts often appear to work while shut downs cause issues.Can I keep Fast Startup enabled but fix the DHCP issue?
It is difficult to reliably fix the DHCP issue while keeping Fast Startup enabled because the core mechanism prevents the network stack from initializing fresh. Some advanced driver settings might allow wake-on-DHCP, but support varies widely by manufacturer. The most consistent technical solution remains disabling the feature in the Power Options.Why does my IP address change after disabling Fast Startup?
Disabling Fast Startup ensures that the network adapter sends a new DHCP request upon boot. If your network environment assigns dynamic addresses based on MAC address or time-of-day policies, you may receive a different IP than the one cached during the previous shutdown. This is normal behavior for a healthy DHCP client and indicates that the system is now communicating correctly with the server.Does Fast Startup affect Wi-Fi connections similarly?
Yes, Fast Startup impacts Wi-Fi adapters just as it does Ethernet. Wireless networks often require re-authentication and new IP assignments, especially when connecting to different access points or when the router has restarted. Disabling Fast Startup helps Wi-Fi devices reconnect properly by forcing a full driver reload and association process.Is there a registry key to disable Fast Startup?
Yes, you can disable Fast Startup via the Registry by navigating toHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power and setting the HiberbootEnabled DWORD value to 0. However, using the Control Panel GUI is safer and preferred because it also updates related power scheme settings automatically.