Regression: Dynamic Refresh Rate option disappears after upgrading from Windows 11 23H2 to 24H2/25H2

Summary

Dynamic Refresh Rate (DRR) works correctly on Windows 11 23H2 on my laptop, but the option completely disappears after upgrading to Windows 11 24H2 or 25H2.

The issue is fully reproducible and occurs on a clean installation.

Hardware

Device: Lenovo ThinkBook16P Gen6 IAX(2025)

Internal Display: Lenovo OEM panel (supports variable refresh rate)

CPU: Intel Core Ultra 7 255HX

GPU: NVIDIA RTX Laptop GPU + integrated graphics

BIOS: Latest available version

Observed Behavior

Windows 11 23H2:

• Dynamic Refresh Rate option is available.
• Refresh rate can be set to Dynamic.
• Variable refresh rate works correctly.

Windows 11 24H2 / 25H2:

• Dynamic Refresh Rate option is completely missing.
• Only fixed refresh rates (60Hz / 120Hz) are available.
• Variable Refresh Rate settings appear changed.
• Same hardware, same BIOS, same display panel.

Troubleshooting Performed

• Clean installation of Windows 11 23H2
• Clean installation of Windows 11 24H2
• Clean installation of Windows 11 25H2
• Lenovo OEM graphics drivers
• Latest Intel graphics drivers
• Latest NVIDIA graphics drivers
• BIOS reset to defaults
• Windows Update completed
• Reinstalled monitor drivers

Result:

DRR works on 23H2.

DRR does not appear on 24H2 and 25H2.

Evidence

The only changed variable is the Windows version.

This suggests a possible regression in the display stack, panel capability detection, ACPI interpretation, or DRR eligibility logic introduced after Windows 11 23H2.

Expected Behavior

The Dynamic Refresh Rate option should remain available on Windows 11 24H2 and 25H2 exactly as it is on Windows 11 23H2 on the same device.

Request

Please investigate whether there were changes in DRR eligibility requirements, display stack behavior, monitor capability detection, or ACPI processing introduced after 23H2 that could cause this regression.

Because the issue is reproducible across clean installations and different driver versions, this does not appear to be a driver configuration problem.

The behavior changed only after upgrading from Windows 11 23H2 to Windows 11 24H2/25H2, suggesting a Windows-side regression.