It only happens when I try to execute darktable from the above batch file.
I noticed if I remove the start command, it works fine, but then I have a command prompt that launched darktable with an open window.
I rarely do batch programming anymore, but I’ve used “start” to launch windows executables like this to prevent command windows from staying open after the “real” executable launches.
I found an old post somewhere elese that said to pass a null command to start first. The batch file with this change works (darktable launches with the correct startup parameters AND the command window stays open only long enough to launch the darktable executable), but I don’t understand why.
@echo on
set files=c:\DarktableTest
start "" "%ProgramFiles%\darktable\bin\darktable" --configdir "%files%\config" --cachedir "%files%\cache" --library :memory: