There are three doors out of a preview build and a fourth that usually refuses to open. Here is each one honestly, with what it keeps and what it costs.
So you have decided to leave the preview build — now comes the argument everyone has: can I get back to stable Windows without starting over? Sometimes yes, sometimes no, and the answer is written in two numbers on your own PC. This page walks each exit route at full honesty, including why the tempting in-place upgrade so often turns into a clean install at the last screen.
If this preview build was installed recently — roughly within the last 10 days — Windows may still hold the previous installation and offer a rollback:
The window closes when the 10 days pass, when the previous installation folder is cleaned up, or when another build lands on top. A greyed-out Go back button is Windows telling you this door has already shut.
On the Beta and Release Preview channels, the patient exit exists: turn on Unenroll this device when the next version of Windows releases in the Insider settings, and keep working. When the next major version ships, the PC upgrades to its stable build in place — no backup-restore dance, no reinstall, everything carried across. The cost is only time: until that release, you remain on preview builds of the current version, watermark included.
Many people try the middle path: mount a stable Windows ISO and run setup, hoping to upgrade in place today. Windows setup compares build numbers, and it will not in-place upgrade to a build older than the one installed. Preview builds — above all Canary and Dev — run build numbers ahead of every stable release, so setup offers only the keep-nothing option, which is a clean install wearing a friendlier costume.
The exception proves the rule: a Release Preview or Beta PC whose build number is at or below the current stable release can sometimes take the stable ISO in place. Run winver, compare honestly, and let the numbers decide — not hope.
It is the heaviest door and the only one that is always open: any channel, any build, any expiry stage short of a dead drive. For Canary and Dev machines, it is not the last resort — it is simply the route.
Before choosing, collect the only two facts that matter: days since this build was installed (under about 10 keeps Go back alive) and your build number versus the stable release (decides the in-place door). Add your channel for the waiting door. With those three facts, the right exit is usually obvious — and if none of the gentle doors is open, the clean install is not a failure, it is the documented path.
See the watermark removal done live in the video — the registry script, the one-click tool, and the settings that matter.
▶️ Watch Full VideoThe rollback window has closed. Go back needs the previous installation to still be stored on the PC, and Windows keeps it for only about 10 days after a build upgrade — less if disk cleanup removed it or another build installed on top. After that, the remaining exits are unenrolling and waiting (Beta and Release Preview) or a clean install.
No. A PC that shipped with Windows or was upgraded legitimately holds a digital licence tied to its hardware. After a clean install of the same edition, Windows activates automatically once the PC is online — no product key needs to be typed on most modern machines.
In practice, no. Dev builds carry build numbers ahead of the stable release, and Windows setup will not in-place upgrade to an older build number — it offers only the option that keeps nothing. That is why Microsoft's documented exit from Dev and Canary is a clean install of the stable release.