Windows 8.1 PATH env var does not evaluate locations

[Tatsujinichi]

file paths are specified in other env variables, these were not evaluated.

If this is a question about how to use NVM4W, please use stackoverflow instead.

If this is an issue regarding antivirus, make sure you search the existing issues first.

My Environment

• [ ] Windows 7 or below (not truly supported due to EOL - see wiki for details)

• [ ] Windows 8

• [x] Windows 8.1

• [ ] Windows 10

• [ ] Windows 10 IoT Core

• [ ] Windows Server 2012

• [ ] Windows Server 2012 R2

• [ ] Windows Server 2016

• [ ] My Windows installation is non-English.

I'm using NVM4W version:

• [x] 1.1.6
• [ ] 1.1.5
• [ ] 1.1.4
• [ ] 1.1.3
• [ ] 1.1.2
• [ ] 1.1.1
• [ ] Older
• [ ] OTHER (Please Specify)

I have already...

• [ ] read the README to be aware of npm gotchas & antivirus issues.
• [ ] reviewed the wiki to make sure my issue hasn't already been resolved.
• [x] verified I'm using an account with administrative privileges.
• [ ] searched the issues (open and closed) to make sure this isn't a duplicate.
• [ ] made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

• [ ] settings.txt
• [ ] proxy support (Have you tried version 1.1.0+?)
• [ ] 32 or 64 bit support (Have you tried version 1.1.3+?)
• [ ] Character escaping (Have you tried version 1.1.6+?)
• [ ] A standard shell environment (terminal/powershell)
• [ ] A non-standard shell environment (Cmder, Hyper, Cygwin, git)

Expected Behavior

Fill me in...

Actual Behavior

Fill me in...

Steps to reproduce the problem:

Fill me in...

[k-j-kleist]

Are you by any chance using Powershell?

I am noting that $env:PATH contains "%NVM_HOME%;%NVM_SYMLINK%" which of course just CMD understands but not Powershell.