We do this by first trying to fetch its location from the registry, then PATH.
This issue is reproducible when vsscript is not in PATH or PATH is not accessible.
One use-case is with opening the program via everything on Windows 11 23H2 without admin priviledges.
It's also good practice in general to refer to the install registry keys.
arch1t3cht
commented
11 months ago
We do this by first trying to fetch its location from the registry, then PATH.
This issue is reproducible when vsscript is not in PATH or PATH is not accessible. One use-case is with opening the program via everything on Windows 11 23H2 without admin priviledges.
It's also good practice in general to refer to the install registry keys.