What has happened to CMD in Windows 11?

Question

What has happened to CMD in Windows 11?

Knut 0

Hi.

I've tried both the versions of CMD in Windows 11, and I can't get my scripts to pause anymore. Like FFMEG running in bat.

In Windows 10 i could just double click them and they would pause.

In Windows 11 they just appear to be paused, but run in the background, no change, just visible progress not showing anymore. When I unpause they just jump forward.

1 answer

Your answer

Answer 1

MotoX80 36,401

Is your bat file executing the pause statement? And that's not working?

Here is my test.bat.

@echo Run ipconfig and look for a string in its output.
ipconfig.exe | findstr.exe 192.168.184
@echo The pause statement is next where you will need to hit some key to allow execution to continue.
pause
@echo Next use timeout to wait for 10 seconds.
@echo This window will then close.
timeout /t 10

Double clicking on it, launches a window where it executes the 2 programs and then the pause statement suspends execution until I hit a key.

User's image

After I press a key, the bat file continues to the timeout statement which does a countdown. The command prompt window then closes.

On both machines, open regedit and check this key. See if there is any difference.

HKEY_CLASSES_ROOT\batfile\shell\open\command

User's image

Knut 0 Reputation points

2024-04-05T10:58:21.1+00:00

Hi, no this is not the problem.

While ffmpeg or any other program is working in cmd I could pause the operation by pressing double clicking inside the cmd window, then it says Select in the windows pane. This haulted the operation and my cpu throttled down, you can continue the progress by pressing a key while the window is selected. Now it still says Select when I pause it and the progress "stops" visibly, but it's still working in the background. When I now continue, the progress jumps forward. So the stop/pause command doesn't work anymore, it worked fine in windows 10.
Knut 0 Reputation points

2024-04-05T11:00:26.62+00:00
MotoX80 36,401 Reputation points

2024-04-05T12:44:58.9433333+00:00
I don't know. It could be the way that ffmpeg writes to stdout. Are you using mutithreading in ffmpeg? Pause may only stop the main thread.

Try this test.bat file. It will run powershell to run a directory list and calculate how long it takes. Look at the TotalSeconds value. Pick a folder and let it run. Then run it again and pause it.

cd \windows\system32 powershell.exe -command "$s=get-date;gci -recurse;$e=get-date;new-timespan -start $s -end $e" @echo %time% pause

On my Win11 laptop I see the time increase when I select and cause it to pause.
Knut 0 Reputation points

2024-04-05T20:04:38.1433333+00:00

You are correct. FFMPEG is the culprit.
Sorry for automatically thinking it was Windows 11.
I updated FFMPEG also after installing Windows 11.
I've tested both versions for windows on ffmpeg.org
I can pause conversions when force-using the old version in Windows 11 also.
Apparently FFMPEG has changed something.
Thank you for making me think about this.
MotoX80 36,401 Reputation points

2024-04-05T21:22:26.8333333+00:00

I found this. If your pc has a nice new multicore cpu, ffmpeg might decide to use it. (Sounds like a "your mileage may vary situation" depending on version and frame rate.)

https://superuser.com/questions/155305/how-many-threads-does-ffmpeg-use-by-default

If ffmpeg does a "console.writeline" and you've paused the cmd window's output, then that thread will be waiting for the output to be displayed while the other threads can continue to run.

Share via

What has happened to CMD in Windows 11?

1 answer

Your answer