apommel / vscode-matlab-interactive-terminal

VS Code extension allowing for an interactive Matlab terminal and launching of scripts through Matlab Engine for Python
MIT License
46 stars 9 forks source link

Terminal Process failed to launch: Native Exception (file not found) #59

Open CollinCodez opened 1 year ago

CollinCodez commented 1 year ago

When I try to open a matlab terminal, I get the error pictured below. image

I have Matlab R2022b installed (it is not on my boot drive, if that makes a difference), Python 3.8.10 is installed (was done via the microsoft windows store) and in PATH (have not entered the location into the matlab interactive terminal). I have also set up the MATLAB Engine API for Python. I can't seem to figure out what to do to make this work. Any suggestions?

alonso-herreros commented 1 year ago

Same problem here. OS: Windows 11 Home (22621.1265) VS Code version: 1.75.1 (Installed for all users) MatLab version: 2022b update 4 (9.13.0.2166757) Python version: 3.10.10 (installed through the Windows Store)

Matlab, Python, Java, and VS Code are all on the same drive and in PATH. MATLAB Engine API for Python was installed from the files in the MATLAB folder (extern\engines\python). I get the exact same error.

alonso-herreros commented 1 year ago

I managed to fix this by uninstalling the Windows Store version of Python, and then installing it the old way, using the .exe form the python downloads page (version 3.10.10, latter versions are not supported by the MATLAB Engine API apparently). I selected the installation for all users (through the "customize install" option) and then I double checked the PATH variable to make sure the correct version of python was selected. Now it works!

amansk0307 commented 1 year ago

same problem here....

amansk0307 commented 1 year ago

I managed to fix this by uninstalling the Windows Store version of Python, and then installing it the old way, using the .exe form the python downloads page (version 3.10.10, latter versions are not supported by the MATLAB Engine API apparently). I selected the installation for all users (through the "customize install" option) and then I double checked the PATH variable to make sure the correct version of python was selected. Now it works!

You're genius!!! thanks for the help