How to Control Windows RunMRU History in Registry

This article explains the specific Windows Registry values responsible for enabling, disabling, and managing the Run dialog’s Most Recently Used (RunMRU) command history. By modifying these registry settings, you can toggle command logging, clear stored commands automatically, or completely prevent Windows from saving your Run command history.


The Primary Registry Value: Start_TrackProgs

The primary registry setting that controls whether Windows logs and saves the Run command history is Start_TrackProgs. This value corresponds to the “Let Windows track app launches to improve Start and search results” setting in Windows Settings.


Policy-Based Restriction: NoRecentDocsHistory

If you want to enforce the disabling of Run command and document history across the system via administrative policy, the NoRecentDocsHistory value is used.


Automatic Deletion on Exit: ClearRecentDocsOnExit

To allow history tracking during an active session but automatically purge the stored RunMRU list upon signing out or restarting, use ClearRecentDocsOnExit.


Where the RunMRU History Is Stored

The actual commands you type into the Run dialog box are stored individually as string values (a, b, c, etc.) alongside a MRUList string value at the following path:

Deleting the entries inside the RunMRU key (except the (Default) value) immediately clears the existing command history without changing future logging behavior.