What is Modern Standby (S0ix), how does it work, and why does it cause so many problems?

If you have a modern Windows laptop and notice that the battery drains faster than usual while it's in sleep mode , it's very likely that your computer isn't using the classic S3 sleep mode, but rather the newer, low-power mode called Modern Standby (S0ix) . This system promises a mobile-like experience: screen off, computer seemingly asleep, but still connected and able to continue running tasks in the background.

The problem is that this nice theory doesn't always match reality. Many users find that, instead of saving battery, their laptops consume more power, overheat at idle, and even run out of charge overnight . To understand what's happening, why some manufacturers implement it better than others, and how it affects Windows and Linux, we need to look at the details of exactly what S0ix is, how Modern Standby works, and how it differs from the older S3.

What is Modern Standby (S0ix) and where did it come from?

Modern Standby is the name Microsoft uses for a set of low-power states within the S0 power state , originally defined by ACPI as S0ix (S0 idle low power). Unlike the traditional S3 sleep mode—where the system enters a state of deep sleep—in Modern Standby the computer technically remains in S0 , but with the processor and most components operating at minimal power levels.

The idea comes from the world of smartphones: the device has its screen off, appears asleep, but remains connected to the network , able to receive notifications, download emails, or apply updates while you're not using it. In Windows 8 and 8.1, this was called Connected Standby. With Windows 10 and later, the concept was expanded and renamed Modern Standby , adding more hardware flexibility and also allowing for scenarios with the network disconnected.

In practice, when a laptop supports Modern Standby, it means that its firmware, drivers, and operating system are prepared to go through different S0ix substates , where the SoC turns off almost everything except what is essential to listen for "interesting events": a keystroke, a specific network packet, a system maintenance signal, etc.

In modern Intel and AMD processors, these S0ix states are closely tied to the SoC design. AMD, for example, added support for S0ix in Ryzen processors through AGESA updates; in a public tweet, they confirmed that AGESA 1.9.0.0 incorporated S0ix compatibility , but that doesn't mean all motherboard manufacturers enable it in the BIOS , nor that all models display it in the same way.

Modern Standby versus classic S3 suspension

To understand the problems and advantages of Modern Standby, it's necessary to compare it with the traditional S3 (Sleep) model , which has been the standard for years in laptops and desktops. With S3, the system is either fully active or in a deep sleep state; there isn't such a fine range of power consumption levels.

In S3 mode, the processor shuts down, many devices are completely de-powered, and the RAM maintains a self-refresh rate with very low power consumption. This results in extremely low power consumption: in well-tuned laptops, it can be around 2 watts, and the system temperature remains very low, almost as if it were turned off.

With Modern Standby, on the other hand, the system doesn't jump abruptly into a deep state, but rather gradually deactivates components . The transition from active use to a very low-power S0ix state is a series of steps: the operating system stops services, applications lose permission to run freely in the background, drivers power down hardware components when they are no longer needed, and so on.

The key difference lies in the "path" to low power consumption. In S3, the firmware plays a significant role in this transition; in Modern Standby, the logic largely rests with the operating system and drivers , enabling much faster sleep inputs and outputs and, theoretically, better integration with modern hardware.

In a well-configured Modern Standby system, when it enters its lowest power state, the practical appearance is very similar to that of a system in S3: CPU off, RAM in auto-refresh mode, and almost no power consumption . However, since the system officially remains in S0, it can be reactivated in milliseconds, and the operating system can decide precisely when to "wake up" to perform maintenance tasks or handle network traffic.

One of the important benefits for the user is the "instant power-on": from the moment you press the button or open the cover until you see the screen turn on, less than a second usually elapses, very similar to what happens with a mobile phone or tablet, much faster than the classic S3 resume.

How a Modern Standby session works in Windows

Microsoft describes Modern Standby as a continuous session that spans from when the screen turns off until it turns back on . Within this session, there are two main segments: the "screen off" phase and the "deep sleep" phase in OS X. The system alternates between periods of near-total inactivity and short periods of controlled activity.

When the user activates sleep mode—by pressing the power button, closing the lid, selecting the Sleep option from the Start menu, etc.—Windows begins the process of entering Modern Standby. During this phase, both applications and operating system components prepare for low-power operation: stopping background tasks, pausing synchronization, saving states, and so on.

Next, the drivers and hardware must do something similar. The system notifies the various devices that they need to enter low-power states . Only when the software and hardware are ready does Windows push the SoC into a low-power S0ix state, listening only for important events.

While the computer is in Modern Standby, occasional transitions to active mode may occur. This typically happens for three reasons: user input, network activity, or internal system tasks . For example, a network packet matching a Wake-on-LAN (WoL) pattern, an integrated keyboard, a mouse, or an internal timer can trigger a brief "wake-up" to perform a specific task.

