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?

edited Jul 26 '17 at 17:52

DavidPostill♦

107k27235270

asked Jul 26 '17 at 17:46

Lone Wanderer

234

It's not an error. The system and user PATH variables are different things.

– DavidPostill♦
Jul 26 '17 at 17:54

They are, however the editor is not, that should be the same because I was editing system Path with the same editor a week ago.

– Lone Wanderer
Jul 26 '17 at 17:56

Ah. OK. Reopened.

– DavidPostill♦
Jul 26 '17 at 17:57

1

The new editor is much cleaner and organized, easier to navigate and to make changes. For example load priorities, that is why this bug is quite painful.. while this style of editor (which is inherited from windows 7) is working, it's not, great..

– Lone Wanderer
Jul 26 '17 at 18:08

1

@LoneWanderer The issue is that the first entry on your Path variable starts with a non-built-in environment variable. Move %SystemRoot%System32 (the third entry) to the front of your path, and this issue will be resolved. Note that in your first screenshot, the background dialog displays the path as %M2_HOME%..., whereas the second displays the path as C:Users.... That indicates that USERPROFILE is a built-in Windows environment variable, but M2_HOME is not (This can be verified by observing USERPROFILE isn't listed in HKCUEnvironment). See my answer for more details.

– Jeff G
Dec 12 '17 at 1:08

|
show 4 more comments

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?

edited Jul 26 '17 at 17:52

DavidPostill♦

107k27235270

asked Jul 26 '17 at 17:46

Lone Wanderer

234

It's not an error. The system and user PATH variables are different things.

– DavidPostill♦
Jul 26 '17 at 17:54

They are, however the editor is not, that should be the same because I was editing system Path with the same editor a week ago.

– Lone Wanderer
Jul 26 '17 at 17:56

Ah. OK. Reopened.

– DavidPostill♦
Jul 26 '17 at 17:57

1

The new editor is much cleaner and organized, easier to navigate and to make changes. For example load priorities, that is why this bug is quite painful.. while this style of editor (which is inherited from windows 7) is working, it's not, great..

– Lone Wanderer
Jul 26 '17 at 18:08

1

@LoneWanderer The issue is that the first entry on your Path variable starts with a non-built-in environment variable. Move %SystemRoot%System32 (the third entry) to the front of your path, and this issue will be resolved. Note that in your first screenshot, the background dialog displays the path as %M2_HOME%..., whereas the second displays the path as C:Users.... That indicates that USERPROFILE is a built-in Windows environment variable, but M2_HOME is not (This can be verified by observing USERPROFILE isn't listed in HKCUEnvironment). See my answer for more details.

– Jeff G
Dec 12 '17 at 1:08

|
show 4 more comments

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?

edited Jul 26 '17 at 17:52

DavidPostill♦

107k27235270

asked Jul 26 '17 at 17:46

Lone Wanderer

234

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?

windows-10 environment-variables path

edited Jul 26 '17 at 17:52

DavidPostill♦

107k27235270

asked Jul 26 '17 at 17:46

Lone Wanderer

234

edited Jul 26 '17 at 17:52

DavidPostill♦

107k27235270

asked Jul 26 '17 at 17:46

Lone Wanderer

234

edited Jul 26 '17 at 17:52

DavidPostill♦

107k27235270

edited Jul 26 '17 at 17:52

DavidPostill♦

107k27235270

edited Jul 26 '17 at 17:52

DavidPostill♦

107k27235270

asked Jul 26 '17 at 17:46

Lone Wanderer

234

asked Jul 26 '17 at 17:46

Lone Wanderer

234

asked Jul 26 '17 at 17:46

Lone Wanderer

234

It's not an error. The system and user PATH variables are different things.

– DavidPostill♦
Jul 26 '17 at 17:54

They are, however the editor is not, that should be the same because I was editing system Path with the same editor a week ago.

– Lone Wanderer
Jul 26 '17 at 17:56

Ah. OK. Reopened.

– DavidPostill♦
Jul 26 '17 at 17:57

1

The new editor is much cleaner and organized, easier to navigate and to make changes. For example load priorities, that is why this bug is quite painful.. while this style of editor (which is inherited from windows 7) is working, it's not, great..

– Lone Wanderer
Jul 26 '17 at 18:08

1

@LoneWanderer The issue is that the first entry on your Path variable starts with a non-built-in environment variable. Move %SystemRoot%System32 (the third entry) to the front of your path, and this issue will be resolved. Note that in your first screenshot, the background dialog displays the path as %M2_HOME%..., whereas the second displays the path as C:Users.... That indicates that USERPROFILE is a built-in Windows environment variable, but M2_HOME is not (This can be verified by observing USERPROFILE isn't listed in HKCUEnvironment). See my answer for more details.

– Jeff G
Dec 12 '17 at 1:08

|
show 4 more comments

It's not an error. The system and user PATH variables are different things.

– DavidPostill♦
Jul 26 '17 at 17:54

They are, however the editor is not, that should be the same because I was editing system Path with the same editor a week ago.

– Lone Wanderer
Jul 26 '17 at 17:56

Ah. OK. Reopened.

– DavidPostill♦
Jul 26 '17 at 17:57

1

The new editor is much cleaner and organized, easier to navigate and to make changes. For example load priorities, that is why this bug is quite painful.. while this style of editor (which is inherited from windows 7) is working, it's not, great..

– Lone Wanderer
Jul 26 '17 at 18:08

1

@LoneWanderer The issue is that the first entry on your Path variable starts with a non-built-in environment variable. Move %SystemRoot%System32 (the third entry) to the front of your path, and this issue will be resolved. Note that in your first screenshot, the background dialog displays the path as %M2_HOME%..., whereas the second displays the path as C:Users.... That indicates that USERPROFILE is a built-in Windows environment variable, but M2_HOME is not (This can be verified by observing USERPROFILE isn't listed in HKCUEnvironment). See my answer for more details.

– Jeff G
Dec 12 '17 at 1:08

It's not an error. The system and user PATH variables are different things.

– DavidPostill♦
Jul 26 '17 at 17:54

They are, however the editor is not, that should be the same because I was editing system Path with the same editor a week ago.

– Lone Wanderer
Jul 26 '17 at 17:56

Ah. OK. Reopened.

– DavidPostill♦
Jul 26 '17 at 17:57

The new editor is much cleaner and organized, easier to navigate and to make changes. For example load priorities, that is why this bug is quite painful.. while this style of editor (which is inherited from windows 7) is working, it's not, great..

– Lone Wanderer
Jul 26 '17 at 18:08

@LoneWanderer The issue is that the first entry on your Path variable starts with a non-built-in environment variable. Move %SystemRoot%System32 (the third entry) to the front of your path, and this issue will be resolved. Note that in your first screenshot, the background dialog displays the path as %M2_HOME%..., whereas the second displays the path as C:Users.... That indicates that USERPROFILE is a built-in Windows environment variable, but M2_HOME is not (This can be verified by observing USERPROFILE isn't listed in HKCUEnvironment). See my answer for more details.

– Jeff G
Dec 12 '17 at 1:08

|
show 4 more comments

1 Answer
1

active

oldest

votes

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%somesubdir;...). 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%somesubdir;..., 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.

answered Dec 12 '17 at 0:59

Jeff G

178211

1

Note that this issue has been resolved by Microsoft.

– Jeff G
Jul 13 '18 at 15:49

Jeff G, I still have that problem. How can I get that fix from Microsoft?

– Holger
Jan 22 at 15:25

Unfortunately, I'm not exactly certain when this fix was rolled out. What I do know is that this symptom is no longer occurring on any of my machines, which are Windows 10 Enterprise 1709 build 16299.904, and Windows 10 Professional 1703 build 15063.1029. Is your system up-to-date? What is your Windows version/OS build #?

– Jeff G
Jan 22 at 20:33

I currently use Windows 10 Professional 1809 build 11763.253. Your trick with not starting the Path with a non-built-in environment variable worked, but was actually required.

– Holger
Jan 23 at 15:24

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1234742%2fpath-enviroment-variable-editor-bug%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

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

answered Dec 12 '17 at 0:59

Jeff G

178211

1

Note that this issue has been resolved by Microsoft.

– Jeff G
Jul 13 '18 at 15:49

Jeff G, I still have that problem. How can I get that fix from Microsoft?

– Holger
Jan 22 at 15:25

Unfortunately, I'm not exactly certain when this fix was rolled out. What I do know is that this symptom is no longer occurring on any of my machines, which are Windows 10 Enterprise 1709 build 16299.904, and Windows 10 Professional 1703 build 15063.1029. Is your system up-to-date? What is your Windows version/OS build #?

– Jeff G
Jan 22 at 20:33

I currently use Windows 10 Professional 1809 build 11763.253. Your trick with not starting the Path with a non-built-in environment variable worked, but was actually required.

– Holger
Jan 23 at 15:24

add a comment |

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

answered Dec 12 '17 at 0:59

Jeff G

178211

1

Note that this issue has been resolved by Microsoft.

– Jeff G
Jul 13 '18 at 15:49

Jeff G, I still have that problem. How can I get that fix from Microsoft?

– Holger
Jan 22 at 15:25

Unfortunately, I'm not exactly certain when this fix was rolled out. What I do know is that this symptom is no longer occurring on any of my machines, which are Windows 10 Enterprise 1709 build 16299.904, and Windows 10 Professional 1703 build 15063.1029. Is your system up-to-date? What is your Windows version/OS build #?

– Jeff G
Jan 22 at 20:33

I currently use Windows 10 Professional 1809 build 11763.253. Your trick with not starting the Path with a non-built-in environment variable worked, but was actually required.

– Holger
Jan 23 at 15:24

add a comment |

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

answered Dec 12 '17 at 0:59

Jeff G

178211

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

answered Dec 12 '17 at 0:59

Jeff G

178211

answered Dec 12 '17 at 0:59

Jeff G

178211

answered Dec 12 '17 at 0:59

Jeff G

178211

answered Dec 12 '17 at 0:59

Jeff G

178211

1

Note that this issue has been resolved by Microsoft.

– Jeff G
Jul 13 '18 at 15:49

Jeff G, I still have that problem. How can I get that fix from Microsoft?

– Holger
Jan 22 at 15:25

Unfortunately, I'm not exactly certain when this fix was rolled out. What I do know is that this symptom is no longer occurring on any of my machines, which are Windows 10 Enterprise 1709 build 16299.904, and Windows 10 Professional 1703 build 15063.1029. Is your system up-to-date? What is your Windows version/OS build #?

– Jeff G
Jan 22 at 20:33

I currently use Windows 10 Professional 1809 build 11763.253. Your trick with not starting the Path with a non-built-in environment variable worked, but was actually required.

– Holger
Jan 23 at 15:24

add a comment |

1

Note that this issue has been resolved by Microsoft.

– Jeff G
Jul 13 '18 at 15:49

Jeff G, I still have that problem. How can I get that fix from Microsoft?

– Holger
Jan 22 at 15:25

Unfortunately, I'm not exactly certain when this fix was rolled out. What I do know is that this symptom is no longer occurring on any of my machines, which are Windows 10 Enterprise 1709 build 16299.904, and Windows 10 Professional 1703 build 15063.1029. Is your system up-to-date? What is your Windows version/OS build #?

– Jeff G
Jan 22 at 20:33

I currently use Windows 10 Professional 1809 build 11763.253. Your trick with not starting the Path with a non-built-in environment variable worked, but was actually required.

– Holger
Jan 23 at 15:24

Note that this issue has been resolved by Microsoft.

– Jeff G
Jul 13 '18 at 15:49

Jeff G, I still have that problem. How can I get that fix from Microsoft?

– Holger
Jan 22 at 15:25

Unfortunately, I'm not exactly certain when this fix was rolled out. What I do know is that this symptom is no longer occurring on any of my machines, which are Windows 10 Enterprise 1709 build 16299.904, and Windows 10 Professional 1703 build 15063.1029. Is your system up-to-date? What is your Windows version/OS build #?

– Jeff G
Jan 22 at 20:33

I currently use Windows 10 Professional 1809 build 11763.253. Your trick with not starting the Path with a non-built-in environment variable worked, but was actually required.

– Holger
Jan 23 at 15:24

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Argthtjtr