How to stop incredibuild from auto-installation on my PC? - visual-studio

It seems that incredibuild was installed on my PC, likely came in bundle with visual studio. It autostarts when my PC runs, and it has high disk usage and eventually will slow down the entire PC. I will have to stop it from running to make my PC fast again.
I tried removing it but each time I did, it would come back a few days later even if I havent used visual studio for the past 2 weeks. Disabling it from startup will not work either, it will be running when the PC starts anyway. So what am I supposed to do with Incredibuild? I dont want to uninstall Visual Studio, but I need Incredibuild gone.

IncrediBuild is a build acceleration software that accelerates Visual Studio compilations by distributing the compilation tasks to idle machines across your network. As IncrediBuild is bundled with Visual Studio, you probably chose to install it as part of your Visual Studio setup.
IncrediBuild is not supposed to use any of your resources when it is not in use and we haven't received such a feedback from the >100,000 developer using IncrediBuild...
To uninstall the IncrediBuild plug-in, go to Visual Studio Tools->Extensions and Updates. In the popup window, under the Install tab, choose IncrediBuild Build Acceleration and uninstall.
We'd highly appreciate if you can make sure that the problem you reported indeed comes from IncrediBuild and if so, contact us at support#incredibuild.com
Disclaimer, the write is working at IncrediBuild.

Related

Visual Studio slowness, possible reason?

Im struggling with extremely slow Visual Studio. I use it to build C++ projects mostly.
Everything could be super slow. Menu's loading, intelIsense tips, builds. I've just tested building simple solution in 1 file, and build took around 5 minutes. But! I found this article about Windows Performance Analyzer which I used to trace this solution build. Despite overall time taking around 5 minutes, WPA report build took only around 0.686 seconds, attaching screenshot:
apparently I press "rebuild" in VS and build itself started ~300 seconds later(timeline).
Currently I use VS2019. Same problem I observed on VS2017. I did removed all VS components and installed VS2019 and problem is not gone. All other programs run fine. No excessive CPU load(intell 6700k), no noticeable harddrive usage(windows and VS components are on m2 ssd, lightning fast), 32 gb ram and enough free space on system disk.
Only VS extension I installed myself is QT extension for VS2019. Which actions can I take next to find the problem?
Things to try:
devenv /safemode from a command line starts the IDE in safe-mode with all plugins disabled.
Visual Studio Installer and repair install
Disable graphics acceleration in Visual Studio (Tools|Options|General ... there are a few "rich client visual experience" related things)
Check paths on your computer. If other apps run fine but one does not, it could be that this app tries to access a network drive or website which is not available.
Run "procmon" and "procexp" (Process Monitor/Process Explorer from Sysinternals) and take a look at what's going on.
Try VS 2022.

why is my Visual Studio 2019 Pro so slow debugging, after doing Visual Installer update?

VS2019 was working fine.
Then I ran Visual Installer and added "Mobile development with .NET".
After than, visual Installer "update" button was showing, so I did the update.
But now when I stop my VS2019 project at a breakpoint, single stepping is very slow, taking many seconds per step.
Tried restarting VS2019, and restarting my Windows 10 Pro, but got same slowness.
Opened same project with VS2017, it is debugging is OK, no slowness.
The resolution I found was that the culprit is not Internet, RAM, or CPU.
It is the Disk Usage. Check for your disk usage under the Performance tab in Task Manager. Try and find out which process (Anti-Malware/ anti-virus/ant other process) is eating up your resources.
Kill the culprit and it works smooth. For me, it was Disk Scan Service and Windows Search Service (which is fairly useless).
Check this link to kill the Windows search service.
Comprehensive deletion of all contents of %TEMP% worked for me -
https://developercommunity.visualstudio.com/content/problem/516141/very-hight-cpu-usage-by-visual-studio-2019.html
I can't believe is 2020 and MS can't stop spaffing crap into a temp directory which causes their software to slow to a snails pace with some kind of infinite processing issue. Jeez.
For me it was NVidia NSight for visual studio. Uninstalling it from the windows application list was the only option as it wasn't showing up in the VS2019 Extensions manager.
For me it turned out to be a problem with the installation. I had old versions of Visual Studio and .NET libraries still on my machine. I did a full uninstall of Visual Studio, .NET Core SDK, .NET Framework, etc. and then re-installed Visual Studio 2019 and just the .NET libraries that I needed. After that VS 2019 debugging is speedy.
I was experiencing the same issue stepping over one line of code took me 1400 ms on my VM and 6 ms on my coworker's VM. (Earlier this week he had copied my VM so essentially we were on the same machine).
Took me some time but then I remembered a change I did to my visual studio.
Earlier that week I needed to step into one of our DLLs. To do this I changed my debug settings under Project Properties --> Debug --> Debugger engines. I Checked "Enable native code debugging". This was wonderful to allow me to debug into our DLL and see what was happening on the other side, although it dramatically slowed down my debugging (233x slower to be exact!!!!).
The performance change will different per your solution and how much you are inheriting, but unchecking this did the fix for me!
Delete .vs folder where locate in your project root directory after backup.