In Windows 10 and later, the general rule is that all activity in Modern Standby is severely limited in frequency and duration . The system attempts to keep the SoC in the deepest S0ix state for as long as possible, only waking up in very brief bursts when absolutely necessary. The goal is to drastically reduce the number of times software can execute code while the computer is idle.

In early systems with Connected Standby in Windows 8.1, Windows forced at least one transition from idle to active every 30 seconds for kernel maintenance tasks. That requirement disappeared in Modern Standby for Windows 10, allowing for much longer periods of deep idle and, in theory, significantly greater battery savings if everything is properly configured.

When the user decides to resume the computer—for example, by pressing the power button or opening the lid—the screen turns on almost immediately , the network adapters resume their active operating modes, and the desktop applications become available again. The design goal is for the response time to be comparable to unlocking a phone: virtually instantaneous.

Modern Standby: Connected vs. Disconnected and Network Behavior

Modern Standby systems can operate in two main modes: connected to the network or disconnected during sleep. In connected mode, which is more similar to Connected Standby, the computer can continue syncing email, receiving VoIP calls, downloading news, or applying certain types of updates while it is asleep.

When the system has no services or applications that require network traffic, the adapter enters a low-power mode , offloading some network logic to the hardware itself (protocol offload) and maintaining Wake-on-LAN (WoL) patterns to respond to certain packets. In this state, power consumption is minimal and the device should not get noticeably hot.

If a system service or an app with permissions needs the network—for example, the email client syncing the inbox or the Windows Update service checking for critical patches—Windows reactivates the network interface, temporarily puts it into an active state , performs the necessary task, and then lowers it back to low power mode.

Sometimes, a laptop may remain in active mode (always with the screen off) for longer than desired. This usually happens when Windows determines it needs to complete more demanding maintenance tasks : installing critical updates, indexing, disk operations, etc. Components that can prevent the System-on-a-Chip (SoC) from returning to OSIX are known as "activators" (requesters or blockers) because they are registered in the power manager as processes that can block the transition to the idle state.

The duration of these active periods is highly variable and is controlled to avoid negatively impacting battery life. Tools like SleepStudy , integrated into Windows, or the ETW trace system allow you to see which components keep the computer awake and for how long, which is key to diagnosing unusual power consumption in Modern Standby.

Real problems: excessive power consumption and laptops that don't "sleep"

On paper, Modern Standby should improve the user experience and reduce power consumption while idle. However, its practical implementation leaves much to be desired on many devices. Cases have been documented where a laptop that consumed around 2W in standby mode (S3) ends up consuming three, five, or even ten times more power in Modern Standby.

In tests with models like the Dell XPS 15, ASUS ZenBook, and Lenovo IdeaPad, power consumption in "standby" mode exceeded 27W with the lid closed, and surface temperatures reached around 50°C . This means the laptop is technically in Modern Standby, but its actual state is more like being on but barely used than a low-power sleep mode.

The consequence for the user is obvious: the device can sit in a hot backpack for hours, the battery drains rapidly, and you risk losing everything you had open if the system runs out of power before you turn it back on. Similar complaints have been circulating for years regarding Microsoft Surface devices and laptops from various brands.

Part of the problem is that Modern Standby replaces S3 mode on many devices . Users no longer have the option to select "classic sleep" in the power settings; clicking "Sleep" automatically enters S0ix. There are hacks to try and force S3 through the registry or advanced settings, but several users have reported that their devices then fail to wake correctly or become unstable.

As a compromise, some users choose to always force hibernation in the power plan, so that when the lid is closed or the power button is pressed, the system saves its state to disk and actually shuts down . This is slower when resuming work, but it guarantees almost zero power consumption and avoids battery drain issues.

The situation is particularly egregious on laptops that only support OS X/S2 Idle running Linux. Some users report battery drain nearing 100% overnight on machines like the Dell XPS with integrated GPUs , even after applying typical power-saving recommendations (powertop settings, disabling Bluetooth and Wi-Fi, etc.). In contrast, laptops like a MacBook Pro with Apple Silicon, featuring highly integrated hardware and operating systems, achieve idle power consumption figures below 1% per day.

Modern Standby in Linux: S0ix, S2idle and headaches

In the Linux world, Modern Standby support is even more complex. Many modern laptops, instead of offering the classic S3 sleep state, only expose S2idle (or “s2idle”) as a mem_sleep option . S2idle is essentially the equivalent of the S0ix model: the system technically remains in S0, but attempts to enter low-power states with the processor and RAM at their minimum levels.

In theory, a well-implemented S2idle should approach the power consumption of S3. In practice, if there's even a single poorly implemented controller, a device that won't enter its low-power mode, or a service that doesn't cooperate, the computer will spend the night half-awake, with the CPU constantly switching in and out of low-power states and the battery draining rapidly.

