The second part of this is UAC related. Under UAC, even though you are a
member of the Administrators group, the SID for that group and the related
privileges are not in your token unless you elevate (Run as administrator...).
There only way to get around that for debugging applications running as
other users is the obvious: elevate the debugger. The old trick of granting a
non-privileged account SeDebugPrivilege no longer works because UAC will
strip that privilege from your token, regardless of how you received it.
As for your first question, I am not sure exactly what you mean by "every
time I run a program I am asked whether I want to continue." Are these UAC
prompts? If so, the "every time I run a program part" can't possibly be true.
The only reason those prompts would occur is if (a) the program is an
installer, (b) the program is designed to ask for elevation, or (c) you have
configured the program to run as an administrator. That should only be true
for a very small fraction of the programs you run. Could you please give more
details on what you mean by that claim, and which programs this happens with?
---
Your question may already be answered in Windows Vista Security:
http://www.amazon.com/gp/product/047...otectyourwi-20
"bharath_r" wrote:
> Hi all,
>
> I am new to windows vista. I shifted from xp to vista only a few days
> back. One strange thing i have noticed is every time i try to run a
> program i am asked whether i want to continue. The other thing is that
> if i do not start VS2005 by saying 'run as administrator' i am not
> able to debug my programs. I cannot debug ISAPI dlls, i cannot attach
> to processes, although i am logged into my machine as administrator. I
> there a way around this?
>
> Thanks
> Bharath
>
>