Cannot debug with running VS2005 as administrator

[bharath_r]

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

 

[Jesper]

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?

 

[bharath_r]

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/0470101555?ie=UTF8&tag=protectyourwi-20







- Show quoted text -

Hey, thanks for the reply.

Actually, you are right. From the day i switched, i had been
installing many applications and hence was getting the elevation
message many times. Yes the 'every time i run a program' part is not
true. I was just fed up of that message popping up many times.

Regards
Bharath

 

[Jesper]

Actually, you are right. From the day i switched, i had been

installing many applications and hence was getting the elevation
message many times. Yes the 'every time i run a program' part is not
true. I was just fed up of that message popping up many times.

You should wait with passing judgement on it until you have the system
mostly configured with all the apps you want. Once you are in steady state
you shouldn't get many pop-ups.

BTW, I'm not sure it is useful for you, but I wrote a couple of tools to
elevate things more easily. Most notably, one of them elevates an instance of
Windows Explorer so you can perform multiple file operations with one prompt
(two if you are a regular user). There is more information at:
http://msinfluentials.com/blogs/jesper/archive/2008/02/14/resource-kit-done.aspx