I am attempting to install Visual Studio 2015 Community but during the installation there is a prompt on the install wizard saying either saying:
'Microsoft build tools x86' (I would assume it's trying to build something and it will not let me)
OR
'Creating a system restore point' (View screenshot):
https://i.gyazo.com/2da949c61d65bcf1b5c2b66dc3bfdf29.png
I am running Windows 10 and I do not know what to do! Even if I cancel the installation it won't let me and I have to force close it using the task manager. Furthermore it has taken up nearly 5GB on my HDD and I can't even uninstall it as it is showing the same message ('Creating a system restore point')!
Any suggestions on how to go about uninstalling it and installing Visual Studio the correct way? I desperately need it for my coursework.
Thanks,
James.
Visual Studio is a very large program and takes a long time to install. You need to have patience. Closing the installation with the task manager is a very bad idea. The install messes with your system files and force stopping it when it is messing with a system file results in corrupt system files.
I would restore your PC to a point before the forced stop install. Then I would start the installer and wait at least 6 hours for the installer to do something. If this does not work I suspect your computer is not suitable to run Visual Studio.
Have you waited long enough? Visual Studio is heavy software and creating system restore point may take a while. if you want to remove it you can follow this http://blogs.msdn.com/b/heaths/archive/2015/07/17/removing-visual-studio-components-left-behind-after-an-uninstall.aspx, even if it is for VS 2013 it should work similar. If it doesn't you can use System Restore to restore to a point before you tried to install. Then use CCleaner to clear temp files and try reinstalling. Also a little recommendation, remove .NET Framework from you PC and wait for VS to install it, it might get corrupted.
Related
I'm using Windows 10 ver. 1909. Installer hangs or does nothing. No feedback.
I had exactly this problem. Same version of Windows 10. I tried both vs_community.exe and vs_professional.exe. On a Microsoft Surface Pro 4. The installer launches, a brief unpacking screen appears, that vanishes, and you're left with the task manager showing the installer but no user interface. I tried numerous different suggestions from Googling as well as the Collect.exe tool. None of that helped. Someone had a similar problem that hinted that a display could cause the problem. My Surface had Duet installed, which allows you to use an iPad as a second monitor. Uninstalling that allowed Visual Studio to install normally. Apparently the Visual Studio installer is finicky about displays so if you have any unusual display drivers, or screen sharing utilities, they should be removed to allow installing. I suspect that the driver or utility could be put back after installation.
In my case, the issue was that I have downloaded and launched the installer to a user folder that contains non-English characters. Moving the installer to another folder fixed the issue. I´ve diagnosed the issue by looking into an installer log file in C:\Users<username>\AppData\Local\Temp\dd_vs_professional__143315035.1628536728_decompression_log.txt.
At first you need to download this tool Event Collect for visual studio, open your CMD as administrator,then run Collect.exe , after that you need to run your visual studio installer in the event of an error you will find and file named C:\Users{username}\AppData\Local\Temp\VSSetupEvents.txt that you can check to see the error messages.
For more details you can check documentation .
My case is very embarrassing for Microsoft. I downloaded Visual Studio Setup and started it right away from browser. It was opened and then immediately closed. Nothing I could read on the Internet about this problem was not helping. Then I did one very simple thing. Moved setup from original location: C:\Users(user name)\Downloads, to c:\Temp -> worked like a charm. The thing is that my user name contains international characters (plus containing a space). All in all 21. century, full unicode support everywhere, but not in windows. Really embarrassing.
Visual Studio 2019 Installer doesn't start
I lost time about something I shouldn't have, I couldn't install vscode studio 2019 (I've installed it on multiple machines before).
I don't know exactly why, observed there might be something in my folder blocking it, I just moved it to a new folder and I could install. Good luck and don't make the same mistake as me
I have this build Machine at a remote location. The process of building a full install is that first I update my code via SVN update and then open Visual Studio 2015 Enterprise and build the solution in Release Mode, once that is done I would then open Advanced Installer to build the package to an executable.
But from Friday I am unable to build my code with visual studio 2015, it would seem that build is happening but I am not seeing Build Successful, its been an hour and I had to kill the process(devenv) to Cancel the build.
The only delta which happened from last time is that SVN in my organization is running into some issues in which writes are failing, but logically it doesn't make any sense that visual studio wouldn't build a solution because there is an issue with SVN. I mean, one can argue saying that maybe there is a read error too but I am positive that I have all the necessary code files to build the solution, and for the sake of argument if we say I hadn't, shouldn't I have run into build errors rather than a hung build?
Note 1: Output window is of no use, as I do not see any meaningful error.
Note 2: I checked the solution out in another directory but same result.
Note 3: Build Machine has Windows 7 Professional SP1 in it.
Any insight to this weird behavior is appreciated.
I was able to build the solution after restarting the Build Machine. I looked into the system log to see when was the last time the computer was restarted and to my surprise, I found that it was never restarted even once. I had been using this Machine at least from 2 years.
As I wrote, restarting the PC solved the issue but I do not know the reason which helped the case here. I am guessing there were memory leaks?
Any person reading this post to solve similar issue may want to start by restarting the Build Machine.
Scenario: I hadn't been coding at home in a while and wanted to kick off my first server client application in C++ using the Visual Studio 2012 Express. But when I clicked the run button, VS froze. There was nothing wrong with the code, so I think the problem lies in some VS settings I'm unaware of, or I accidently downloaded an update which made things worse.
Issue: Hitting the play button (Debug Win32 selected) freezes the VS. Also the taskmanager gets 3 processes of the running program (none which I can interact with). Those processes cannot be terminated unless I reboot the computer.
Specs: Visual Studio 2012 Express, Windows 7, 64 bit. Avast Premier 2015.
#include <iostream>
int main() {
printf("tilt");
return 0;
}
Self-Debugging: I tried making new Hello World programs in new projects, but the issue was still there. If I opened an old project I knew worked before, it also had the same issue without me modifying anything. I changed to C# but still I couldn't run a simple program. I repaired my VS. I installed Visual Studio 2015 Community, but still cannot run any programs.
Error messages:
the process cannot access the file because it is being used by another process
visual studio could not copy exceeded retry count of 10. failed
Microsoft.Common.targets(3390,5)
Linker Tools Error LNK4098
error LNK1168: cannot open tiltTest.exe for writing
error LNK1181: cannot open input file 'kernel32.lib' //after repairing VS
Related links:
Visual Studio Hangs in debug?
Visual Studio 2015 freezes when debugging a cpp code
Windows Forms application remains alive in task manager after hitting "stop debugging" button
Visual Studio "Could not copy" .... during build
Resolving LNK4098: defaultlib 'MSVCRT' conflicts with
visual studio linker warning LNK4098
http://www.bytemedev.com/how-to-fix-visual-studio-error-the-process-cannot-access-the-file-because-it-is-being-used-by-another-process/
Final Words: I'm really bad at linking, settings, libs and anything that isn't code. So if you know how to solve it using those, please expect me to be really beginner as all that is totally confusing and illogical to me. Help would be really appreciated ! If the solution is found, I will modify this post so others will find the solution as well.
Solution: I reinstalled the Visual Studio and turned off Avast, which solved my problems! Thanks for suggestions!
Given the error message about another process using the file it could be down to the antivirus software trying to scan the files at the same time that Visual Studio is trying to access them.
I'd try turning off Avast (or any other anti virus) first. (If you're paranoid about viruses disconnect the computer from the internet).
If everything now works add an exclusion to the AV of your source folders so that it doesn't scan your code - after all you know that there are not going to be any viruses in the executables you create (right?). This will also have the added benefit of speeding up your compiles/links as the AV isn't checking the (potentially) 100's of files you could be modifying each time you build.
When I try to install the Async CTP for Visual Studio 2010 the installer fails.
I got the same problem bob mujica described in http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/2b816f97-ba1a-4342-824f-07c53f946b57.
Now Visual Studio doesn't work at all. I don't care about having CTP, I just want Visual Studio back. Does anyone know how I can do this?
Ian,
I know it won't help in this scenario but a little advice for the future that could save a lot of heartache. for the past 7-8 years, i've got into a disciplined habit of making a fresh backup (ghost) of my program partition (genarally the c:\ drive in my case) everytime i add a new program feature (other than service packs etc) to my installation. This basically means that should something 'not work' after installing, I can simply restore the ghost image over the top, rather than spend hours trying to figure why.
As i said, may not help this time but is a good discipline to work towards in the future.
My recommendation would be to install a fresh copy of Visual Studio, or perhaps to copy files from a fresh installation to overwrite any updated libraries. Assuming that you have the installation media you could also try to repair the installation from Control Panel -> Programs (Add/Remove Programs if you're still on XP).
From the linked post it sounds like either (a) a library file has been overwritten with an incompatible version or (b) a library file is referenced but not found on the system. (a) likely can be fixed by trying any of the above. (b) most likely requires VS to be removed and reinstalled from scratch. If you have a second machine around, you could try installing VS on that and dump or record the relevant registry changes and compare it with the faulty installation, but it might be faster just to reinstall.
My Visual Studio seems to be freezing/lagging when I open a existing project. I have added NHibernate framework into my code and it seems to lag my computer (at least that's what I think). When I open other projects, I do not lag or freeze at all. The freeze is about 3- seconds to a minute, then it will open my project and it will just act very slowly, it might take 20+ seconds just to switch classes an 20+ more seconds just to type a single character into visual studios.
I was wondering if anyone has had this problem before. If so how did you fix it?
I can't really work on my code until this is fixed. Oh also, when is save the code, it freezes for a good minute or two also.
You can see exactly what VS is doing at any given moment, if you attach a debugger to the devenv.exe process and hit Break when it hangs. Then load the symbols from Microsoft Symbols server and show the call stack for the VS main thread.
I wrote a very detailed article about how to debug crashes and hangs here:
http://blogs.msdn.com/kirillosenkov/archive/2008/12/07/how-to-debug-crashes-and-hangs.aspx
From the call stack it should be obvious what is causing the delay.
For me, removing the suo file (from the v14 sub directory) solved the problem...
Had the same problem. Closed Visual Studio 2010, opened again Running as Administrator, went to Extension Manager, uninstalled Nuget Package Manager, restarted Visual Studio 2010 running as regular user, opened problem solution, solution opened fine.
Nuget Package Manager seems to be the cause. My problem solution is using EF 4.3 Code First which interacts heavily with the Package Manager Console, but that may just be a coincidence.
As answer by Visual Studio 2015 Freezing White Loading Solution delete the .vs hidden directory solved the issue for me.
I am using Visual Studio 2017 Community Edition.
I had a hunch that something had been corrupted with one of my NuGet packages, and completely deleted the \packages subfolder and its contents. When I reopened the solution, all projects loaded successfully without hanging.
From there, I restored the previously deleted packages from the NuGet Package Manager Console and I was back up and running.
What, if any Add-ins do you have installed?
Edit:
One suggestion I would have then is to systematically disable each of your add-ins and see if performance changes and if it does research the culprit and see if there any updates available.
Uninstall any MS Enterprise Framework addin's you may have.
Delete the VS temp directory (and the Windows one).
Do you use TFS? Perhaps the server is a bit sleepy, that will make it freeze for a few minutes, but is ok afterwards.
For me, a chkdsk /F /R (which will prompt you to restart) and about 30 minutes of company time fixed this issue.
I think a few improperly closed instances of Visual Studio may have attributed to the issue.
I had same problem. Delete following folder.
C:\Users\UserName\AppData\Local\Microsoft\VisualStudio
My local files somehow became corrupted for one project, fortunately I didn't have any pending changes so rather than run chkdsk I just deleted the folder and checked out the solution from source control again.