FileNotFoundError: [WinError 2] The system cannot find the file specified

Install & build
1

I have been unable to start the application, it seems that I am lacking the file: runConsole.py

PS E:\SALOME> python salome start -gk
runSalome running on Someones-Laptop
Searching for a free port for naming service: 2816 - OK
th. 00000033A574FA90 - Trace e:\s\salome-9.8.0\sources\kernel\src\namingservice\salome_namingservice.cxx [1351] : CORBA::SystemException: unable to contact the naming service
Traceback (most recent call last):
  File "E:\SALOME\W64\KERNEL\bin\salome\runSalome.py", line 694, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
  File "E:\SALOME\W64\KERNEL\bin\salome\runSalome.py", line 482, in startSalome
    clt=orbmodule.client(args)
  File "E:\SALOME\W64\KERNEL\bin\salome\orbmodule.py", line 56, in __init__
    self.initNS(args or {})
  File "E:\SALOME\W64\KERNEL\bin\salome\orbmodule.py", line 76, in initNS
    NamingServer(args).run()
  File "E:\SALOME\W64\KERNEL\bin\salome\server.py", line 80, in run
    pid = subprocess.Popen(command).pid
  File "E:\SALOME\W64\Python\lib\subprocess.py", line 709, in __init__
    restore_signals, start_new_session)
  File "E:\SALOME\W64\Python\lib\subprocess.py", line 997, in _execute_child
    startupinfo)
FileNotFoundError: [WinError 2] The system cannot find the file specified


--- Error during Salome launch ---

And then when I do:

E:\SALOME>python salome connect -p 2816 
Search for running instance on port 2816...
   ...found unique instance: AaronEJs-Laptop:2816
Selected instance: AaronEJs-Laptop:2816
python3: can't open file 'E:\SALOME\W64\SALOME\bin\salome\runConsole.py': [Errno 2] No such file or directory
2

Hi,
to start SALOME on windows, simply use run_salome.bat or run_salome.exe scripts. Can you try these approaches to check?
Thanks

3

Hello
Try ré installing it, and pay extra attention to you anti-virus, avast deleted several files while installing v9.8
Regards,
F.

4

Hello,
Oh, that was the first thing I did, using the command line was just so that I could do diagnostics and not have the console disappear. The error is the same though.

5

Thanks, that must have been it. Uninstalling and reinstalling with Avast disabled did the trick, even though Avast made no mention that it was blocking anything.