[Looking for Charlie's main web site?]

Saving windows command prompt history to a file

Do you find yourself working at the Windows (DOS) command prompt window (aka Start>Run>cmd), and after having entered many commands, wish you could save them to a file, such as before closing the window or perhaps when needing to restart?

This is a bit of esoterica, but as I've seen some searching for a solution in various help forums, I figured I'd share it here. It can be especially useful if you've been using the Microsoft LogParser command-line tool, which allows you to use SQL statements from the command line to analyze log files of all sorts. You may build up a large set of them during a session, and wish you could save them off before closing the command prompt window.

Quick Answer:

doskey /history > commands.log


This solution and its meaning will be old hat to some, but it seems to be a revelation to others (judging by how many I found searching for a solution to this challenge, and not being offered any useful answer).

Using the Command History

First, some may know that you can recall past commands on the command prompt (to re-execute them) using the up arrow. You can also "see" a list of the past commands (to choose from them, to re-execute) using f7. But that old-school dos popup can't be edited or saved in any way.

Well, all this command-line history goodness is really driven by a command that's executed implicitly when you open a command prompt window, called DOSKEY.

And if you enter doskey /?, you get some available help (including reminders of the shortcut keys above, and more). But you will see that it has the /history argument I've used, and that lists (to the screen) all the past commands you've entered during the current command prompt session.

Of course, from there, if the list is small enough to appear all on screen, you can just copy/paste the stuff to some file (if you know how to copy content from/to the command window), but if it scrolls off screen, that's where the command I offered is most handy (yes, I know about the "more" command to cause paging of DOS command output, but really, I'd sooner use the one command above then doing a copy, then page forward, and copy. To each his own.)

Piping the history to a file

So saving the displayed history to a file just involves a little more old-school DOS trickeration, whereby you can redirect the output of any command to a file, using the ">" argument, and naming the file to hold the output. The named file will be created in the current directory (indicated in the command prompt window).

Beware, though, that that command will overwrite any previous content in that file. If you want to append to it, instead, use ">>" in the command above. This could be useful if you, for instance, wanted to always write the log to some file, such as in your drive root, so it would become:

doskey /history >> \commands.log

Just be really careful you don't forget those two brackets, or you'll lose what you have!

