The latest articles on DEV Community by Teoman Ege Selcuk (@teoman_egeselcuk_d962da6). https://dev.to/teoman_egeselcuk_d962da6 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3427794%2F27ca7842-b5a7-45b4-8ae6-6be5cafeb3de.jpg https://dev.to/teoman_egeselcuk_d962da6 en Teoman Ege Selcuk Mon, 11 Aug 2025 17:39:07 +0000 https://dev.to/teoman_egeselcuk_d962da6/title-powershell-on-windows-11-home-how-to-cap-displaysleephibernate-at-5-minutes-300-s-7ag https://dev.to/teoman_egeselcuk_d962da6/title-powershell-on-windows-11-home-how-to-cap-displaysleephibernate-at-5-minutes-300-s-7ag <p>I can set idle timers with powercfg (e.g., 2–3 minutes for Sleep/Hibernate) on Windows 11 Home and they apply fine.</p> <p>I need to enforce a maximum of 5 minutes so users (incl. local admins) can pick shorter timeouts but not exceed 300 seconds for:</p> <p>VIDEOIDLE (Turn off display after)</p> <p>STANDBYIDLE (Sleep after)</p> <p>HIBERNATEIDLE (Hibernate after)</p> <p>Environment/limits: Win11 Home, AC/DC, no GPO/AppLocker. Browser keep-awake is already handled separately with /requestsoverride.</p> <p>Tried:</p> <p>Just writing values → can be raised later.</p> <p>A crude clamp that parses powercfg /q → unreliable with plan changes/locales.</p> <p>Looking for: A PowerShell solution (preferably a SYSTEM scheduled task) that clamps to 300 s on the active plan and survives plan switches and GUI/powercfg edits, ideally using GUIDs/APIs rather than parsing localized output. Minimal example appreciated.</p> discuss microsoft programming devops