When using a venv, selecting the path requires the selection of a file inside the venv folder. The issue arises when the venvPath is used by the onKeyDown. The code passes the compete path (including the file portion) to the createChildProcess. This causes the script to fail to start the venv.
`2025-11-18T15:49:07.428Z INFO C:/Users/BertzCPA/gitClones/StreamDeck_Python_Automation/venv/pyvenv.cfg
2025-11-18T15:49:07.428Z INFO C:/Users/BertzCPA/gitClones/StreamDeck_Python_Automation/venv
2025-11-18T15:49:07.428Z INFO venv
2025-11-18T15:51:04.656Z INFO path to script is: C:/Users/BertzCPA/gitClones/StreamDeck_Python_Automation/automations/Engmt_File_Sync.py
2025-11-18T15:51:04.658Z INFO start reading output
2025-11-18T15:51:04.659Z ERROR Failed to start python process: spawn C:\Users\BertzCPA\gitClones\StreamDeck_Python_Automation\venv\pyvenv.cfg\Scripts\python.exe ENOENT
2025-11-18T15:51:04.659Z INFO child process exited with code -4058
`
The error line shows the pyvenv.cfg portion of the path is still there and so when it adds the \Scripts\python.exe it is not producing a valid path.
When using a venv, selecting the path requires the selection of a file inside the venv folder. The issue arises when the venvPath is used by the onKeyDown. The code passes the compete path (including the file portion) to the createChildProcess. This causes the script to fail to start the venv.
`2025-11-18T15:49:07.428Z INFO C:/Users/BertzCPA/gitClones/StreamDeck_Python_Automation/venv/pyvenv.cfg
2025-11-18T15:49:07.428Z INFO C:/Users/BertzCPA/gitClones/StreamDeck_Python_Automation/venv
2025-11-18T15:49:07.428Z INFO venv
2025-11-18T15:51:04.656Z INFO path to script is: C:/Users/BertzCPA/gitClones/StreamDeck_Python_Automation/automations/Engmt_File_Sync.py
2025-11-18T15:51:04.658Z INFO start reading output
2025-11-18T15:51:04.659Z ERROR Failed to start python process: spawn C:\Users\BertzCPA\gitClones\StreamDeck_Python_Automation\venv\pyvenv.cfg\Scripts\python.exe ENOENT
2025-11-18T15:51:04.659Z INFO child process exited with code -4058
`
The error line shows the pyvenv.cfg portion of the path is still there and so when it adds the \Scripts\python.exe it is not producing a valid path.