Why is Visual Studio 2013 very slow?

Question

I'm running Visual Studio 2013 Pro (RTM version) on my formatted PC (Windows 8.1 fresh install).

I don't know why, but Visual Studio 2013 Pro is very very slow! Slow for building, debugging, navigating in the IDE... my hard disk drive LED is not lighting up at all!

I'm on a little MFC (C++) project using the Boost library.

Any ideas?

Does this help:- http://social.msdn.microsoft.com/Forums/vstudio/en-US/1def7e35-b0e9-4842-bb51-70ff62242751/visual-studio-2013-preview-gets-really-laggy-and-slow ? — Rahul Tripathi, Oct 27 '13 at 11:49
Thanks, i disabled the source control, but....it stay slow ! — Walter Fabio Simoni, Oct 27 '13 at 11:55
I have stopped working in VS2013 after a few days, it just kept freezing... — Goran, Nov 08 '13 at 22:47
You should consider marking Asim Omers answer as the solution... it helped me out just fine. — Kris, Aug 05 '14 at 06:49
I would like to see a comprehensive checklist of all the visual studio temp cache — Shawn J. Molloy, Aug 09 '14 at 18:33
Please have a look at my answer on [Visual Studio 2015 extremely slow](http://stackoverflow.com/questions/34395686/visual-studio-2015-extremely-slow). Hope this helps... — Murat Yıldız, Aug 17 '16 at 14:38

score 268 · Answer 1 · edited Jan 27 '14 at 18:42

268

It is something concerned with the graphics drivers. If you update them you will be fine.

Or you can disable the hardware graphics acceleration in Visual Studio according to these steps:

In Visual Studio, click "Tools", and then click "Options".
In the Options dialog box, navigate to the "Environment > General" section and clear the "Automatically adjust visual experience based on client performance" check box. (Refer to the following screen shot for this step.)
Clear the "Use hardware graphics acceleration if available" check box to prevent the use of hardware graphics acceleration.
Select or clear the "Enable rich client visual experience" check box to make sure that rich visuals are always on or off, respectively. When this check box is selected, rich visuals are used independent of the computer environment. For example, rich visuals are used when you run Visual Studio locally on a rich client and over remote desktop.

enter image description here

References:

You experience performance issues, product crashes, or rendering issues in Visual Studio 2013

edited Jan 27 '14 at 18:42

Uwe Keim

39,551
56
175
291

answered Nov 26 '13 at 15:38

Asim Omer

2,689
1
10
5

8

This worked for me, thanks. Not sure why the OP hasn't bothered to kindly accept this as the answer. – Josh C Dec 22 '13 at 18:30
5

It's not a solution for me. – selami Mar 27 '14 at 14:12
11

Deleting the .suo file did it for me. – ceebreenk Jun 19 '14 at 11:52
1

Seems ridiculous having "visual enhancements" enabled for developers. I'm on an i7 w/32GB and this caused problems for me over time. – Fred Lackey Jun 23 '14 at 20:31
Unfortunately this did not help me. – AH. Oct 29 '14 at 07:39
13

Shouldn't "Use hardware graphics acceleration if available" actually increase performance? :\ not decrease it – GONeale Nov 23 '14 at 23:44
+1 for working for me, thank you for the solution! I left the last step on just as an FYI for anyone else stumbling upon this – Torch2424 Jan 28 '15 at 03:52
1

Wow, my work colleague had is computer's fan blasting after almost every key stroke... his compute is now quiet after un-checking "enable rich client visual experience". Thanks! ( vs 2013 prof ). – RayLoveless Jan 30 '15 at 16:59
1

Okai... So I'm using the following hardware and had to disable visual effects: 16 GB RAM, i7-3770K, Titan X, 1000W PSU. I do NOT understand why... This only happens in Windows 8.1 though, not Windows 7. – Yuki Kutsuya Jun 07 '15 at 02:11
The **opposite** of step #3 is what fixed my issues. Visual Studio felt like it was running at 30fps; scrolling felt *especially* laggy. Turning `hardware graphics acceleration` on made everything feel completely smooth. – inline Jun 30 '15 at 03:28
This helped me as well, under windows 10 – LauriK Aug 12 '15 at 06:53
Check [this](http://www.codemag.com/article/0907031) article **Time to clean up** may help too. – Shaiju T Sep 08 '15 at 09:53

score 111 · Answer 2 · edited Nov 01 '19 at 11:58

111

Try to set Current source control plug-in to None (menu Tools → Options → Source Control), if you are using the Microsoft Git provider, which seems to slow Visual Studio 2013 down more and more the larger the repository gets.

Enter image description here

I had the whole Dojo Toolkit framework under source control using the Microsoft Git provider, and it got to the point where there were delays from the time I hit a key to the time the glyph would appear on the screen. That bad.

When/if you need Git again, you can switch to the TortoiseGit provider or Git-Extensions, both will work without slowdown. I like Git-Extensions, personally.

edited Nov 01 '19 at 11:58

Peter Mortensen

30,738
21
105
131

answered Mar 05 '14 at 18:33

Isaac Bolinger

7,328
11
52
90

26

Removing source control is not a solution in a professional development enviornment – codemonkeh Dec 15 '14 at 21:58
9

I said switch to a different VS git extension. – Isaac Bolinger Dec 16 '14 at 00:24
1

The OP didn't even mention source control, let alone Git – codemonkeh Dec 16 '14 at 22:41
42

This question transcends its original context. People search for VS 2013 slow and come here. It's helpful to know that Microsoft Git is currently slow and buggy. – Isaac Bolinger Dec 17 '14 at 02:31
1

@codemonkeh I had same issues as OP and turning of Microsoft Git saved me after a lot of searching. – Vian Esterhuizen Jan 08 '15 at 21:54
1

It is somewhat better with that but not perfect.. but Microsoft closing the bug report as "not reproduced" is unacceptable (https://connect.microsoft.com/VisualStudio/feedback/details/894086/configuration-manager-extremelly-slow) – JB. Feb 17 '15 at 10:31
Waow, this made a world of difference! Pretty much anytime I renamed a file, moved anything about or added/removed files, VS would grind to a halt even on an SSD. Thanks – JMK May 23 '16 at 14:11
I don't know about you but when I try to change this setting back to None I get an error message saying it needs to close my solution. When I reopen my solution this setting is back to it's original value. – Jean-Simon Brochu Dec 13 '16 at 13:41

score 53 · Answer 3 · edited Nov 01 '19 at 12:11

53

I too have struggled a bit with bad performance in Visual Studio 2013 (Premium). Pretty much the same issues as TS had. Slow navigation, scrolling, building... just about everything. Luckily I have manage to solve my own problem by disabling Synchronized Settings in Visual Studio. Go to menu Tools → Options → Environment-Synchronized Settings and remove this option by unchecking the checkbox.

Disable Synchronized Settings

edited Nov 01 '19 at 12:11

Peter Mortensen

30,738
21
105
131

answered Aug 26 '14 at 19:08

Indregaard

1,195
1
18
26

This helped me for reducing the long wait time (even up to a minute) when switching configurations (e.g. from 'Debug/x64' to 'Release/Win32'). Disabling setting synchronization dropped it to normal speed of < 1 second. +1 – zzz May 26 '16 at 23:43
This is the answer that seemed to fix my problem. I was waiting between 1 and 3 seconds after typing for 10 seconds in my IDE. – Jean-Simon Brochu Dec 13 '16 at 13:39

score 47 · Answer 4 · answered Mar 28 '14 at 12:19

47

In the case of web applications, another cause of slow building and debugging (but not IDE navigation) could be the Browser Link feature.

I found that with this switched on, building would take 4 times longer and debugging was painful - after every postback, web pages would freeze for a few seconds before you could interact with them.

answered Mar 28 '14 at 12:19

pierreluigi88

488
4
8

After upgrading to VS2013 my pages especially with javascript started to load very slow. Turning off Browser Link feature solved this problem and now my web pages load fast again. Thanks a lot! – cck Jun 18 '14 at 13:48
1

The weird thing is that browser link slows down some pages and others not. At least one can easily check if browser link is the source of the problem. Just load a page where the problem occurs and check if after the page has been loaded the CPU usage remains high. If that is the case and the CPU usage is low if you disable Browser link, than you can be sure it's browser link. BTW: I have the feeling that it has sth to do with the use of class attributes in HTML. – Leo Gerber Jun 25 '14 at 12:00
1

This improved my debugging 400% faster. Disabling Browser link has to be done by each developer, rather you can add following appsetting to disable it from the project level – Dhanuka777 Dec 30 '14 at 05:27
This fixed the issue for me. My machine would start thrashing after opening a web project, then navigating to it in my browser. Switching this feature off made a huge improvement. @Garzun, I think you are on the right track, I suspect media queries could be the issue. – Rastus7 May 13 '15 at 04:11
1

Tried removing Git Source Control and disabling the graphics enhancements but this change made the most difference for my machine. – Neil Thompson Jul 14 '15 at 08:25
This made a HUGE difference, this was the issue for me, absolutely! Thank you – njfife Aug 31 '15 at 20:14
It is still the same for VS2015. I don't know why Microsoft adds these "features". It just makes them look bad. – Dan Randolph Feb 08 '16 at 18:54

score 38 · Answer 5 · answered Nov 12 '14 at 00:21

38

I was using a solution upgraded from Visual Studio 2012. Visual Studio 2013 also upgraded the .suo file. Deleting the solution's .suo file (it's next to the .sln file), closing and re-opening Visual Studio fixed the problem for me. My .suo file went from 91KB to 27KB.

answered Nov 12 '14 at 00:21

Aaron Jensen

25,861
15
82
91

2

I'd like to concur this tip. My suo was 1mb!! I just deleted it and reopened the sln and the typing and intellisense is now immediate whereas before bringing up properties in the xaml editor would take 10s of seconds. – pfa Nov 12 '14 at 18:02
5

.suo is a hidden file. – Dherik Feb 05 '15 at 15:35
Perhaps add information about what will be lost? E.g. settings for what to launch at F5 (the particular project. Several projects.) – Peter Mortensen Nov 01 '19 at 12:16

score 37 · Answer 6 · edited Nov 01 '19 at 12:13

37

I had the same problem and the only solution that worked for me was to follow the three steps presented below:

Clean the WebSiteCache folder (you may find it at C:\Users\%USERNAME%\AppData\Local\Microsoft\WebSiteCache)
Clean the "Temporary ASP.NET Files" folder (find it at C:\Users\%USERNAME%\AppData\Local\Temp\Temporary ASP.NET Files)
Restart Visual Studio

edited Nov 01 '19 at 12:13

Peter Mortensen

30,738
21
105
131

answered Sep 19 '14 at 13:11

playful

1,744
15
14

This definitely helped and improved the situation... but did not solve it completely, this step is recommended on the journey of discovering why vs2013 is so slow and crashy – julian guppy Jan 31 '15 at 10:55
5

Cleaning the WebSiteCache folder did the job for me. Honestly, I can't even describe what a huge difference there is. I waited for 30 minutes to create a new ASP.NET Web Forms project and Visual Studio was often saying "Not Responding". After cleaning the cache, it takes less than 10 seconds. – Apostrofix Jun 02 '15 at 11:45
3

The "Temporary Asp.Net Files" are usually under C:\Windows\Microsoft .Net\Framework(64)\{version} – yoel halb Apr 07 '16 at 15:27

score 20 · Answer 7 · edited Nov 01 '19 at 12:02

20

What fixed it for me was disabling Git by setting Current source control plug-in to None in Visual Studio, menu Options → Source Control:

Enter image description here

edited Nov 01 '19 at 12:02

Peter Mortensen

30,738
21
105
131

answered May 21 '14 at 02:23

Mike Flynn

22,342
54
182
341

To corroborate: this fixed it for me in VS Express 2013. Having my project attached to git was absolutely killing VS. – adaam Jun 10 '14 at 19:44
Reformatted my computer, disabling Git still makes it faster so I believe this is one of the issues why VS is slow in 2013. – Mike Flynn Aug 13 '14 at 15:19

score 19 · Answer 8 · edited Nov 01 '19 at 12:01

19

This issue seems to be because of uninstalling the SQL Server Compact edition (4.0).

I was having this issue, and it got fixed after installing the SQL Server Compact edition 4.0. On closing Visual Studio 2013, I was getting a message to install SQL Server Compact edition as a C++ project needed some thing... can't put finger on anything.

edited Nov 01 '19 at 12:01

Peter Mortensen

30,738
21
105
131

answered Apr 15 '14 at 02:50

user3534241

191
1
2

3

THANK YOU! I was trying to clean off my system but for Visual Studio it backfired! – Pete Alvin May 20 '14 at 02:18
What a bizarre and completely intuitive solution. From the op's question, it is hard to trace the problem to sql compact, but hey it works. – Shawn J. Molloy Aug 02 '14 at 00:48
Yes, that worked for me too. Matter of fact I dont know why it would matter but I started getting intellisense working for plain C++ code after installing SQL Server Compact Edition. – NOMO Mar 10 '15 at 03:17
This worked perfectly. Could not understand why it was running so slowly with only c++ projects, but a warning is displayed before exiting visual studio, which I should've read better since it specifically mentions the absence of SQL Server Compact Edition... – Force444 Sep 12 '15 at 20:56
Was it for me. Very hard to find. – Bene Tleilax Jan 18 '16 at 20:56

score 12 · Answer 9 · answered Jun 20 '14 at 07:56

12

Resolve this issue by installing Microsoft SQL Server Compact 4.0

Microsoft SQL Server Compact 4.0

visual Studio 2013 performance issue due to missing Microsoft SQL Server Compact 4.0

answered Jun 20 '14 at 07:56

Halim

2,090
2
16
9

11

I don't follow. How is this related to this question? – Keith Pinson Sep 11 '14 at 17:05
This definitely works. I uninstalled mine but had to reinstall. It's as if VS goes off on a wild goose chase to look for this component constantly, so do yourself a favor and make sure it's installed. – Seralize Nov 04 '14 at 19:35
[user3534241's answer](https://stackoverflow.com/questions/19617670/why-is-visual-studio-2013-very-slow/23073857#23073857) also alluded to this. – Peter Mortensen Nov 01 '19 at 12:09

score 11 · Answer 10 · edited Nov 01 '19 at 12:34

11

I can advise an option like this.

CodeLens can be disabled like as at the picture. It gives a lot of performance goodness.

Enter image description here

edited Nov 01 '19 at 12:34

Peter Mortensen

30,738
21
105
131

answered Mar 03 '15 at 20:24

Oğuzhan Soykan

2,522
2
18
33

score 7 · Answer 11 · edited Nov 01 '19 at 12:07

7

If you are debugging an ASP.NET website using Internet Explorer 10 (and later), make sure to turn off your Internet Explorer 'LastPass' password manager plugin. LastPass will bring your debugging sessions to a crawl and significantly reduce your capacity for patience!

I submitted a support ticket to Lastpass about this and they acknowledged the issue without any intention to fix it, merely saying: "LastPass is not compatible with Visual Studio 2013".

edited Nov 01 '19 at 12:07

Peter Mortensen

30,738
21
105
131

answered Jun 18 '14 at 01:09

Smyrnian

701
9
15

Amazing, I just installed LastPass this AM and never thought twice that it was causing my headaches... – ewitkows Aug 18 '14 at 18:58
It's not just IE. Same issue with Chrome and Firefox it seems. Disabling it returned VS to normal once again for me. – Noah Sep 17 '14 at 17:24

score 6 · Answer 12 · edited Nov 01 '19 at 12:24

6

I had the same problem and all the solutions mentioned here didn't work out for me.

After uninstalling the "Productivity Power Tools 2013" extension, the performance was back to normal.

edited Nov 01 '19 at 12:24

Peter Mortensen

30,738
21
105
131

answered Dec 09 '14 at 17:19

CoffeeCode

4,296
9
40
55

I also have had this issue with the same fix using Visual Studio 2015. – Gram Jan 26 '16 at 21:54

score 5 · Answer 13 · edited Nov 01 '19 at 12:25

5

One more thing to check; for me it was Fusion logging.

I'd turned this on a very long time ago and more or less forgotten about it. Getting rid of the 5000+ directories and 1 GB of logged files worked wonders.

edited Nov 01 '19 at 12:25

Peter Mortensen

30,738
21
105
131

answered Dec 18 '14 at 13:00

Richard Petheram

805
12
16

I've enabled fusion logging in the past, and forgotten about it. In solutions with lots of projects (20+) this can really kill performance. I've disabled it again and everything is very speedy now. Also only enabling bind failures is better for performance then all bindings. – Preben Huybrechts Feb 17 '15 at 08:00
What is *"Fusion"* (in this context)? – Peter Mortensen Nov 01 '19 at 12:26
Some context: *[Back to Basics: Using Fusion Log Viewer to Debug Obscure Loader Errors](https://www.hanselman.com/blog/BackToBasicsUsingFusionLogViewerToDebugObscureLoaderErrors.aspx)* – Peter Mortensen Nov 01 '19 at 13:22

score 4 · Answer 14 · edited Nov 01 '19 at 12:13

4

There is a good workaround for this solution if you are experiencing slowness in rendering the .cs files and .cshtml files.

Just close all the files opened so that the cache gets cleared and open the required files again.

edited Nov 01 '19 at 12:13

Peter Mortensen

30,738
21
105
131

answered Sep 11 '14 at 06:29

Renjith K

41
1
1

score 4 · Answer 15 · edited Nov 01 '19 at 12:22

Visual Studio Community Edition was slow switching between files or opening new files. Everything else (for example, menu items) was otherwise normal.

I tried all the suggestions in the previous answers first and none worked. I then noticed it was occurring only on an ASP.NET MVC 4 Web Application, so I added a new ASP.NET MVC 4 Web Application, and this was fast.

After much trial and error, I discovered the difference was packages.config - If I put the Microsoft references at the top of the file this made everything snappy again.

Enter image description here

Move the Microsoft* entries to the top.

Enter image description here

It appears you don’t need to move them all - moving say <package id="Microsoft.Web.Infrastructure" has an noticeable effect on my machine.

As an aside

Removing all contents of the file makes it another notch faster too*
Excluding packages.config from Visual Studio does not fix the issue
A friend using Visual Studio 2013 Premium noticed no difference in either of these cases (both were fast)

UPDATE

It appears missing or incomplete NuGet packages locally are the cause. I opened the Package manager and got a warning 'Some NuGet packages are missing from this solution' and choose to Restore them and this sped things up. However I don’t like this as in my repository I only add the actual items required for compilation as I don’t want to bloat my repository, so in the end I just removed the packages.config.

This solution may not suit your needs as I prefer to use NuGet to fetch the packages, not handle updates to packages, so this will break this if you use it for that purpose.

This answer had the most significant effect in my case. Thank you. — hakan, Apr 14 '15 at 15:57
Yes it seems missing Nuget packages too cause VS 2013 to slow down. Strange! — Chandermani, Mar 17 '16 at 10:49

score 3 · Answer 16 · edited Nov 01 '19 at 12:24

For me, the problem was the Start page -- it was downloading content and causing Visual Studio to hang.

The only solution for me was to:

Kill the DevEnv process from Task Manager
Start Visual Studio in Safe Mode from the command line:
devenv.exe /safemode
Go to menu Tools → Options, and select the Environment/Startup options
Choose "Show empty environment" for the startup action
Close Visual Studio
Restart normally

score 2 · Answer 17 · edited Nov 01 '19 at 13:08

2

Running unit tests was slow. It was a ReSharper issue.

Menu ReSharper → Options → Environment → General ... Clear Caches
Menu Tools → Options → ReSharper → General ... Suspend Now
Close Visual Studio
Delete the .suo file.
Open Visual Studio again.
Re-enable ReSharper.

edited Nov 01 '19 at 13:08

Peter Mortensen

30,738
21
105
131

answered Aug 03 '15 at 14:35

Jess

23,901
21
124
145

score 1 · Answer 18 · edited Nov 01 '19 at 12:37

I also had an issue with a slow IDE.

In my case I installed

ReSharper
Npgsql (low chance to cause the problem)
Entity Framework Power Tools Beta 4

The following helped me a bit:

Disabled synchronization - menu Tools → Options → Environment-Synchronized Settings
Disabled plug-in selection - menu Tools → Studio → Options → Source Control.
Disabled Entity Framework Power Tools Beta 4 - menu Tools → Extensions and Updates

Uninstalled JetBrain's Resharper - WOW!! I am fast again!!

score 1 · Answer 19 · edited Nov 01 '19 at 13:23

1

Change the Fusion Log Value to 0. It solved my issue.

This is the FusionLog key in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion
Check ForceLog value (1 enabled, 0 disabled).

edited Nov 01 '19 at 13:23

Peter Mortensen

30,738
21
105
131

answered May 13 '16 at 12:41

sansalk

4,595
2
36
37

*"Fusion Log Value"* vs. *"FusionLog"* vs. *"Fusion"*: What is literal and what is not? – Peter Mortensen Nov 01 '19 at 13:24

score 1 · Answer 20 · edited Nov 01 '19 at 13:26

1

I was also facing this issue for quite long time. Below are the steps that I perform, and it works for me always:

Deleting the solution's .suo file.
Deleting the Temporary ASP.NET Files (You can find it at find it at %WINDOW%\Microsoft.NET\Framework\Temporary ASP.NET Files)
Deleting all breakpoints in the application.

edited Nov 01 '19 at 13:26

Peter Mortensen

30,738
21
105
131

answered Jul 12 '16 at 09:43

Geeky Ninja

6,002
8
41
54

score 0 · Answer 21 · edited Nov 01 '19 at 12:14

0

Visual Studio 2013 has a package server running, and it was spending up to 2 million K of memory.

I put it to low priority and affinity with only one CPU, and Visual Studio ran much more smoothly.

edited Nov 01 '19 at 12:14

Peter Mortensen

30,738
21
105
131

answered Sep 26 '14 at 18:47

André Liu

441
5
8

6

What is the process name of Visual Studio package server ? You see, 2 million K of memory is a lot, ~1.9GB of RAM. Is it devenv.exe process or something else ? – Dio Phung Nov 18 '14 at 02:29

score 0 · Answer 22 · edited Nov 01 '19 at 12:46

0

Performance Explorer

Have you been using menu Analyze → Performance and Diagnostics? I have! It's awesome! But you may want to clean up.

Open the Performance Explorer. If you collapse all of the items in there, select all, then you can right click and do Delete.

My solution opens faster and is in general running much faster now.

Also you may notice changes to your sln file as shown. For me, this section was deleted from the sln.

GlobalSection(Performance) = preSolution
    HasPerformanceSessions = true
EndGlobalSection

edited Nov 01 '19 at 12:46

Peter Mortensen

30,738
21
105
131

answered Jul 24 '15 at 16:23

Jess

23,901
21
124
145

1

This is for measuring apps performance during development, but not for visual studio itself – Dec 09 '15 at 13:43
Yes, but using the tool will affect visual studio performance as in my case. This question and set of answers is more like a check list. Not all answers will apply in all cases. – Jess Dec 09 '15 at 14:09
Can you add some more information to the answer about what it deletes/changes (some state is altered)? – Peter Mortensen Nov 01 '19 at 12:39

score 0 · Answer 23 · edited Nov 01 '19 at 13:09

0

In Visual Studio 2015 Community edition, I've experienced a very (very) slow IDE after changing the "Environment Font" on menu Tools → Options... → Fonts and Colors.

Reverting this options back to the default value ("automatic") solved it immediately.

edited Nov 01 '19 at 13:09

Peter Mortensen

30,738
21
105
131

answered Aug 25 '15 at 22:08

Marcelo Myara

2,841
2
27
36

This is definitely the weirdest optimization I've seen on this thread so far. I wonder how Font was messing it up... – kayleeFrye_onDeck Jun 22 '16 at 19:07

score 0 · Answer 24 · edited Nov 01 '19 at 13:15

I had similar problems when moving from Visual Studio 2012 → Visual Studio 2013. The IDE would lock up after almost every click or save, and building would take several times longer. None of the solutions listed here helped.

What finally did help was moving my projects to a local drive. Visual Studio 2012 had no problems storing my projects on a network share, but Visual Studio 2013 for some reason couldn't handle it.

score 0 · Answer 25 · edited Nov 01 '19 at 13:28

I had a Visual Studio 2013 installed, and it was running smoothly. At some point it started to get sluggish and decided to install Visual Studio 2015. After install, nothing changed and both versions were building the solution very slow (around 10 minutes for 18 projects in solution).

Then I have started thinking of recently installed extensions - the most recent installed was PHP tools for Visual Studio (had it on Visual Studio 2013 only). I am not sure how can an extension affect other versions of Visual Studio, but uninstalling it helped me to solve the problem.

I hope this will help others to realize that it is not always Visual Studio's fault.

score 0 · Answer 26 · edited Nov 01 '19 at 13:29

0

I added "devenv.exe" as an exclusion to Windows Defender. This solved my problem completely. People can try this as their first try.

edited Nov 01 '19 at 13:29

Peter Mortensen

30,738
21
105
131

answered Jan 04 '17 at 09:06

Sahil Lakhwani

108
2
11

score 0 · Answer 27 · edited Nov 01 '19 at 13:30

0

I have the same problem, but it just gets slow when trying to stop debugging in Visual Studio 2013, and I try this:

Close Visual Studio, then
Find the work project folder
Delete .suo file
Delete /obj folder
Open Visual Studio
Rebuild

edited Nov 01 '19 at 13:30

Peter Mortensen

30,738
21
105
131

answered May 05 '17 at 04:23

kho dir

125
4

score 0 · Answer 28 · edited Nov 01 '19 at 13:34

None of the suggestions worked for me, but I did solve my problem. I had tried most of the other recommendations before coming to the following solution.

My Scenario/Problem:

Using Visual Studio 2017 with ReSharper Ultimate. Keyboard input in the IDE got super slow as others have described. The last change I made to my solution was to add a new web site project, so I looked into that. After trying a lot of things, I tried adding a second web site project, so I could try to replace the first one, and Visual Studio just tanked after that. It wouldn't even load the solution anymore.

My Solution:

I forced Visual Studio closed and then I removed the newly added web site project(s) from the .sln file using Notepad. After saving and starting Visual Studio, my solution loaded quickly and everything seemed to be back to normal. I added a new Web Site with a slightly different configuration (see the thinking below), and the problem did not present itself again.

My Thinking:

I think the problem stemmed from creating the new web site project and using a file system path to a network share that is hosted in Azure. I'm working over VPN which tends to slow things down, and I occasionally experience various routing problems with some services, so my problem/solution might be a bit of a snowflake. I changed the file system path to be a local repository and will publish the files as needed which seems like a much better way to go.

score 0 · Answer 29 · edited Nov 01 '19 at 13:35

0

I had a Visual Studio behavior where the typing was slow for my HTML files. Previously when I installed, I guessed that because my HTML files were generic HTML that the need to install any web development tools from the workload component of the installer was unnecessary. I went back and installed this bit and Visual Studio behavior became as I expected it.

edited Nov 01 '19 at 13:35

Peter Mortensen

30,738
21
105
131

answered Aug 24 '17 at 15:33

Todd Partridge

661
1
8
11

score 0 · Answer 30 · answered May 12 '21 at 15:45

This already has a bunch of answers here, but a general way to easily boost Visual Studio is to clear your temp files.

Press the Windows Key and R, and enter 'temp'. Press enter, and provide any administrator permission if you need to. Then press Control A to select all, and hit the Del key. Remember to provide any administrator permissions, and if 'the item is already in use' then just press skip.

After this, Press Windows Key and R again, but this time type '%temp%'. Repeat the previous steps in the new directory.

Finally, empty the recycle bin.

This might not help a ton, but it should boost general performance.

score -1 · Answer 31 · edited Nov 01 '19 at 12:33

-1

Did anybody find CodeLens (the reference counter) problems with startup performance?

Disable CodeLens (menu Tools → Options → text editor → All languages → CodeLens)

Disable Git Source Control too (menu Tools* → Options → Source control)

edited Nov 01 '19 at 12:33

Peter Mortensen

30,738
21
105
131

answered Jan 09 '15 at 06:40

nano

183
1
1
7

score -1 · Answer 32 · edited Nov 01 '19 at 13:19

-1

Mike Flynn's version did not work for me. Renaming C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Microsoft.TeamFoundation.Git.Provider.dll worked for me.

edited Nov 01 '19 at 13:19

Peter Mortensen

30,738
21
105
131

answered Feb 26 '16 at 09:29

Kunal

887
1
8
15

Why is Visual Studio 2013 very slow?

32 Answers32

UPDATE

Performance Explorer

Linked