After applying the tweaks, the run command history is cleared

[superspartan300]

I don't like that my Run Dialogue Box previously entered entries are cleared everytime. How do I revert back that settings so whatever I typed there remains in the history (ie. services.msc, gptedit.msc, etc)

[ItsRenjiii]

That comes from the "Disable telemetry, tracking & targeted ads" option. Besides the telemetry settings, its Regfiles/Disable_Telemetry.reg turns off app-launch tracking:

; Disable Let Windows improve Start and search results by tracking app launches
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"Start_TrackProgs"=dword:00000000

Windows only keeps the Run dialog history while app-launch tracking is on, so with this value at 0 your Run entries aren't remembered.

To get the history back without undoing the rest of the telemetry changes, turn just that one setting back on:

• Settings: Privacy & security → General → Let Windows improve Start and search results by tracking app launches → On.

• Or from a terminal (current user, no admin needed):

  reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v Start_TrackProgs /t REG_DWORD /d 1 /f

  If the Run box doesn't start remembering commands straight away, restart Explorer or sign out and back in.

Entries cleared earlier won't come back, but new ones will be kept from then on.

Two things to watch:

• If you run Win11Debloat again with Disable telemetry ticked, it sets the value back to 0. Untick it, or re-enable the setting afterwards.
• Regfiles/Undo/Enable_Telemetry.reg also restores this value (Start_TrackProgs=1), but it re-enables all the other telemetry settings too. Use it only if you want to undo the whole feature.

[superspartan300]

thanks a lot! Setting that toggle back to on did the trick! I appreciate your hard work!
PS: Speaking of disbling Telemetry, even after I applied the tweaks, I still had to disable the "Connected User Experiences & Telemetry" service myself. Is there any reason why that wasn't done automtically by the tweaks?

[ItsRenjiii]

Glad it worked!

On the service: that's by design rather than something missed. The Disable Telemetry option only writes registry settings: the AllowTelemetry=0 policy, plus the related privacy and app-tracking toggles (that's also where the Start_TrackProgs setting from your search issue came from). It never changes any Windows service. Across the whole script, the only service it touches is the Copilot AI service (WSAIFabricSvc), and only when you choose that option.

Some background on why:

• On Home and Pro, AllowTelemetry=0 is treated as "Required diagnostic data". Only Enterprise and Education honour the stricter level 0. So the policy cuts telemetry down to the minimum, and the Connected User Experiences and Telemetry service (DiagTrack) keeps running to send that minimum.
• The maintainer has said (in Disable startup of services? #560) that disabling services usually brings little benefit and can break things. Services are only considered when most users won't need them.

If you want it off, disabling it yourself is fine and is a common choice. Just know that Windows Update and feature updates can sometimes switch it back on. To undo it, set it back to Automatic in services.msc, or run this in an admin terminal:

sc config DiagTrack start= auto && sc start DiagTrack

If this answered your question, please click Mark as answer on the reply that helped (and an upvote is always appreciated). It helps other people with the same problem find the fix. Thanks!