Subst oddity with UAC

Why is it that I have to subst drives in both a normal cmd prompt and also
an elevated cmd prompt? You'd think that a single subst in either type of
cmd prompt would become visible to the other (just as if both prompts were
running at the same privilege level)?

--
Keith

On Fri, 3 Aug 2007 23:26:52 -0600, "Keith Hill"

>Why is it that I have to subst drives in both a normal cmd prompt and also
>an elevated cmd prompt? You'd think that a single subst in either type of
>cmd prompt would become visible to the other (just as if both prompts were
>running at the same privilege level)?

Prolly the setting that takes effect when Subst is applied, is itself
split between true HKLM and the virtualized version.



>--------------- ----- ---- --- -- - - -
To one who only has a hammer,
everything looks like a nail
>--------------- ----- ---- --- -- - - -

"cquirke (MVP Windows shell/user)" <cquirkenews@nospam.mvps.org> wrote in
message news:8a79b3lu5cu6o8iko2iriihibna3oisjk2@4ax.com...
> On Fri, 3 Aug 2007 23:26:52 -0600, "Keith Hill"
>
>>Why is it that I have to subst drives in both a normal cmd prompt and also
>>an elevated cmd prompt? You'd think that a single subst in either type of
>>cmd prompt would become visible to the other (just as if both prompts were
>>running at the same privilege level)?
>
> Prolly the setting that takes effect when Subst is applied, is itself
> split between true HKLM and the virtualized version.

Nope. I tracked this down to the permissions on subst.exe getting changed
automatically somehow. Most all exes in the system32 dir allow Users to
execute them. However for subst.exe somehow got removed (along with
TrustedInstallers). Unfortunately, while I can put Users back in with
read/execute perms at some point later Users gets removed. This is very
annoying because I do development on Vista that requires the use of subst
drives. My build scripts are failing because of this.

--
Keith