Visual Studio Debugger appears when Print Spooler or another service crashes and waits for user input on a server

Visual Studio Debugger Appears when Print Spooler or Another Service Crashes and Waits for user Input on a Server.

Once Visual Studio is installed the default behaviour when an unhandled exception occurs is to show an Exception dialog that requires user intervention to either start Just-In-Time debugging or ignore the exception.

To configure the server to no longer show a dialog when an unhandled exception occurs (the default behavior prior to installing Visual Studio), use the registry editor to delete the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

On a 64-bit operating system also delete the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger

Your Office Anywhere offer a range of Cloud Computing services centred around our Hosted Remote Desktop platform; paid monthly and per user, hosted desktops enable access to core business applications from anywhere and on any device.

Company Registration 5135448 VAT registration 834 5840 16

Tel: 01282 500318 | Web: www.yourofficeanywhere.co.uk

www.twitter.com/yourofficeany

Your Office Anywhere, Cardium Outsourcing, Unit 4, Dominion Court, Billington Road, Burnley, Lancashire, BB11 5UB, UK.

Article ID: 132, Created: November 22, 2010 at 11:02 AM, Modified: August 7 at 11:43 AM

Visual Studio Debugger appears when Print Spooler or another service crashes and waits for user input on a server

Was this article helpful?

Share this article