Can a PowerShell prank safely change several Windows display settings at once?

The most responsible approach is to get permission and use a harmless, reversible demo instead of altering someone else’s workstation. If the goal is just a delayed surprise, locking your own test machine or showing a simulated settings screen is much safer than changing system configuration or installing software.

Calling PowerShell from a batch file is common, but the batch file doesn’t make the underlying operations safer or easier. You’d need to track the original display, scaling, cursor, contrast, and language settings, then handle failures and restore everything in the correct order. Without a tested rollback script, one error could leave the machine partially modified.

Some of these changes can be scripted, but they rely on different Windows APIs and system settings rather than one simple PowerShell command. Installing a language pack may require administrative rights, downloads, and sometimes a sign-out or reboot. A prank that changes accessibility and display settings without explicit consent could easily leave someone with a difficult-to-use desktop, so it’s better tested in a disposable virtual machine or avoided on a work computer.