Windows 10: Visual Studio heavily slows down system since moving to Win10

Hi,

I recently upgraded from 8.1 to 10. Performance seems great in general, but Visual Studio 2013 really slows down the system, both when parsing the project directory and during compiling. Chrome for example takes up to a minute to load a single page. I tried setting the process priority to low, with no effect. Under Windows 8.1 I didn't have any problems with VS.

I tested other applications such as the Unreal Editor and rendering a video from Adobe Premiere, both also get the CPU usage to 100%, but don't have any impact on the general system performance, so VS is the only app where I notice this behaviour.

Has anyone any ideas? Thanks!

:)

 

System update failed couldn't reinstall with same patch again ?

I got failed to install with "Microsoft Visual Studio 2010 Tools for Office Runtime (KB2961149)" and "Microsoft Visual Studio 2010 Tools for Office Runtime (KB2796590)" on Win10 system.

The failed date is 2 Oct 2016, but up to now, the system have not reinstall those patch again ? why ?

 

How to completely uninstall Visual Studio 2015?

I installed Visual Studio 2015 earlier when it came out. I installed different components and various plug-ins. Since Visual Studio 2017 has come out I would like to completely uninstall Visual Studio 2015 before installing Visual Studio 2017.

Because I installed various components, it can be doubtful whether all of them are getting uninstalled or not, I want to completely uninstall Visual Studio 2015 and all of it's components and plug-ins and start from fresh and download Visual Studio 2017.

Can someone please guide me on how to do this?

Operating System - Windows 10 Pro

System Architecture - 64-bit

 

Some things you can try:

Tools -> Options -> Environment -> General
Uncheck "Automatically adjust visual experience based on client performance"
Uncheck "Use hardware graphics acceleration if available"
Uncheck "Enable rich client visual experience"


Tools -> Options -> Environment-Synchronized Settings
Uncheck "Enable synchronization for the following categories of settings"


Delete the .suo file

 

I tried the above and did not work.

Recently we have upgraded our OS to windows 10.
Now when I attempt to open a large DBML file, Visual Studio 2013 hangs forever.
I have tried everything (Safemode, compatbility runs, re install, etc..) but nothing seems to work.
When my previous OS was windows 8.1, the DBML designer was working perfectly.
I dont know if this helps, but I compared memory usage of Visual studio 2013 of windows 8 vs windows 10.
in windows 8, VS 2013 I had readings of about 800 MB + of RAM
In windows 10, it seems VS2013 is being put down to a measly 350 + MB and can't go beyond that

 

I would uninstall and try the new Visual Studio 2015 Community... its FANTASTIC.

 

Thanks for the replies. I tried the VS setting above without luck. I also tested VS2015 Community (even if I couldn't use it even if it would work, because the UE4 does not support it yet), same problem. *Sad

 

I've stuck with W7 'till now, but I think I'm close to upgrading my dev ThinkPad to W10.

I'm wondering if these issues have been resolved, or anyone else can share their W10/VS20xx experience?

I want to do it, but I really can't afford any upgrade issues with my work computer. I've done my personal laptop, but I don't have VS on that.

 

Don't upgrade to Windows 10... thats my recommendation.

Once you've done your fine tuning, disabled the stuff you don't care about, turned off bloaty services, etc... you realize that Windows 10 doesn't do anything that Windows 7 can't. In fact, you find that the operating system in general is filled with compromises. For every 1 thing that works great, there are 10 things that worked better in Windows 7.

Windows 10 also has logical design problems, in that there is no uniformity with how it works... as if the operating system was made by 10 different teams who had different methodologies... who all put the system together as one in the end.

 

Thanks. It seems like, for anyone with an OK experience, there's someone else who's had a not-so-good one.

My biggest concern is potentially losing a day of work cuz I'm wasting time troubleshooting issues resulting from the upgrade. If anything gained from taking that risk is marginal at best, I should maybe reassess my next move.

 

This isn't a problem for the vast majority of others running VS2013 or VS2015 on Windows 10. Did you do an in-place upgrade from Win7/8.1, or did you do a fresh reinstall of Windows 10? Many in-place upgrades have problems.