How to Remove Startup Programs From the Windows Registry

Where startup entries actually live

The registry is the master list Windows reads at every logon, and the classic autostart locations are the Run keys. One branch sits under HKEY_CURRENT_USER and holds programs that start only for you; a mirror under HKEY_LOCAL_MACHINE holds programs that start for every account; a WOW6432Node copy exists for 32-bit applications on 64-bit Windows. Each value is simply a name plus a command line — the name tells you which program it belongs to, and the Data column shows the exact executable being launched.

There is a second layer most guides miss: StartupApproved. When you disable a program in Task Manager, Windows does not delete the Run entry — it writes a binary value under Explorer\StartupApproved\Run marking the program as disabled. That is why a program can appear disabled in Task Manager yet still sit in the registry, and why deleting the Run value is the cleaner, complete removal.

• HKCU\Software\Microsoft\Windows\CurrentVersion\Run — your user's autostart; the usual home of most junk
• HKLM\Software\Microsoft\Windows\CurrentVersion\Run — machine-wide autostart; needs an administrator to edit
• HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Run — the same, for 32-bit programs on 64-bit Windows
• HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce — one-shot installer commands, usually best left alone
• HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\StartupApproved\Run — where Task Manager stores its disable switches

Removing entries safely, step by step

Press Win+R, type regedit, and open the HKCU Run key from the list above. Before deleting anything, back the key up: File > Export, save it to your desktop as a .reg file, and keep it — double-clicking that file later restores everything you removed. Then read each value in turn; when the Data column points to a program you recognize and no longer want at startup, right-click the value and delete it. Reboot afterwards and confirm that everything you rely on still launches.

Two honest warnings before you start on the HKLM branch. Some programs re-create their Run entry the next time they run, so for those the fix belongs in the program's own settings — look for an option like “run at Windows startup”. And entries from touchpad utilities, audio consoles or security suites often provide hotkeys and background protection; removing them costs you function, not just boot time. When in doubt, open Task Manager with Ctrl+Shift+Esc, go to the Startup apps tab, and click Disable instead — identical effect on boot time, fully reversible.

Keeping autostart lean

A trimmed Run key is not a one-off trophy: new installers add entries all year, so re-read Task Manager's Startup apps list every couple of months and ask of each line whether that program earned its place at boot. The impact ratings there — high, medium, low — are measured on your hardware, not guessed by the vendor. A rule of thumb that holds up: browsers, updaters and cloud-sync clients rarely need to start with Windows.

Kleaner PRO can show entries from the HKCU and HKLM Run keys and optionally check executable signatures, but it does not measure boot impact or disable entries. Use Task Manager's Startup apps page for Windows' impact estimate and for changes; export a registry backup before editing Run keys directly.

Questions and Answers

Read next

All articles · FAQ