Output (stderr) can't be redirected in powershell

[KeinNiemand]

Summary of the bug:
Trying to redirect the output of ffmpeg (stderr) to a file in powershell results and an empty file. Doing the same thing in cmd sucefully redirects the output to a file.
This problem does not occur in older versions of FFMPEG (7.1.3)
How to reproduce:

ffmpeg 2> test.txt
ffmpeg version N-99959-g09f1d15ae8 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 9.3-win32 (GCC) 20200320

test.txt is empty when running this in powershell

Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker.

[Carl Eugen Hoyos]

There is no version 7.1.3 and it is unlikely that the console output looks like the one you posted. Sorry

[KeinNiemand]

That's becouse there is no console output since I'm triying to Redirect the output but I only get an empty file as as an output. Sorry for using the wrong formating and making it look like there was a console output.
This is the old build a I was using that did NOT have the problem (it's no longer online outside of web archive) with this build I can redirect the output to a file (the output in the file is just the error Message for not specifiying any input): ​https://web.archive.org/web/20190426212558/https://ffmpeg.zeranoe.com/builds/win64/shared/ffmpeg-4.1.3-win64-shared.zip
This is called version 4.1.3 don't know if has another name or something but clearly there is a version 4.1.3
Both the latest realease build from gyan.dev (4.3.1) and latest dev build from BtBn (ffmpeg-N-99959) do have the issue with them it just creates an empty file with no output whatsoever when trying to redirect output in powershell.
I hope this is enough information do I need to try every version to find out which version this firt happend in or build it myself or something?

[Elon Musk]

Not our bug. Please refrain from reopening this ticket.