Your long build is running. Windows still dims the screen.
You kicked off a deploy, a download, or a presentation rehearsal. The machine treats you like you walked away. The display sleeps. The room thinks you are done.
On macOS you would reach for caffeinate. On a locked-down Windows laptop, winget and installers are often off the table, and script files may not run at all.
Keep Windows Awake gives you a PowerShell command with the same flags you already know from macOS. Paste it into the window, set a timer or keep the display on, and stop with Ctrl+C. Nothing installs, nothing writes to disk, and a normal user session is enough.
Stay awake without begging IT for another installer.
What you get
- Familiar flags. Use -d for display, -t for a timer in seconds, -w to stop when a process exits, and -i where it matches the macOS default behavior.
- Paste-first setup. Copy the raw script from GitHub into PowerShell when file execution is blocked. Execution policy targets script files, not text you paste at the prompt, as Microsoft documents.
- Honest limits. The README explains what SetThreadExecutionState cannot override: lid close, power button, screen saver, and Group Policy session locks each have their own section in the methods guide.
- A map when IT says no. If PowerShell is in Constrained Language mode, the docs point you to Presentation Settings or power settings instead of pretending one trick fits every laptop.
- macOS and Linux pointers. A separate guide covers built-in tools on other platforms when you switch machines mid-week.
Picture a one-hour screen share
You paste the command, run caffeinate with -d and -t 3600, and the display stays on through the demo. When the hour ends, Windows returns to its normal sleep rules. No leftover service, no mystery tray app.
Ready to try it?
Open PowerShell, copy the raw script from the repo, paste, then run the command with the flags you need.
Keep exploring
- The macOS shortcuts I use daily: the built-in caffeinate habits that inspired this Windows port.







