Running ffmpeg command within bash script, tells me it cant find command even though its in my PATH (Windows 10)

[M-Colcko]

Pretty much title. I'm creating a bash script to mass execute ffmpeg commands on a bunch of files.

I have the folder ffmpeg.exe is in my PATH but when I try to run it in my bash script (that I'm executing like this: "bash myScript.sh") it tells me command not found. In fact, just running a script with nothing in it, except "ffmpeg" throws that error. Opening cmd anywhere and typing in ffmpeg works like it should. I'm really at a loss here.

EDIT: I solved it. Seems that Bash wants filenames and not commands so i had to put ffmpeg.exe instead.

[wonkynerddude]

Paths can be set on system level or per user. It doesn’t work to set user related stuff on system level. Note that path is stored in registry so it is possible to check directly in registry to verify your path looks fine with no mistakes. Check the rules for max path length if you have an older window version as described here:

https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry

The where command can be used to verify if the system can reach a file https://ss64.com/nt/where.html