Home Dashboard Directory Help
Search

Windows defender severely slows down debugger by Josh Luth


Status: 

Closed
 as External Help for as External


4
0
Sign in
to vote
Type: Bug
ID: 776802
Opened: 1/17/2013 8:26:22 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

When you launch your assembly using the Visual Studio Debugger and the Windows Defender service is running, it takes several minutes to launch. If you kill the defender process, the startup is reduced to seconds. Of course this depends on the size of your project, but never-the-less performance of the debugger is hampered by the Windows Defender service.
Details
Sign in to post a comment.
Posted by Microsoft on 2/1/2013 at 12:05 AM
Thank you for your bug submission. The issue you reported appears to be on a released Windows Product. If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com or call 1-800-MICROSOFT for assistance. For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.

To post a question or receive community support for developing Windows Store apps, consider posting your question or concern on the Windows Store apps forum. http://social.msdn.microsoft.com/Forums/en-US/category/windowsapps
Posted by Josh Luth on 1/24/2013 at 7:58 AM
It would appear the problem is becoming more severe. The whole build process is now slower when Windows Defender is running. I have to shut down defender to build in a reasonable amount of time.
Posted by Microsoft on 1/17/2013 at 11:42 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/17/2013 at 8:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.