%ProgramFiles% resolves to "C:\Program Files (x64)" for "Local System" user

%ProgramFiles% resolves to "C:\Program Files" as a normal user but
it resolves to "C:\Program Files (x64)" as the "Local System" user.

I wonder why this is happening?

I'm using "set" to display all the environment variables. I'm using
SysInternals's
PsExec to run cmd as Local System.

JH
Tue Apr 29 18:00:10 PDT 2008

It seems that it's not a user issue. Instead it's the difference between 32
bit and 64 bit processes.
PsExec is a 32 bit app.

> %ProgramFiles% resolves to "C:\Program Files" as a normal user but
> it resolves to "C:\Program Files (x64)" as the "Local System" user.
>
> I wonder why this is happening?
>
> I'm using "set" to display all the environment variables. I'm using
> SysInternals's
> PsExec to run cmd as Local System.
>

Charlie
Tue Apr 29 18:12:04 PDT 2008

32-bit processes "see" the file system differently. I haven't used PsExec,
but if it's a 32-bit process, it's running the 32-bit version of cmd, so I'm
not surprised.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"JH" <jh_ng@newsgroup.nospam> wrote in message
news:uJvmL2lqIHA.1316@TK2MSFTNGP06.phx.gbl...
> It seems that it's not a user issue. Instead it's the difference between
> 32 bit and 64 bit processes.
> PsExec is a 32 bit app.
>
>> %ProgramFiles% resolves to "C:\Program Files" as a normal user but
>> it resolves to "C:\Program Files (x64)" as the "Local System" user.
>>
>> I wonder why this is happening?
>>
>> I'm using "set" to display all the environment variables. I'm using
>> SysInternals's
>> PsExec to run cmd as Local System.
>>
>
>