Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

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

I'm running asynchronous command prompt commands in cmd on Windows 7 64-bit and for some reason it affects my ability to recall previous commands just after I run them; for example:

I might run something like:

start /B rmdir /Q /S .\some_massive_directory

And next I try to press the up arrow to recall the text of the previous command..but nothing this because whatever data structure is holding my commands is locked by the process I sent to the background, or is it because I am using a network mapped drive to run my command on?

share|improve this question
Works as expected here using some basic testing. When in that state, what happens when you hit "Down" once? – Ƭᴇcʜιᴇ007 Nov 5 '13 at 21:04
Nothing, that's the problem...well this is an old system which has been through quite a few system administrators and motherboards...maybe that's the issue. – leeand00 Nov 5 '13 at 21:06
Why are you using start /B? (This is not sent to the background) This uses the current window so execution will wait until executed. So you would not need the start /B. And how many cmd.exe have you open. In the settings you probably have 4 buffers for DOSKEY. When you do a start (and it is the fifth) maybe you'll loose the buffer of the last/first cmd. – Rik Nov 5 '13 at 21:12
And you can use doskey /history to see the history. So you can check if it's really empty. – Rik Nov 5 '13 at 21:15

Your Answer


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

Browse other questions tagged or ask your own question.