Sunday, August 31, 2014

windows 10 - Path enviroment variable editor BUG


Windows 10 brought new PATH environment variable editor, but for some reason, it just stopped working for me.


The odd thing is that path editor is "broken" only for system variables.. in case of User variables, the editor is fine.


System editor:


enter image description here


User Path editor:


enter image description here


As you can see, both are editing Path variable, however both use different editor. This is quite infuriating, have you ever encountered such error?


Answer



I was having the exact same issue, and finally figured this out via trial-and-error. The issue is that there is a bug in the Windows 10 Path environment variable parser. In my case, the first entry in my Path environment variable started with an application-defined REG_SZ environment variable (e.g., Path was set to %MyAppPath%\some\subdir;...). From my testing, it appears that the first entry on the Path must not start with a non-built-in environment variable.


For example, if my Path environment variable were set to %SystemRoot%;%MyAppPath%\some\subdir;..., it would be editable in the Path list view editor, since SystemRoot is a built-in environment variable. If you swap the first two paths in that example, I observed the symptom you describe (that editing the Path variable results in opening the standard text editing dialog instead of the Path list editor).


To fix this issue, ensure the first entry in your Path doesn't start with a non-built-in environment variable.


No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...