How to Configure System Idle Power Saver on Network Adapters in Windows 11 Using PowerShell

Modern Gigabit and multi-gigabit Ethernet adapters incorporate multiple layers of dynamic power management to satisfy modern energy efficiency standards such as Energy Star and European Union Lot 6. In addition to link downshifting and Energy Efficient Ethernet (EEE), many Network Interface Card (NIC) controllers—particularly those manufactured by Realtek, Intel, and Broadcom—feature System Idle Power Saver (SIPS). When Windows 11 enters an idle state or when network packet density drops below a hardware threshold, SIPS scales down transceiver voltages and internal DSP processing to minimise power consumption. While advantageous for battery life and thermals, SIPS can induce intermittent packet drops, first-packet latency spikes, and connection stalls when endpoints resume active communication. In enterprise and high-performance environments, configuring SIPS via PowerShell provides deterministic control over adapter behaviour.

How System Idle Power Saver Operates in Windows 11

System Idle Power Saver operates at the physical layer (PHY) and medium access control (MAC) interface of the network controller. Unlike operating system sleep states (S3/Modern Standby), SIPS functions while Windows remains fully awake. When the operating system determines that CPU activity is idle and the NDIS driver detects minimal ingress/egress queue traffic, SIPS transitions the Ethernet transceiver into an ultra-low-power idle state.

While in this low-power state, the transceiver maintains physical link synchronization with the upstream switch port but reduces internal clock frequencies and signal amplification. When an outbound network frame is dispatched or an inbound broadcast arrives, the hardware must exit the low-power mode, re-synchronise internal Phase-Locked Loops (PLLs), and re-engage full signal voltage. This wake-up transition introduces microsecond-to-millisecond latency penalties. In environments running real-time VoIP, financial transactions, database queries, or remote desktop protocols (RDP), this wake-up lag can cause dropped frames or noticeable interface stutter.

Querying Network Adapters and SIPS Properties

To inspect your network hardware and locate the exact registry property name exposed by your network driver, launch an elevated PowerShell session and list active physical adapters:

Get-NetAdapter -Physical | Select-Object -Property Name, InterfaceDescription, Status, LinkSpeed

To identify whether your adapter driver supports SIPS or related idle power-management properties, query the adapter’s advanced properties using Get-NetAdapterAdvancedProperty:

Get-NetAdapterAdvancedProperty -Name "Ethernet" | Where-Object { $_.DisplayName -match "Idle|SIPS|Power Saver" }

Depending on whether the driver is an official vendor package (such as Realtek PCIe GbE Family Controller) or a Microsoft in-box NDIS driver, the setting typically appears under the display name System Idle Power Saver or the registry keyword *SIPS or SIPS. Retrieve its current configuration and allowed display values:

Get-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "System Idle Power Saver" | Select-Object DisplayName, DisplayValue, RegistryKeyword, RegistryValue

Disabling SIPS to Eliminate Idle Latency and Packet Stalls

In low-latency scenarios—such as high-frequency trading stations, competitive multiplayer gaming, audio-over-IP (Dante/AES67), or local virtualisation hosts hosting database workloads—disabling SIPS ensures that the physical transceiver operates at full power continuously, delivering immediate packet transmission without wake-up penalties.

To disable SIPS on your primary Ethernet interface, execute Set-NetAdapterAdvancedProperty:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "System Idle Power Saver" -DisplayValue "Disabled"

If script automation requires referencing the registry keyword directly, apply the setting via RegistryKeyword:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -RegistryKeyword "SIPS" -RegistryValue "0"

Applying this change causes an instantaneous, sub-second physical layer reset as the PHY transceiver renegotiates link power parameters with the upstream switch. The network interface will momentarily display a disconnected state before returning to service.

Enabling SIPS for Energy Conservation

In office workstations, commercial call centres, or battery-operated mobile docking stations where energy conservation and heat reduction take priority over microsecond-level latency, enabling SIPS reduces overall endpoint power draw.

To enable System Idle Power Saver via PowerShell, run:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "System Idle Power Saver" -DisplayValue "Enabled"

Or configure the registry keyword directly:

Set-NetAdapterAdvancedProperty -Name "Ethernet" -RegistryKeyword "SIPS" -RegistryValue "1"

Verify that the updated setting is active by querying the property again:

Get-NetAdapterAdvancedProperty -Name "Ethernet" -DisplayName "System Idle Power Saver"

Automating Fleet-Wide Configuration Across Multiple Endpoints

For systems administrators deploying standardized endpoint baselines across enterprise environments, script automation must dynamically handle varying adapter names. The following PowerShell script identifies all physical Ethernet adapters, checks for the presence of the SIPS keyword or display name, and enforces a deterministic power policy:

$EthernetAdapters = Get-NetAdapter -Physical | Where-Object { $_.MediaType -eq "802.3" }

foreach ($NIC in $EthernetAdapters) {
    $Property = Get-NetAdapterAdvancedProperty -Name $NIC.Name -ErrorAction SilentlyContinue |
        Where-Object { $_.DisplayName -match "System Idle Power Saver" -or $_.RegistryKeyword -match "SIPS" }

    if ($Property) {
        Write-Host "Disabling SIPS on: $($NIC.Name) ($($NIC.InterfaceDescription))" -ForegroundColor Cyan
        Set-NetAdapterAdvancedProperty -Name $NIC.Name -RegistryKeyword $Property.RegistryKeyword -RegistryValue "0"
    } else {
        Write-Host "SIPS not supported on interface: $($NIC.Name)" -ForegroundColor DarkGray
    }
}

Validating Link Performance and Monitoring Event Logs

After adjusting transceiver power settings, verify that the physical link maintains its rated speed without unexpected renegotiations. Check link speed and duplex status:

Get-NetAdapter -Name "Ethernet" | Select-Object Name, Status, LinkSpeed, FullDuplex

Additionally, monitor the Windows System Event Log for any NDIS link reset events (Event ID 10400) or driver resets that may indicate link instability:

Get-WinEvent -FilterHashtable @{
    LogName = 'System'
    ProviderName = 'Tcpip'
    StartTime = (Get-Date).AddHours(-1)
} -ErrorAction SilentlyContinue | Select-Object TimeCreated, Id, Message -First 5

With SIPS disabled, the transceiver maintains continuous signal integrity, eliminating the physical power transitions responsible for idle wake-up delays and ensuring steady, high-performance network throughput.