PATH environment variable hosed, and all normal files need Administrator access (??!)

[Guest Jon Davis]

Using Windows Server 2008 as a developer workstation, with all recent

updates installed.

 

If I open a command prompt (cmd.exe) as myself, the global PATH variable is

populated. But it doesn't do much good because, as a developer and power

user, I cannot do anything I'd normally do, like "defrag" because you must

run cmd.exe as Administrator.

 

If I open a command prompt "as Administrator", the global PATH variable is

NOT populated; only my profile PATH that normally gets prepended to the

global PATH is populated. I had to create a setpath.bat file and paste my

global PATH variable.

 

But that was a kludge and I'm finding normal, non-console apps not

functioning correctly, such as TortoiseSVN, and Windows Server 2008 wants to

lock practically every file so it's almost like it's behaving like it's

elevating to Administrator but losing the PATH environment variable in the

process of doing so. (Just guessing.) I have UAC disabled.

 

So I have two problems to resolve:

 

1) how do I get Administrator to behave XP-style, keeping the PATH, and

2) how do I get Windows to stop locking up my normal files as though they

need Administration permission for all modify/delete actions??!

 

Jon

[Guest Jon Davis]

Bug in Local Security Policy? (Re: PATH environment variable hosed, and all normal files need Administrator access (??!))

 

Bug in Local Security Policy? (Re: PATH environment variable hosed, and all normal files need Administrator access (??!))

 

K I fixed this by changing in Local Security Policy, "Only elevate UIAccess

applications that are installed in secure locations", setting it back to

True. Setting that to False makes the computer practically unusable as a)

EXEs like Notepad++ and TortoiseSVN don't have priviledged access to diddly,

and b) the PATH environment variable gets hosed, and those are only two of

who knows what other symptoms it produces.

 

Jon

 

 

"Jon Davis" <jon@REMOVE.ME.PLEASE.jondavis.net> wrote in message

news:4223B871-4B38-4485-930B-6033A5B01A41@microsoft.com...

> Using Windows Server 2008 as a developer workstation, with all recent

> updates installed.

>

> If I open a command prompt (cmd.exe) as myself, the global PATH variable

> is populated. But it doesn't do much good because, as a developer and

> power user, I cannot do anything I'd normally do, like "defrag" because

> you must run cmd.exe as Administrator.

>

> If I open a command prompt "as Administrator", the global PATH variable is

> NOT populated; only my profile PATH that normally gets prepended to the

> global PATH is populated. I had to create a setpath.bat file and paste my

> global PATH variable.

>

> But that was a kludge and I'm finding normal, non-console apps not

> functioning correctly, such as TortoiseSVN, and Windows Server 2008 wants

> to lock practically every file so it's almost like it's behaving like it's

> elevating to Administrator but losing the PATH environment variable in the

> process of doing so. (Just guessing.) I have UAC disabled.

>

> So I have two problems to resolve:

>

> 1) how do I get Administrator to behave XP-style, keeping the PATH, and

> 2) how do I get Windows to stop locking up my normal files as though they

> need Administration permission for all modify/delete actions??!

>

> Jon