Modern Standby (S0) Fails to Enter Deep Sleep – Excessive Power Consumption and Heat Due to PDC Task Client: Windows Update Client

Dear Microsoft Support Team,

I would like to report what appears to be a serious issue with Windows Modern Standby (S0 Low Power Idle).

My laptop supports only**"Standby (S0 Low Power Idle) Network Disconnected"**, as confirmed by powercfg /a. Despite configuring all recommended power-saving settings, the system frequently fails to enter a true low-power state and instead remains active for extended periods with the display off.

The issue is consistently reported in SleepStudy/System Power reports as:

PDC Task Client: Windows Update Client

The problem is not a brief maintenance wake-up. In one recent incident, the laptop remained in a "screen off" state for more than six hours, became noticeably hot, and consumed a significant amount of battery power. Since the system was configured for Network Disconnected Modern Standby, it is unclear why Windows Update activity would require the device to remain active for such a prolonged period.

I have already performed the commonly recommended troubleshooting steps:

• Disabled wake timers.
• Disabled automatic maintenance wake-ups.
• Configured Modern Standby as Network Disconnected.
• Verified that the issue persists even when the system should not be performing active network operations.
• Confirmed through SleepStudy that the reported activator is "PDC Task Client: Windows Update Client".

My concerns are:

1. A sleeping laptop should not remain active for hours with significant heat generation.
2. Users have no meaningful control over Windows Update activity during Modern Standby.
3. The reporting does not clearly identify whether Windows Update itself is consuming power or whether another component is preventing the platform from reaching deep S0 idle states.
4. The behavior creates a risk of excessive battery drain and overheating when the device is closed and stored in a bag.

From a user perspective, this behavior makes Modern Standby significantly less reliable than traditional S3 sleep. If the operating system intentionally prevents the system from entering a true low-power state, users should be clearly informed. If this is a defect, I request that Microsoft investigate and provide a mechanism to prevent Windows Update-related PDC activity from keeping systems active for extended periods.

I would appreciate guidance on:

• How to completely prevent Windows Update from interrupting Modern Standby.
• How to identify the exact component responsible for blocking deep S0 idle residency.
• Whether Microsoft considers this behavior expected or a known issue.

Thank you for your attention to this matter.

Kind regards,

<PII removed>