Windows 10: Previous commands left in title-bar of command-prompt under Windows 10

(Note: the "Windows topics" selection of "Windows settings" doesn't really fit, but seemed a less-bad fit than any of the others).


Within a command-prompt window, when you run a command, the title-bar of the window is altered to show the command being executed. For instance, if the title was MyCMD and you run DIR /S then, for the duration, the title becomes MyCMD - DIR /S. When the command finishes, the original title is restored.


Under Windows 10, under some circumstances, this restoration does not happen: the command is left in the title, even after it has finished. Running the command again adds a second copy and so on. The simplest reproduction of this is with the following two batch-files:


batch1.bat

(batch2.bat)

echo Should not be reached


batch2.bat

dir


If you run batch1, the title will change from MyCMD to MyCMD - batch1 but does not revert to the original when it returns to the command-prompt. If you run it a second time, the title becomes MyCMD - batch1 - batch1 and so on, as the following shows:





Some exploration shows that this only seems to happen when (a) the second batch-file is invoked without using CALL (i.e., so that control will not return to the original batch-file), and (b) the invocation is within parentheses (while their use in the above example is slightly artificial, the original example where I spotted this used an IF statement... something like IF condition ( batch2 ) ELSE ( ... ). Changing the first line of batch1 to either (call batch2) or batch2 will prevent the corruption of the title-bar (although the first means that control returns to batch1, which is not what was wanted).


Under Windows 7, the above works as expected (the original title is restored). Specific versions tested: Windows 10 version 10.0.17763.615 and Windows 7 version 6.1.7601.

(This can be worked-around by, for instance, changing the first line of batch1 to (call batch2 & goto :eof), but is there a "cleaner" way, or is this a "bug" in the Windows 10 command-prompt?

:)

 

command prompt will not open in safe mode with command prompt

Would I just follow the same steps within safe mode after hooking up to the other system?

 

command prompt will not open in safe mode with command prompt

I am repairing a laptop for a friend and I need to access windows in safe mode and the owner has forgotten the password to the main user. I tried logging on with the administrator profile in safe mode but it is not showing up so I was going to use command prompt in safe mode with command prompt but command prompt will not open when I boot that option. Does anyone have any hints for me to figure this out?

 

GPU-Z what command line parameter ?

Suggestion: /? (-?) and /help (-help) command-line arguments to show a list of all possible arguments in a small window. *Smile