Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Also found in the article mentioned by Tzury, but to sum up the answers in this thread:</p> <p><strong>make sure Visual Studio is not running when changing the registry key or it will be overwritten on exit with the old value</strong></p> <p>Change (or create) the following registry key to <strong>1</strong>:</p> <p><strong>Visual Studio 2008</strong> <code>HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Debugger\DisableAttachSecurityWarning</code></p> <p><strong>Visual Studio 2010</strong> <code>HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\Debugger\DisableAttachSecurityWarning</code></p> <p><strong>Visual Studio 2012</strong> <code>HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\Debugger\DisableAttachSecurityWarning</code></p> <p><strong>Visual Studio 2013</strong> <code>HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\Debugger\DisableAttachSecurityWarning</code></p> <p><strong>Visual Studio 2015</strong> <code>HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\Debugger\DisableAttachSecurityWarning</code></p> <p>For VS2015, you might need to create the Registry Key referenced above.</p> <ol> <li>Make sure Visual Studio is not running, and open the Registry Editor.</li> <li>Navigate to <code>HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0\Debugger</code>, right-click and create a new <code>DWORD</code>: <ul> <li>Name: <code>DisableAttachSecurityWarning</code></li> <li>Value: <code>1</code>.</li> </ul></li> </ol> <p><strong>Update:</strong> If you don't want to open up regedit, save this <a href="https://gist.githubusercontent.com/zidad/418e0ac6f670f2b0e14f/raw/324cf866f6dabcf3021fd908447a430803bf6609/disable-attach-security-warning.reg" rel="noreferrer" title="disable-attach-security-warning.reg">gist</a> as a *.reg file and run it (imports the keys for all VS versions lower than VS2017). </p> <p><strong>Visual Studio 2017</strong> </p> <p>The configuration is saved in a private registry location, see this answer: <a href="https://stackoverflow.com/a/41122603/67910">https://stackoverflow.com/a/41122603/67910</a></p> <p>For <strong>VS 2017</strong>, save this <a href="https://gist.githubusercontent.com/hmoratopcs/f7461c95ccdcad7bcbc3686bd45cec84/raw/0d34eb734d088455b854d3b415abd94446dfb05d/DisableAttachSecurityWarningVS2017.ps1" rel="noreferrer" title="DisableAttachSecurityWarningVS2017.ps1">gist</a> as a *.ps1 file and run it as admin, or copy and paste the following code in a ps1 file:</p> <pre class="lang-cs prettyprint-override"><code>#IMPORTANT: Must be run as admin dir $env:LOCALAPPDATA\Microsoft\VisualStudio\15.* | % { #https://stackoverflow.com/a/41122603 New-PSDrive HKU Registry HKEY_USERS reg load 'HKU\VS2017PrivateRegistry\' $_\privateregistry.bin $BasePath='HKU:\VS2017PrivateRegistry\Software\Microsoft\VisualStudio' $keysResult=dir $BasePath $keysResult | ? {$_.Name -match '\\\d+\.\d+_[^_]+$'} | % { $keyName = $_.Name -replace 'HKEY_USERS','HKU:' New-ItemProperty -Path $keyName\Debugger -Name DisableAttachSecurityWarning -Value 1 } $keysResult.Handle.Close() [gc]::collect() reg unload 'HKU\VS2017PrivateRegistry' Remove-PSDrive HKU } </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload