failed to create process - on Windows 11 Python v3.11.3 about ck HOT 7 CLOSED

Sure @gfursin , I will share the output once I reach home

from ck.

I tried Python 3.11 on Windows 10 with/without Power Shell and it works.
Need to test it on Windows 11.

A question: how did you install Python 3.11? Also, can you please give me the exact version? Did you download and install it manually from https://www.python.org/downloads/ ?

Thanks!

from ck.

Hi @anandhu-eng.

I tried it on ASUS laptop with Windows 11 from scratch. I installed Python 3.11 (added it to Path) and then CM and everything worked fine!

So, can't reproduce your issue. One extra thing: can you please report the output of the following commands:

where cm.exe

where cmr.exe

where python.exe

echo %PATH%

Maybe there is another python in the PATH or maybe there is another program with the same name cm?

I would like to make sure that it works ...

from ck.

Hi @gfursin, I executed the commands and did find python was also installed from windows store

from ck.

Oh, I have noticed weird behavior with Python and CM when installed from the store (on Windows and MacOS). We will need to dig it further one day. In the meantime, may I ask you to install Python from here and click on "add to PATH" during installation to make it the first choice, please? Could you please then try to install and run cm with this Python installation? If it works, I will write down a note in our installation guide not to use Python from the store until we understand the problem ...
Thank you very much for your feedback!

from ck.

Hi @gfursin , im confused whether that was the problem. If another python was installed through windows store it should have been mentioned in the installed appsbut was not there. I found a convincing article in stack overflow let me share.
https://stackoverflow.com/questions/57485491/python-python3-executes-in-command-prompt-but-does-not-run-correctly

After executing the steps and reinstalling python, im able to run cm without python -m cmind

from ck.

Oh, I see. Thank you for the update. I added this fix to the installation readme.

from ck.