We came across another tiny bug, that only occurrs on very rare occasions.
To reproduce it, a windows system with at least two drives is necessary (one can be a USB stick). If the toolbox is on one drive, but the (arbitrary) script that is executed is on the other, the execution using the C Binary fails, because the system cannot find the binary.
The reason for this is the change directory command in the script kspaceFirstOrder3DC.m
Windows will change the directory, but since the current directory is on a different drive, the change will not take effect unless the drive is also changed.
For example, if the toolbox is on the C drive ("C:\kwave-path\") and the script (and also the active directory of matlab) is on D ("D:\scripts\"), a command "cd C:\kwave-path\" will result in the current directory still being "D:\scripts". Only an additional "C:" as a command will result in "C:\kwave-path\" becoming the active directory.
I would suggest simply adding the drive change to the command as well by extracting it from the path variable first. This is possible also by enabling the /d option of the cd command.
The background of this odd behavior seems to be that windows allows for multiple active directories (one per drive). I don't see the benefit of this, since you still have to tell it which drive should be active, but that's how it is.