There are specific guides for checking S0ix support in Linux by analyzing, for example, ACPI tables and system behavior at rest. One of the most cited references explains how to verify if the system has actually reached the deepest S0ix states, by examining counters and internal states. These methods typically include advanced commands , reading files in /sys , and analyzing power traces.

Users of recent devices like the Dell XPS 13 or XPS 15 report that, even after following all the usual recommendations—disabling Intel VMD by changing RAID to AHCI in the BIOS, applying settings recommended by powertop , disabling wireless radios, etc.—they still see idle battery consumption of 12% per day or more, which is far from reasonable.

Given these situations, many wonder if using S2idle on current laptops is truly viable, or if it's simply due to unfortunate hardware and firmware combinations that Linux doesn't yet handle with the same finesse as Windows. Currently, the answer depends heavily on the specific model and the level of support from the manufacturer: some laptops perform well, while others have virtually no support for modern sleep mode.

How to check and enable Modern Standby in Windows

If you want to know if your computer is compatible with Modern Standby, you can use the powercfg command-line tool in Windows 10 and 11. The process is simple and requires no additional installation.

First, open the "Run" window with the shortcut WIN + R , type cmd , and press OK to open the command prompt . Once there, run the following command:

powercfg / a

The command output will show the sleep states supported by your computer. If you see something like “Standby (S0 Low Power Idle) – Network connected” or similar, it means your PC supports Modern Standby. If you only see S3 as an available sleep state, your computer uses the traditional model and does not support S0ix.

To manually enter Modern Standby, simply go to the Start menu, click the power icon, and select the Sleep option . If your hardware and drivers are compatible, the system will transition to S0ix instead of using S3. Keep in mind that if your laptop remains inactive for an extended period, Windows may automatically switch from Modern Standby to hibernation , entering an even deeper state where power consumption is almost zero, but resuming is slower.

Some manufacturers explicitly describe in their documentation that, if your laptop has Modern Standby, you may see behaviors such as music continuing to play after suspending or you continuing to receive alerts and notifications while the screen is off, something impossible with classic S3 suspend, where almost the entire system remains completely still.

Wake on LAN and Modern Standby: what changes

Another area where Modern Standby complicates things a bit is Wake on LAN (WoL) . On older S3 systems, enabling WoL basically involved enabling a few options in the BIOS and the network controller, and that was it. With S0ix, the story is more nuanced because the network adapter is part of a much more dynamic, low-power input/output system.

To wake a computer in Modern Standby remotely, you must first ensure it maintains network connectivity while at rest . On Windows, this involves going to Settings > System > Power & sleep, opening Advanced power options, and, in your active power plan, adjusting settings such as the wireless adapter's power saving mode to "Maximum performance" and enabling the "Allow network connectivity during standby" option.

Additionally, in Device Manager , under the network adapter properties, it's usually necessary to enable options like "Allow this device to wake the computer" and, if available, "Allow only one magic packet to wake the computer." This prepares the card to listen for certain traffic patterns even in the deepest S0ix states.

In practice, there are cases where these options don't even appear. Some users of compact laptops or Intel NUC -type kits find that the wake-up setting is missing from the Ethernet adapter's power management tab . In these scenarios, even if the router is correctly configured to send Wake-on-LAN (WoL) packets and the operating system supports Modern Standby, the hardware simply doesn't offer the ability to wake the computer over the network.

Alternatively, remote administration tools such as TeamViewer, AnyDesk, or similar services can be used. These maintain background processes capable of waking the system as long as it retains some connectivity in Modern Standby. Windows Remote Management (WinRM) and remote communication via PowerShell can also be used to send commands to the computer while it is in S0ix, provided the necessary services are enabled and the firewall allows it.

Another more advanced option involves creating custom services that listen on specific ports and react to certain network requests to wake the system. However, all these solutions depend on the computer actually keeping the network adapter operational in Modern Standby, which doesn't always happen depending on the combination of BIOS, drivers, and system.

When everything fits together —compatible hardware, correct drivers, adjusted settings—, it is possible to achieve very convenient behavior: the laptop asleep in Modern Standby, with very low consumption and the ability to wake up upon receiving a magic packet or a remote command, similar to an always-available home server.

At the other extreme, if the implementation is poor, you may find that WoL never works, the computer overheats at idle, or it enters loops where it continuously exits S0ix to attend to processes that never finish shutting down, with the consequent battery drain.

Modern Standby (S0ix) is another piece of the puzzle of energy saving in modern laptops. When well implemented, it can offer instant-on and ridiculously low power consumption while maintaining network functionality . However, when poorly tuned, it results in laptops that don't truly "sleep," frustrated users experiencing rapid battery drain, and, in many cases, the need to resort to hibernation or advanced settings to mitigate the problems while manufacturers and operating systems continue to refine this power model.

Related articles:

How to enable or disable battery saving mode in Windows 11 step by step

Isaac

Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.