"Andrew McLaren" <andrew@fakeaddress.com> wrote in message
news:7527DA96-AAAA-4D01-967A-8E70540F35B6@microsoft.com...
> "Bob Butler" <noway@nospam.ever> wrote ...
>> I've tried using ImpersonateLoggedOnUser which the MS web page says
>> disables virtualization and that seems to work for a user that has admin
>> rights (running elevated or not) but not for a regular user. What am I
>> missing?
>
> Hi Bob,
>
> This is rather a stab in the dark, but ... maybe you can add a manifest to
> the EXE?
>
> As per the MSDN page on Virtualisation
> (http://msdn2.microsoft.com/en-us/library/aa965884.aspx) if the app uses a
> requestedExecutionLevel in a manifest, then Virtuliasation will be
> disabled.
>
> It looks like you're using VB6? Embedding a manifest into a VB6 app is a
> little bit of a hassle; at least setting it up the first time. There's a
> good description of the procedure, here:
>
> http://www.experts-exchange.com/Prog..._22156349.html
>
> Caveat, I haven't tried this myself ... I'm just guessing it will solve
> your problem, really (albeit, an educated guess :-).
I tried a manifest specifying "asInvoker" (external though) and it didn't
help. I'm not sure my follow-up post got through because I don't see it but
I did find the solution using ImpersonateLoggedOnUser on my own token. I
realized right after sending the original post what I'd done wrong when
testing it as a non-admin user.
I was just surprised that the virtualization works in both directions.