Environment variables not used, even after reboot
I modified some environment variables (using both setx
and through the GUI: Control Panel--System Properties--Advanced--Environment Variable). The changes persist after rebooting, which I can see in the terminals, in regedit or through the GUI. But they are not picked up by powershell
, cmd
or gitbash
. Why would that be?
Here's some excerpts from powershell using the example environment variable %HOMEDRIVE%
, run immediately after rebooting:
PS H:> Get-ItemProperty Registry::HKEY_CURRENT_USEREnvironment
AWP_LOCALE182 : en-us
HOMEDRIVE : C:
...
PS H:> Get-ItemProperty "Registry::HKLMSystemCurrentControlSetControlSession ManagerEnvironment"
...
HOMEDRIVE : C:
...
PS H:> $Env:HOMEDRIVE
H:
cmd
is very similar, except that the scripts in the two answers here do successfully update the environment variables in cmd, but not for powershell or gitbash.
I have administrator privileges, but it is a work machine, so some restrictions still apply.
windows-registry environment-variables
add a comment |
I modified some environment variables (using both setx
and through the GUI: Control Panel--System Properties--Advanced--Environment Variable). The changes persist after rebooting, which I can see in the terminals, in regedit or through the GUI. But they are not picked up by powershell
, cmd
or gitbash
. Why would that be?
Here's some excerpts from powershell using the example environment variable %HOMEDRIVE%
, run immediately after rebooting:
PS H:> Get-ItemProperty Registry::HKEY_CURRENT_USEREnvironment
AWP_LOCALE182 : en-us
HOMEDRIVE : C:
...
PS H:> Get-ItemProperty "Registry::HKLMSystemCurrentControlSetControlSession ManagerEnvironment"
...
HOMEDRIVE : C:
...
PS H:> $Env:HOMEDRIVE
H:
cmd
is very similar, except that the scripts in the two answers here do successfully update the environment variables in cmd, but not for powershell or gitbash.
I have administrator privileges, but it is a work machine, so some restrictions still apply.
windows-registry environment-variables
1
%homedrive%
is a special environment variable that reflects the current user’s homedrive as specified in Active Directory. You can’t change that. If you’re trying to set a variable, use a different name.
– Appleoddity
Jan 29 at 5:13
When I open powershell, cmd or gitbash, they start in %HOMEDRIVE%%HOMEPATH%. At the moment it is a location that I never use, so my first command is alwayscd somewhere_useful
. I have never used Active Directory before - does that mean it's a setting that is managed by my network admins?
– craq
Jan 29 at 20:40
Yes. This is normal behavior.
– Appleoddity
Jan 29 at 22:38
add a comment |
I modified some environment variables (using both setx
and through the GUI: Control Panel--System Properties--Advanced--Environment Variable). The changes persist after rebooting, which I can see in the terminals, in regedit or through the GUI. But they are not picked up by powershell
, cmd
or gitbash
. Why would that be?
Here's some excerpts from powershell using the example environment variable %HOMEDRIVE%
, run immediately after rebooting:
PS H:> Get-ItemProperty Registry::HKEY_CURRENT_USEREnvironment
AWP_LOCALE182 : en-us
HOMEDRIVE : C:
...
PS H:> Get-ItemProperty "Registry::HKLMSystemCurrentControlSetControlSession ManagerEnvironment"
...
HOMEDRIVE : C:
...
PS H:> $Env:HOMEDRIVE
H:
cmd
is very similar, except that the scripts in the two answers here do successfully update the environment variables in cmd, but not for powershell or gitbash.
I have administrator privileges, but it is a work machine, so some restrictions still apply.
windows-registry environment-variables
I modified some environment variables (using both setx
and through the GUI: Control Panel--System Properties--Advanced--Environment Variable). The changes persist after rebooting, which I can see in the terminals, in regedit or through the GUI. But they are not picked up by powershell
, cmd
or gitbash
. Why would that be?
Here's some excerpts from powershell using the example environment variable %HOMEDRIVE%
, run immediately after rebooting:
PS H:> Get-ItemProperty Registry::HKEY_CURRENT_USEREnvironment
AWP_LOCALE182 : en-us
HOMEDRIVE : C:
...
PS H:> Get-ItemProperty "Registry::HKLMSystemCurrentControlSetControlSession ManagerEnvironment"
...
HOMEDRIVE : C:
...
PS H:> $Env:HOMEDRIVE
H:
cmd
is very similar, except that the scripts in the two answers here do successfully update the environment variables in cmd, but not for powershell or gitbash.
I have administrator privileges, but it is a work machine, so some restrictions still apply.
windows-registry environment-variables
windows-registry environment-variables
asked Jan 29 at 2:13
craqcraq
1013
1013
1
%homedrive%
is a special environment variable that reflects the current user’s homedrive as specified in Active Directory. You can’t change that. If you’re trying to set a variable, use a different name.
– Appleoddity
Jan 29 at 5:13
When I open powershell, cmd or gitbash, they start in %HOMEDRIVE%%HOMEPATH%. At the moment it is a location that I never use, so my first command is alwayscd somewhere_useful
. I have never used Active Directory before - does that mean it's a setting that is managed by my network admins?
– craq
Jan 29 at 20:40
Yes. This is normal behavior.
– Appleoddity
Jan 29 at 22:38
add a comment |
1
%homedrive%
is a special environment variable that reflects the current user’s homedrive as specified in Active Directory. You can’t change that. If you’re trying to set a variable, use a different name.
– Appleoddity
Jan 29 at 5:13
When I open powershell, cmd or gitbash, they start in %HOMEDRIVE%%HOMEPATH%. At the moment it is a location that I never use, so my first command is alwayscd somewhere_useful
. I have never used Active Directory before - does that mean it's a setting that is managed by my network admins?
– craq
Jan 29 at 20:40
Yes. This is normal behavior.
– Appleoddity
Jan 29 at 22:38
1
1
%homedrive%
is a special environment variable that reflects the current user’s homedrive as specified in Active Directory. You can’t change that. If you’re trying to set a variable, use a different name.– Appleoddity
Jan 29 at 5:13
%homedrive%
is a special environment variable that reflects the current user’s homedrive as specified in Active Directory. You can’t change that. If you’re trying to set a variable, use a different name.– Appleoddity
Jan 29 at 5:13
When I open powershell, cmd or gitbash, they start in %HOMEDRIVE%%HOMEPATH%. At the moment it is a location that I never use, so my first command is always
cd somewhere_useful
. I have never used Active Directory before - does that mean it's a setting that is managed by my network admins?– craq
Jan 29 at 20:40
When I open powershell, cmd or gitbash, they start in %HOMEDRIVE%%HOMEPATH%. At the moment it is a location that I never use, so my first command is always
cd somewhere_useful
. I have never used Active Directory before - does that mean it's a setting that is managed by my network admins?– craq
Jan 29 at 20:40
Yes. This is normal behavior.
– Appleoddity
Jan 29 at 22:38
Yes. This is normal behavior.
– Appleoddity
Jan 29 at 22:38
add a comment |
0
active
oldest
votes
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399482%2fenvironment-variables-not-used-even-after-reboot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399482%2fenvironment-variables-not-used-even-after-reboot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
%homedrive%
is a special environment variable that reflects the current user’s homedrive as specified in Active Directory. You can’t change that. If you’re trying to set a variable, use a different name.– Appleoddity
Jan 29 at 5:13
When I open powershell, cmd or gitbash, they start in %HOMEDRIVE%%HOMEPATH%. At the moment it is a location that I never use, so my first command is always
cd somewhere_useful
. I have never used Active Directory before - does that mean it's a setting that is managed by my network admins?– craq
Jan 29 at 20:40
Yes. This is normal behavior.
– Appleoddity
Jan 29 at 22:38