question marks in Windows path environment

[rd25994]

In my Windows 10 PATH, that environment variable one sees by either typing "set" or "path" at a command prompt, Process Lasso has something odd, seen in the excerpt below:

Code Select Expand

C:\WINDOWS\System32\OpenSSH\;;C:\Program Files\Process Lasso\???????;C:\Program Files\Calibre2\;
Those question marks are truly the hex x3F for ASCII question mark, not some odd character my text editor can't display.

Should I edit aout the extra semicolon and those question marks?

[amandaschloss]

In my Windows 10 PATH, that environment variable one sees by either typing "set" or "path" at a command prompt, Process Lasso has something odd, seen in the excerpt below:
geometry dash lite

Code Select Expand

C:\WINDOWS\System32\OpenSSH\;;C:\Program Files\Process Lasso\???????;C:\Program Files\Calibre2\;

Those question marks are truly the hex x3F for ASCII question mark, not some odd character my text editor can't display.

Should I edit aout the extra semicolon and those question marks?

Yes, you should definitely edit out the extra semicolon and the question marks from your PATH variable.

[Jeremy Collake]

Yes, you should edit them out. It's benign, as you probably don't need Process Lasso in the path anyway, but for the sake of tidiness I'd remove them.

I'm not sure how this happened, and we don't see it in our testbeds so it's not evident that it was the result of our installer. However, we'll take a look at the code and see if we can reproduce or theorize how that may have occurred.