Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Sometimes I forget how the exact syntax of a CMD command looks and then I would like to search my own CMD history. Clearly, within the same session, you can browse it with the up and down arrow keys but what about the history of former CMD sessions? Is there a file, a log the history gets written to or does it all go to digital Nirvana?


share|improve this question

Not natively but check out: , makes cmd.exe much more productive. Quoting features from the project page:

Powerful Bash-like line editing from GNU's Readline library.
Superior path completion (TAB).
Paste from clipboard (Ctrl-V).
Support for the completion of executables/commands, and environment variables.
Undo/Redo (Ctrl-_ or Ctrl-X, Ctrl-U)
Improved command line history.
Persists across sessions.
Searchable (Ctrl-R and Ctrl-S).
History expansion (e.g. !!, !<string>, and !$).
Scriptable completion using Lua.
share|improve this answer
clink solved everything – Okuma.Tony Jan 20 '15 at 16:27
Any plans to include it by default in Windows? :D – Jaime Hablutzel Mar 1 '15 at 22:40
Can you set a ~/.inputrc when using clink? (and do you know whether it can be used Console or anything?) – Mike H-R Apr 20 '15 at 17:39
Apparently, see the doc – Baris Demiray Dec 18 '15 at 9:29

No, Windows command prompt history can't be saved when a session ends.

share|improve this answer
for real? how do you know this? Sorry for questioning you, I guess you are right but how can u know unless u programmed the damn thing ;) – raoulsson Dec 18 '09 at 0:08
Ok, let me rephrase :-) The Windows command interpreter ("cmd.exe") doesn't provide any support for saving/exporting/keeping history, of, if it does, Microsoft didn't document it and nobody was ever able to find it. You can of course try to work around that, like Sean suggested, but there's (or does appear to be) no built-in support for this. – Massimo Dec 18 '09 at 6:17
You can press F7 to see a history list of the current session. – jftuga Feb 14 '11 at 13:20
@jftuga, Wow, just wow, how did you know that? – Pacerier Aug 23 '15 at 21:36
CURRENT session is the keyword here. – Massimo Aug 24 '15 at 5:42

Massimo is correct that your command prompt history does not persist across sessions. You could manually grab this before closing your prompt by typing doskey /history > history.txt

Or... you could use PowerShell as your CMD prompt, and follow this post to persist your history across sessions.

share|improve this answer

Command History: To enable a command history (that can be accessed using the up and down arrow keys) just execute doskey at the command prompt. For example, to create a command history of 100 elements:

doskey /listsize=100


share|improve this answer
That doesn't answer the question at all?? – Chopper3 Feb 14 '11 at 13:27

It is possible to save the current history to file,

`$ doskey /history > somefile.txt`

But it seems there is no way to load it back as history. It is possible only to use a command line argument to load and execute all lines,

cmd.exe /K somefile.txt

, what can be useful to load a list of doskey macros. This invocation could be included in a shortcut so you don't need to type it everytime; this reference has some additional info on this approach.

There is a similar question on Superuser that bring some alternatives, including clink, as suggested by @RobertBak.

share|improve this answer
Hmm, to load it back into history, wouldn't you simply need to save it to a .bat file and run it? – Pacerier Aug 23 '15 at 22:10
@Pacerier running the commands again would surely include them back in the history, but it likely would have large side-effects. Imagine that you delete some files through the shell and then recreate them outside the shell through a long and painful process. Reloading the history through your procedure would unexpectedly delete the files again. – mMontu Aug 24 '15 at 11:00

You can use clink.

Easiest way to install clink is using chocolatey. Once you install chocolatey, you can install clink by typing

choco install clink

Starting from the next time you start cmd.exe, it should store history across sessions.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.