I think sysnative/ should be used on 64 bit machines? Please confirm @daviwil

That is correct. Since VS Code is a 32-bit process, the 64-bit version of PowerShell has to be explicitly launched otherwise you'll get the 32-bit version. Here's the relevant code from the PowerShell extension:

https://github.com/PowerShell/vscode-powershell/blob/5b32676e9559233f8759e3b0c60583c60e70eb94/src/session.ts#L493

You can remove this line 👍

I think you'd be better off getting the major version here as os.release() may return x.y.z?

Something like this should be safe (if Node does indeed give that format):

parseInt(os.release().split('.')[0], 10) >= 10

I'm not sure if it's necessary, since I'm parsing it to a float. That means 10.2.22222 and 11.4.4444 will still be >= 10 (and 9.5.555 will not).

I'm happy to take the change - let me know what you want to do.

I think it would be best to be explicit here, parseFloat('10.2.22222') may work but it feelss dodgy to me and the behavior itself may even be undefined and only works by coincidence.

@daviwil so this is an env variable only available on 64 bit Windows? Would it be better to check process.arch instead?

I dunno, I just copied from the PowerShell extension. :-D

process.arch probably makes more sense anyway. I'll change it.

Actually, now that I'm playing around with it, process.arch is going to give you 32-bit. I think that code that I stole from @daviwil is probably the right way to do it.

Yep, that's what I had to use to figure out the true bitness of the OS.