Sorry, this is just a pet peeve of mine. I keep reading “DOS prompt” everywhere, even in academic literature, when people are actually referring to the Windows command prompt.
Now, historically, yes, it once was a DOS prompt. But this was back in the days that Windows was still built on top of DOS itself. We are talking Windows 9x and earlier 16-bit versions of Windows. Windows NT has always had the “command prompt”, the cmd.exe process. Microsoft never referred to it as a DOS prompt, because it simply wasn’t.
What the command prompt was, and still is, is just that: a command line interpreter. Not all CLI’s are DOS. There are plenty of OSes out there that use a CLI. DOS was not the first, and not the only one. So, Windows also has its own CLI. Yes, it is similar to DOS (then again, in a way, they’re all similar. They all carry traits from early CLIs from UNIX and CP/M). But no, it is NOT DOS.
In 32-bit versions of NT, you could run DOS applications. In fact, you could even run the REAL DOS command prompt (which is command.com, not cmd.exe) inside Windows NT. However, these DOS processes would be started inside the NTVDM, the 16-bit virtual machine for DOS and Win16 programs. The NT command prompt is a native 32-bit Windows program, and does not use NTVDM. The NTVDM is not started until you invoke a DOS program from the command prompt (and like cmd.exe itself, not all Win32 programs are GUI-based, there are plenty of native Win32 command line tools as well).
Now, with 64-bit versions of Windows, there is no NTVDM anymore. Therefore, you can no longer run DOS programs at all. Not even from the Windows command prompt. The only way to run DOS programs on a 64-bit version of Windows is to use an emulator, such as Dosbox. So you see how silly it is to refer to the Windows command prompt as a DOS prompt in this day and age?