I instead write it to a file (not worrying where it is), then open it and save that off to evernote. (There may even be some trick to route the save directly to evernote, but I don't know that.)

More on Doskey and command prompt power

For more info on fun with this command prompt doskey and related features, see these docs, which while for XP are good for Vista/Windows 7 (I couldn't find the same content in a more updated page at Microsoft.)

Hope that helps someone. (Just couldn't fit it in a tweet. Darn!)

Hey Charlie,

Thanks for the great post. How would I do this automatically at the end of each command session? I'm concerned about malware being installed via the command line and want to see a cumulative history for forensic purposes.

# Posted By Kevin | 2/14/11 2:04 PM
Kevin, as for causing an automatic dump of the commands at the close of a command window, there may well be a way to do it but I'm not aware of any. Sorry I can't help more there.
# Posted By Charlie Arehart | 2/15/11 11:54 AM
Very nice sir! I am used to being on Linux at home and I usually set my history to an amount that I am assured I wont lose what I want and since it saves my history when the terminal is closed I never thought of piping this to a file. If I can't have it just retain the history after the session is closed this is the next best thing. Thank you.
# Posted By Josh | 2/22/11 4:15 PM
Hi Charlie, I run an interactive JAVA program on the DOS and want to backup the whole interaction in a text file. For instance in ORACLE SQL PLUS prompt, you get everything spooled, when spooling. Commands as well as the output. Is there a way to achieve it in DOS ?

# Posted By Sat | 9/17/11 10:41 AM
Skt, I can't imagine how that may be possible, no. Well let me put it this way: I don't see it connecting to the focus of this entry (tracking history of the command prompt). Instead, for your need I'd think you'd have to hope the tool had some way to log things itself.
# Posted By Charlie Arehart | 9/17/11 12:07 PM
Tried using schtasks to record the history, the problem is that it spawns a brand new doskey command, so it doesn't actually get the command history of the original command prompt. I guess just leave your windows open and run Charlie's cool command, run a keystroke logger, or poke around some more...
# Posted By Scott Lucas | 3/21/12 12:59 PM
Maybe I'll try powershell too...
# Posted By Scott Lucas | 3/21/12 1:01 PM
Try using
doskey /history | clip

The clip command puts it onto your clipboard, which them could be pasted into an editor (handy if you keep the editor open all the time)
# Posted By taybill | 9/20/12 7:15 PM
Very cool. Thanks for that, taybill.
# Posted By Charlie Arehart | 9/20/12 7:23 PM
Thank you very much, I was searching for this. :)
# Posted By NITIN HARANE | 10/30/12 5:07 AM
cool. thank you.
# Posted By Arun | 11/15/12 12:11 PM
Thanks much.
# Posted By samwel | 1/30/13 4:39 AM
Still helping out...two years later!! Thanks!
# Posted By John Watson | 4/17/13 4:41 PM
Any ideas on how to redirect input to dos DEBUG command without it allways locking up ? in other words regaining keyboard input instead the dos window/debug session freezes.

> DEBUG < sometypesavingfile.txt

# Posted By nick | 9/3/13 10:35 AM
@Nick, sorry. I have no idea at all. I have never used the DOS command-line DEBUG feature before.
# Posted By Charlie Arehart | 9/3/13 1:21 PM
If you're like me and start cmd.exe through a shortcut with a setup batch file (a shortcut target as something like "%windir%\system32\cmd.exe /k c:\users\cdennis\Documents\winscripts\windows_auto.bat"), try adding the following to your startup batch script (code partially taken from "http://stackoverflow..."):

DOSKEY exit=DOSKEY /HISTORY $g$g "%USERPROFILE%\cmd_history.log"$t exit $*
DOSKEY eixt=DOSKEY /HISTORY $g$g "%USERPROFILE%\cmd_history.log"$t exit $*
DOSKEY exti=DOSKEY /HISTORY $g$g "%USERPROFILE%\cmd_history.log"$t exit $*

This will cause a log file to be written (as long as you close the command line by typing the command "exit", and not using the X button on the window).

The "$g" is not documented in "doskey /?", but it's from "prompt /?". However, it seems to work.

Keep in mind that there are security considerations for such a history file.
# Posted By Chris | 1/2/14 9:55 AM
Cool tip, Chris. Thanks.
# Posted By charlie arehart | 1/3/14 5:59 PM
Thanks for this tip - have used it numerous times over the last few years.
# Posted By Mike Steber | 10/6/15 2:37 AM
This tip also served me very well until I found out about the wonderful Clink - http://mridgers.gith...
# Posted By Ronan Mullarkey | 11/5/15 6:23 AM
Interesting, Ronan. Thanks for sharing.

So in the context of my blog post, I assume what you like most about clink is that it preserves history between command line sessions? That is indeed interesting.

So are the keyboard shortcuts, and of course the similarity to Bash for those familiar with that.

While I'd want to make sure folks seeing this do know that the Windows command line does indeed already have completion (hit the tab key while typing to get it to loop through files/folders matching any initially typed letters), I notice that clink says it's "context sensitive". I assume that means it would only show suitable things in different situations, which sounds interesting.

Hope that MS may incorporate such things some day. The Windows command line has indeed evolved over the years, incorporating more and more things from others.

Anyway, hope the tip I shared may continue to serve for a long time those who ARE still using only the Windows command line. :-)
# Posted By Charlie Arehart | 11/5/15 9:13 AM
I am running Windows 8.1 and to copy the contents of the full command prompt, I simply left click inside the window, then right click, then "select all". Then press ctrl c (which is copy) , which will copy the full text into memory. Now open word pad (or any word processor). Open a new document, then do ctrl v (which is paste). Now save the file.
# Posted By Kbguy | 1/12/16 7:58 PM
Still useful and helpful after five years. Thanks, Charlie! :-)

Regards from Spain,
-- Wayfarer
# Posted By Wayfarer | 1/28/16 4:56 AM
Thanks so much, Wayne, and glad to help. (I lament that so many people pay little attention to older blog posts. Some stuff doesn't change, and old info is as valuable today as in the past.)

I'm thinking about reprising some of those key posts (and articles and presentations) from the past, to help increase the chance of people finding them (versus solely by searching). :-)
# Posted By charlie arehart | 1/28/16 1:51 PM
charlie arehart is my hero of the day:

"reprising some of those key posts (and articles and presentations) from the past, to help increase the chance of people finding them"

What a great idea m8, people like you is what makes the internet great :)
# Posted By Baurits Lertelsen | 1/31/16 12:23 AM
I've been looking for a way to log DOS console session output to a log file, much the same as you can with all and sundry SSH clients, too. I tried this solution but it only seems to store the commands you enter, not the resultant output from it.
However, I just found that you can log all session output in Powershell using the "Start-Transcript" cmdlet:

Maybe this is this best option (until something better comes along?). Another possible workaround is to install an SSH Server on your Windows box and open an SSH connection to "localhost"? (But I think that's a bit much since Powershell is already part of most Windows deployments now.)
# Posted By stevo | 10/8/16 2:53 AM
Thank you!
This is still helping people.
# Posted By batya | 7/2/17 3:30 AM
BlogCFC was created by Raymond Camden. This blog is running version 5.005. (Want to validate the html in this page?)

Carehart Logo

Managed Hosting Services provided by
Managed Dedicated Hosting