The blue screen with the spinning dots that everyone has been trapped by at the worst possible moment. Set it to freeze at 32% and walk away. It is a web page — Esc ends it, and nothing on the machine is touched.
Copy shareable link gives you a URL that opens straight into the update screen with these exact settings. Press Esc or double-click to exit. Set Freeze at to 100 if you want it to actually complete; leave it at 32 and it never will.
Most joke screens fail because the target knows immediately that something is wrong. This one works on the opposite principle: it shows something completely ordinary. Everyone has sat in front of "Working on updates, 32% complete, don't turn off your computer" — on a laptop they needed five minutes ago, before a meeting, at an airport gate. The screen carries no threat, so nobody questions it. They just wait. And then keep waiting.
That is why the Freeze at control is the important one. A counter that climbs to 100% and finishes is a mild joke. A counter that sits at 32% for eleven minutes is the whole gag, because the target's own experience tells them this is normal and they should not interrupt it.
Nothing is being updated, and nothing can be. This is a web page drawing a picture. It cannot install updates, modify Windows, access files, or continue after the tab is closed. Press Esc, double-click, or leave fullscreen and it is gone.
The prank has a natural lifespan of about two to five minutes. Past that, one of two things happens: they walk away and forget the machine entirely, which is not funny, or they force a power-off, which is genuinely bad because on a real machine that is exactly the moment an interrupted update corrupts something. Be present, let them see it, and end it yourself.
Do not run it on a machine that is doing something — a render, a download, a call, an exam. The point is the reaction, and the reaction stops being enjoyable the moment it costs someone real work.
No. It is a web page that draws the same screen. Windows is not involved, no updates are downloaded or installed, and nothing on the computer changes. Closing the tab ends it completely.
Press Esc, double-click anywhere, or leave fullscreen with F11. If the keyboard is not reachable, closing the browser tab works.
Yes — that is what the Freeze at field does. Set it to 32 and the counter climbs to 32% and stops there indefinitely. Set it to 100 if you want the update to appear to complete.
It runs in any modern browser, so yes on both, but the joke lands hardest on a Windows PC because that is the screen the target recognises. On a Mac it reads as obviously wrong.
Usually they are not stuck. Large feature updates spend long stretches on file operations that produce no visible progress, so the percentage sits still while work continues. Genuine hangs are normally caused by a corrupted update cache, insufficient disk space, or a driver that fails to migrate — clearing C:\Windows\SoftwareDistribution and rerunning is the standard first fix. A real update that has genuinely frozen usually still recovers if left for an hour.
No, and this is worth knowing before you use this prank on someone. Interrupting a genuine update while it is writing system files can leave Windows unbootable. That is the exact behaviour this prank might provoke, which is why you should end it yourself rather than let the target reach for the power button.
Follow it with the fake blue screen of death for the punchline, the boot sequence simulator to fake the restart, or the fake command prompt if you want an intrusion rather than an update. The CMD hacker prank guide covers the same joke in a real Command Prompt.