Visual Studio Developer Center > Visual Studio Forums > Visual Studio Debugger > Turning off Attach Security Warning popup
Ask a questionAsk a question
 

AnswerTurning off Attach Security Warning popup

  • Friday, February 10, 2006 6:58 PMSuperStruct Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I did a hard drive format a few days ago and had to reinstall VS2k5. Now I am getting a very annoying Attach Security Warning popup every time I go into Debug->Attach To Process and attach to the DLL I am working with.

    I have checked MSDN and came across this link:

    http://msdn2.microsoft.com/en-us/library/ms241736.aspx

    It says that there is a registry value that needs to be switched off, but doesn't tell what that registry value is.

    How do I turn off this popup?

Answers

  • Wednesday, January 30, 2008 7:38 PMGatoCat Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    I might be onto something here, SuperStruct.  Look at this key:
    HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Debugger
    It has a dword value named DisableAttachSecurityWarning, with a value of 0.  That's bound to be it.  Now if we can just figure out what value to plug in instead of 0... I've already tried 1, that didn't do it.

    I also found the same setting for VS2005, at
    HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Debugger
    so I set it to 1 too, just in case it was somehow overriding the other.  Still no luck.  If you play with this and find the right value, please post it here.

    Corrrecting that:  1 does work.  Somehow it didn't take the first time, and was still zero.

     SuperStruct wrote:

    My company redid their networking recently and I'm part of a different user group now. I tried my steps and added everyone who logs into my computer and I still get the popup. It worked fine on the old network for some reason. If anyone could post that registry key tweak we'd all be very grateful! I feel like I'm running Vista with that annoying popup creeping up every time I have to debug.

  • Friday, February 10, 2006 10:38 PMSuperStruct Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    OK! Here's the detailed solution! Go to this admin screen:

    Control Panel->Administrative Tools->Local Security Policy->Security Settings->Local Policies->User Rights Assignment->Debug Programs

    Double-click debug programs and add your user to the list!

All Replies

  • Friday, February 10, 2006 7:51 PMVipul Patel - CLRMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Add your self to the Debugger Users group and see. That should solve the problem.
  • Friday, February 10, 2006 10:38 PMSuperStruct Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    OK! Here's the detailed solution! Go to this admin screen:

    Control Panel->Administrative Tools->Local Security Policy->Security Settings->Local Policies->User Rights Assignment->Debug Programs

    Double-click debug programs and add your user to the list!

  • Wednesday, January 30, 2008 5:15 PMGatoCat Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    This solution does not work for me.  I am using Visual Studio 2008 Team Suite on Windows Server 2003 with IIS 6.  I am trying to attach to the worker process w3wp.exe, whose user is the identity of the application pool for my default website.  I have added that user, myself, and Aspnet to the Debug Programs list, and also to the Debugger Users group.  And yet the message still keeps popping up.

    Does anyone know the mysterious unspecified registry setting mentioned in this article?
    http://msdn2.microsoft.com/en-us/library/ms241736.aspx

    That, or any solution that works to get rid of the warning dialog.  Thanks in advance!

     SuperStruct wrote:

    OK! Here's the detailed solution! Go to this admin screen:

    Control Panel->Administrative Tools->Local Security Policy->Security Settings->Local Policies->User Rights Assignment->Debug Programs

    Double-click debug programs and add your user to the list!

  • Wednesday, January 30, 2008 5:19 PMSuperStruct Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    My company redid their networking recently and I'm part of a different user group now. I tried my steps and added everyone who logs into my computer and I still get the popup. It worked fine on the old network for some reason. If anyone could post that registry key tweak we'd all be very grateful! I feel like I'm running Vista with that annoying popup creeping up every time I have to debug.

  • Wednesday, January 30, 2008 7:38 PMGatoCat Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    I might be onto something here, SuperStruct.  Look at this key:
    HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Debugger
    It has a dword value named DisableAttachSecurityWarning, with a value of 0.  That's bound to be it.  Now if we can just figure out what value to plug in instead of 0... I've already tried 1, that didn't do it.

    I also found the same setting for VS2005, at
    HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Debugger
    so I set it to 1 too, just in case it was somehow overriding the other.  Still no luck.  If you play with this and find the right value, please post it here.

    Corrrecting that:  1 does work.  Somehow it didn't take the first time, and was still zero.

     SuperStruct wrote:

    My company redid their networking recently and I'm part of a different user group now. I tried my steps and added everyone who logs into my computer and I still get the popup. It worked fine on the old network for some reason. If anyone could post that registry key tweak we'd all be very grateful! I feel like I'm running Vista with that annoying popup creeping up every time I have to debug.

  • Thursday, January 31, 2008 3:49 PMSuperStruct Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    FredSaw you are my hero! I've been looking for that registry key since for about 3 years! THANK YOU!
  • Thursday, November 13, 2008 2:29 PMMartinRobins Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    If you change the registry key whilst Visual Studio is running, the change will be ignored for the current session and then reset when VS is closed.
    You must therefore close VS before making the change to the registry key.
  • Friday, November 06, 2009 7:03 AMVitaliy Vol Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    GatoCat
    You are Guru! This works for me on Windows 7!!!