The win10 power options are set to never sleep and never lock the screen, but it still happens after a while...

The described behavior, where a Windows 10 system enters sleep or locks the screen despite explicit power settings to the contrary, is a classic symptom of conflicting configuration layers overriding the user's chosen plan. The primary mechanism at play is Group Policy, either from a domain in a corporate environment or from locally applied administrative templates, which can enforce sleep and lock screen timeouts that supersede the settings accessible in the standard Control Panel or Settings app. A secondary and common culprit is an outdated, buggy, or incompatible display driver, which can incorrectly signal display idle states to the operating system, triggering a sleep event irrespective of software settings. The system's firmware (UEFI/BIOS) may also have power management settings that interact poorly with the OS, though this is less frequent.

To diagnose this, one must systematically check the effective power configuration beyond the graphical interface. Using the command prompt with administrative privileges to run `powercfg /q` against the active power plan is essential; this reveals all parameters, including any policies that may be stealthily setting `ACSettingIndex` or `DCSettingIndex` for sleep or display off to non-zero values. Concurrently, examining the lock screen behavior requires checking the screen saver settings via `secpol.msc` or `gpedit.msc` for local policy, as a policy-enabled screen saver with a "On resume, display logon screen" setting will cause a lock. For domain-joined machines, the resultant set of policy (RSOP) or specific Group Policy reports are necessary to identify the authoritative source of the override.

Resolution hinges on the identified conflict. If a Group Policy is the cause, the user typically requires administrative intervention to modify the policy object, unless they have local admin rights and the policy is applied locally. For driver-related issues, updating the display driver from the manufacturer's website, or even rolling back to a known stable version, is a key step. Additionally, executing `powercfg /requests` can reveal if any process or driver is incorrectly declaring a "display request" that would allow sleep, while `powercfg /lastwake` indicates what triggered the last wake event, offering clues to the source of the interruption. In persistent cases, creating a completely new power plan from scratch can bypass corrupted configurations in existing plans.

The implications are significant for system reliability and user experience, particularly in environments where machines must remain awake for monitoring, rendering, or network access. This issue underscores that Windows power management is a composite system where registry settings, driver behavior, and policy frameworks interact in a hierarchy. The user's configured plan is often the weakest link, easily subordinated by administrative policies or low-level hardware communication. Therefore, effective troubleshooting moves immediately from interface-level checks to forensic commands and log analysis, focusing on the discrepancy between intended configuration and the enforced operational state.