Windows installer hangs if Batch files are set to open in a specific application (such as a text editor)

[xenago]

With batch files set at the system level to open by default in another application (such as Notepad++), the installer will hang. Instead of running the file AppData\Local\Temp\rad8A5F4, it opened it:

At this point, the install process was hung and I aborted it (presumably, a user could also run the script manually and then close whatever application was inadvertently opened, but I didn't test that).

To temporarily get around this problem, I ran this command to reset the file association, and then reran the installer successfully:

ASSOC .bat=batfile

Maybe this can be avoided by preceding the command running the batch file with call or cmd to ensure it is treated as a script rather than opening whatever the default application is for .bat extension? I think it might be this line that runs it:

edb-installers/server/scripts/windows/initcluster.vbs

Line 80 in de3a56b

DoCmd = objShell.Run(""""&objTempFolder.Path & "\" & strBatchFile & """", 0, True)