I can't seem to set %path% beyond the current cmd session anymore. I can use set to set %path%, but it doesn't stay. Changes made via System Properties -> Advanced -> Environment Variables seem to have no effect. I have a bunch of directories in there I set before via System Properties, but now I can't get rid of them or add new ones.
New: Run-Command (Dec 2, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads Nov/Dec!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Maybe there's a 255 character limit. *shrugs*
Also check:
HKEY_CURRENT_USER\Environment\PATH
and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\Path
Answer on thew charater limit is "it depends on your OS"...either 2047 or 8191 characters.
http://support.microsoft.com/kb/830473
http://msmvps.com/blogs/erikr/archive/2007/09/17/maximum-length-of-envir...
Cancer Survivors -- Remember the fight, celebrate the victory!
Help control the rugrat population -- have yourself spayed or neutered!
It seems to have (kind of) fixed itself. After a few reboots, it is set correctly. However, there is still the problem of it not changing without a reboot.
The character limit had nothing to do with it (what I wanted it to be is actually much shorter than what it was). Thanks for the keys, though.
Vintage!
I changed an environment variable via System Properties -> Advanced -> Environment Variables.
I noticed that some of the CMD sessions I started after that had the new variable, and some didn't.
It looks like the ones that don't have it were started from an application that has been running for a while (before I changed the variable), while the ones that did have the new setting were started from the start menu | Run. So I'm guessing that Explorer gives you the fresh variables, while the other program I was using to start CMD was using the environment it inherited when it was first started. Which makes sense when I think about it. Just a bit confusing the first time I saw it.
I do expect the new environment variables to show up after a reboot.
MC