Visual Studio 2013 Community Installer installed the Express Edition

Recently, I decided to "get with the times" and upgrade from VS2012 to VS2013. I downloaded the installer, and ran it. The first time around, the install failed around the 80th component, but I tried again and it worked. When it finished, I booted up VS, and it all looked fine, save for that little word on the splash screen, "express". I didn't really care for a while, but now I need a GLSL plugin, and it won't install, on account of it being the express edition. I would prefer not to reinstall, as it took quite a while last time, and I'm not too confident in the installers ability to not muck up my projects.
Whenever Visual Studio installations end up in a funny state, it's best to try to reinstall it. Most of the times just running setup again and choosing Repair will do the trick, but sometimes your configuration is corrupted in such a way that it prevents repairs. In that case try running setup with the /uninstall /force command line options once to forcefully evict Visual Studio from your computer before trying the installation again.
It may feel that it's faster to try and 'fix' Visual Studio, but remember that this is a massive beast installing and configuring many different packages and components and trying to manually ensure that they're all correct is incredibly hard. It may seem that you fixed it, but then later find out that the debuggger acts funny or that you can't create a certain type of project.
So, to prevent those strange issues, always, in case of a failed install, sit through it once more.

Visual Studio 2010 (devenv) Hung Process After Closing

I have problem with Visual Studio 2010 on Windows 7 64-bit. After some time of work VS starts consuming ~50% CPU and UI responding slows down. When I close VS then UI disappear but process stay.
When I forgot to kill those hung processes at the end of day, I will end up with numerous devenv.exe processes.
I have reinstall Visual Studio and reinstall Windows and ended up with the same problem... doesn't change anything. Please help. :/
Remove and/or uninstall all third-party Visual Studio add-ins and extensions. Disabling is not good enough.
Visual Studio 2010 relies heavily on graphics. Therefore:
Update your video driver.
Turn off "Enable rich client visual
experience"
Turn off "Use Hardware graphics acceleration if
available"
There are also temporary files that Visual Studio uses that may need to be cleared out.
Clear out your %temp% folder.
Clear out %AppData%\Local\Microsoft\WebsiteCache
Clear out %AppData%\Local\Microsoft\VisualStudio\10.0\ProjectAssemblies
Your project and solution user settings may be corrupt due to so many "crashes".
Delete .user and .suo files (you will lose the startup project, bookmarks, breakpoints, and other user settings specific to projects and solutions.)
Begin where you began before - it may seem overkill but this is the only way to be sure we are addressing everything short of hardware issues.
Reinstall Windows - make sure you are using a validly licensed copy, and patch the hell out of it before installing Visual Studio.
Note: I doubt it is a GPU driver issue, but it never hurts to use the most up to date driver and this is the place to do it right after a fresh OS install.
Install Visual Studio .Net 2010 but do not start it up. Let it get the frameworks installed fresh.
Use Windows Update to install the VS 2010 SP1 patch, and any/all patches for .Net frameworks.
Make an images for yourself right here so you have something to build from if you need to try this again. It will save you lots of time.
Fire up Visual Studio, and test your closing before installing anything else.
If it does not work here, there's likely some conflict between PC hardware and window OS, and you should try to find this symptom in other applications to get more info.
Here's what i would be looking for:
Does it happen EVERY TIME?
Does it happen after you debug your project ? does it happen for ALL projects?
Does it also happen when you don't load any projects? (simply start the IDE and wait).
Does it happen after a debug session of your application? maybe the application is not closed properly?
Do you have any other apps running at the same time that may cause this? try reproducing with a minimal set of apps/services running.
What are you doing exactly when it starts freezing ? anything in particular?
I would try to get 2-3 memory dumps at the time of hanging, post it here as well as to MSFT people. That would be a good start.

Visual Studio 2005 build problem

Cheers,
I have Microsoft VS 2005 installed (full version). And when I'm trying to build or debug my solution (with 10 projects) a windows installer window opens and says:
The feature you are trying to use is on cd-rom or other removable....
So I then put my VS2005 CD and VS does his thing and than my build and debug processes are working. But when I shut down VS and open it again and when I want again to build my solution it asks me the same thing.
I deleted VS2005 and installed it again (again full version) and it asks me the same thing. I am really crazy right now.. why VS just don't do "update" or something, I don't want to insert CD every time I start VS.
tnx
When Visual Studio was installed on your system, you might have chosen a typical installation or a custom installation that did not include everything available to it. This is appropriate in some cases (low disk space, you know only a certain subset is all that is aver or should ever be used).
Try reinstalling, and make sure its a complete install. And don't have it delete unused pieces.

Resources