BUG: Fix bug with sys_info on Windows

[larsoner]

Fixed a little bug I hit on Windows where not having permissions to call a command-line function caused a ValueError

Closes #13154

[larsoner]

Tacked on a little fix for #13154 as well, ready for review/merge from my end!

[sappelhoff]

Being on mne main, I can run mne sys_info just fine on a non-elevated powershell (i.e., I do not need this PR for it to work). Do I need to call something special to reproduce the error?

[larsoner]

Not 100% sure what needs to be done but without this change this is what I see:

CPU                  Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 cores)
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\larsoner\mne-python\1.9.0_0\Scripts\mne.exe\__main__.py", line 7, in <module>
    sys.exit(main())
             ~~~~^^
  File "C:\Users\larsoner\python\mne-python\mne\commands\utils.py", line 109, in main
    cmd.run()
    ~~~~~~~^^
  File "C:\Users\larsoner\python\mne-python\mne\commands\mne_sys_info.py", line 58, in run
    mne.sys_info(
    ~~~~~~~~~~~~^
        show_paths=options.show_paths,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<2 lines>...
        check_version=options.check_version,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "C:\Users\larsoner\python\mne-python\mne\utils\config.py", line 781, in sys_info
    total_memory = _get_total_memory()
  File "C:\Users\larsoner\python\mne-python\mne\utils\config.py", line 690, in _get_total_memory
    total_memory = int(o)
ValueError: invalid literal for int() with base 10: ". : File C:\\Users\\larsoner\\Documents\\WindowsPowerShell\\profile.ps1 cannot be loaded because running scripts is \ndisabled on this system. For more information, see about_Execution_Policies at \n

[larsoner]

These seem to have relevant info:

• https:/go.microsoft.com/fwlink/?LinkID=135170
• https://stackoverflow.com/questions/54776324/powershell-bug-execution-of-scripts-is-disabled-on-this-system

So on my machine I have:

PS> Get-ExecutionPolicy -List
        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser       Undefined
 LocalMachine       Undefined

I can confirm that setting:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine

allows things to work without this change, and

Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope LocalMachine

brings back the error above on main. So you can mess with these locally to try to replicate if you want. FWIW this is on Windows 10, if it matters.

[sappelhoff]

That makes sense, I have the ExecutionPolicy that allows things to work without this change. This is on Windows 11.