2026-09-09
I Hired a Scheduled Task to Bodyguard My Desktop
I hired a scheduled task to bodyguard my desktop, and Windows took the job description literally.
Not metaphorically. Not as a cute comment in a README. As a real Task Scheduler entry named DesktopBouncer_VIP_Protection, running PowerShell hidden, LogonType S4U, RunLevel Highest, repeating every hour, whose entire moral philosophy is: if it ends in .lnk, it dies.
The script still lives at D:\run\DesktopBouncer.ps1. The velvet rope is still on the Public Desktop. The bouncer is currently Disabled, which feels correct for a club that got tired of its own door policy.
The setup was almost boring
Desktops accumulate shortcuts the way festival tote bags accumulate. Installers drop them. Updates drop them. Something called “helpful” drops them while you are rendering. You delete them. They return like bad houseguests with better permissions than you.
So on August 29, 2026, I wrote a small PowerShell rite instead of another manual purge.
Step one: plant the rope.
The script builds an ASCII sign, the full nightclub velvet energy, and writes VIP_AREA.txt into every desktop path it can find:
$env:USERPROFILE\onedrive-vm\OneDrive\Documents\Desktop$env:PUBLIC\Desktop$env:PUBLIC\Public Desktop
As of today, C:\Users\Public\Desktop\VIP_AREA.txt is still there, still announcing:
VIP AREA
DESKTOP BOUNCER ON DUTY
Only authorized files allowed beyond this point. No shortcuts allowed without explicit permission.That is not documentation. That is a threat dressed as stationery.
The turn
Then the script stops being cute and becomes policy.
It builds a scheduled task action: PowerShell.exe -NoProfile -WindowStyle Hidden with a one-liner that walks those same three desktop roots and runs Remove-Item "$_\*.lnk" -Force.
Trigger: start now, then every hour.
Settings: allow on batteries, do not stop on batteries, Hidden.
Principal: me, S4U, Highest.
Register under the VIP name. Description field, quoted from the task itself: “Keeps the desktop a VIP area by removing unauthorized shortcuts.”
Magenta console line on success: VIP Desktop Protection Enabled.
There is also a mangled Write-Host at the bottom of the script where the string quoting collapses mid-sentence ("Your desktop ost "You're the only...). Even the victory lap has a door-policy violation. I am leaving that in the record because the archive is the joke.
Highest privilege to delete shortcuts
This is the part that still makes me laugh in the kitchen.
I did not ask Task Scheduler for a gentle reminder. I asked for S4U at Highest so an hourly ghost could assassinate .lnk files on the Public Desktop while I was elsewhere, probably pretending to be a serious filmmaker.
Windows said yes.
Last successful run in the task history I could see: September 5, 2026, 9:44 PM PT, result 0. Clean kill. No drama. The kind of exit code that implies the night went fine and several shortcuts did not.
By September 9 the task shows Disabled, with a next-fire time that would have been lunch if the velvet rope were still employed. The sign remains. The bouncer went on break. The shortcuts, I assume, have started sneaking back like interns who found the badge printer.
What I was actually installing
I was not building security theater for nation-states. I was building club policy for icon litter.
The medicine under the glitter is simple. Windows will happily escalate a petty preference into a privileged recurring ritual if you ask in the right accent. Give Task Scheduler a velvet rope and it will staff the door forever, or until you remember to disable the task and live with the tote bags again.
Computer misadventures are usually about kernels, cables, and the loneliness of a blinking cursor. This one is about hiring infrastructure to enforce taste.
The transcript is a script file, a Public Desktop .txt, and a scheduled task that still knows its own job description.
If your desktop has ever grown a second rainforest of installer shortcuts overnight, you already understand the assignment.
What would your bouncer be allowed to delete?