I have been trying to install Visual Studio 2017 RC for the past two hours but so far, I have not been able to install any version of Visual Studio. I have tried looking around for solutions, but so far nothing.
Here's an image of running the installer. This is about as far as it goes.
After doing this, the installer just exits and kills itself and no installation happens. Waited for a while and nothing happens. No installer applications running in both task manager and resource manager, so I'm assuming it right after it reaches that.
Any ideas?
EDIT:
This computer is clean and has never install or attempt to install any version of MS Visual Studio before.
[1/17/2017, 16:12:46] === Logging started: 2017/01/17 16:12:46 ===
[1/17/2017, 16:12:46] Executable: C:\Users\xxxxx\Downloads\vs_Community.exe v15.0.26020.0
[1/17/2017, 16:12:46] --- logging level: standard ---
[1/17/2017, 16:12:46] Directory 'C:\Users\xxxxx\AppData\Local\Temp\2a6df70b7a7d7cb06efead\' has been selected for file extraction
[1/17/2017, 16:12:46] Extracting files to: C:\Users\xxxxx\AppData\Local\Temp\2a6df70b7a7d7cb06efead\
[1/17/2017, 16:12:47] Extraction took 828 milliseconds
[1/17/2017, 16:12:47] Executing extracted package: 'vs_bootstrapper_d15\vs_setup_bootstrapper.exe ' with commandline ' '
[1/17/2017, 16:12:49] The entire Box execution exiting with result code: 0x0
[1/17/2017, 16:12:49] Launched extracted application exiting with result code: 0x2
[1/17/2017, 16:12:49] === Logging stopped: 2017/01/17 16:12:49 ===
I had the same problem, and it turns out that some part of the installation was trying to read from a config and failing. After running it a few times, it eventually created a folder called "VSFaultInfo", and it contained a ConfigurationErrorsException.
My problem was that I edited my machine.config at one point, and the installer was getting an exception from trying to read from it. It installed when I undo-ed the modifications I made. My config was located under "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config", but it might be different for you. Try to delete it or find a VSFaultInfo folder on your computer.
Most Visual Studio installer problems since VS2012 are caused by corrupt packages that is has downloaded. The log file you posted suggests this might be the case.
The packages are downloaded to the temp directory in user accounts \AppData\Local\ folder as indicated in the log file. I would suggest that you clear out all files in this directory and run the installer again, triggering it to re-download required packages which are hopefully no longer corrupted.
Refer to the error message, the installation met issues when extracted or launched the package. Make sure windows update is up-to-date, temporarily disable any antivirus software, clean up the %temp% folder, then re-run the VS 2017 installer as administrator.
In you have tried to install any VS 15 preview versions or re-install the VS 2017, you can perform a manually uninstall like the following:
Go to Control Panel—Programs and Features, if there have ‘Microsoft Visual Studio 2017’ or ‘Microsoft Visual Studio Installer’, right click it and choose ‘Uninstall’
Try to delete the following installed folders: (you can back up those folders before any modification, in case we need to roll back)
• Go to the folder: %ProgramData%\Microsoft\VisualStudio and delete the ‘Packages’ folder
• Go to the Visual Studio installation folder (normally under %ProgramFiles(x86)%\Microsoft Visual Studio) and delete the folder ‘2017’ or ‘VS15Preview’ if you have
After the uninstallation, then re-download the VS 2017 RC and run as administrator.
I finally figure out a problem after over an ENTIRE week of searching and messing around with settings. I can actually do my homework normally now (whoo hoo...).
Like so, I have tried everything you guys have said to no avail, although the solutions you guys have provided did solve some of my classmates' problems, so thank you for that.
So here is what I did:
Press Start (windows icon) + R to open up the 'Run' window.
Type in services.msc to open the 'Services' window.
Scroll down and find 'Windows Management' Instrumentation, right-click it, then click 'Start'.
Look at the 'Startup Type' and see if it says 'Manual (Trigger Start).' If it does not say that, right-click on it, click on properties and set the 'Startup Type' to automatic.
Run the installer as an administrator and install.
So if anybody has this problem, try enabling services. Some of these services are required in order for Windows to actually allow the application to install. In this case, it was a service which retrieves information from the computer in order for the installer to install properly.
I disabled this service previously in order to improve hard drive performance, with no awareness that it restricted me from installing software.
Cheers!
I noticed I had unknowinly messed up with machine.config
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG
I reverted the changes to default and the installation started well at last.
I downloaded the full ISO for Visual Studio Ultimate CTP 6. The installation program got to about the 90% mark, gauging by the progress bar, and just stuck there. There was frequent activity from Superfetch, Anti-malware protection, and other background processes, but the progress bar was dead still. Eventually the background task activity subsided after 20 minutes, but the progress bar still wouldn't budge.
CHEAP TRICK: Open a notepad window and position the left edge of it so it perfectly marks the current position of the progress bar. If it the progress bar doesn't move past the left edge of the notepad window in about an hour, it's probably stuck.
This was a case of one of the sub-installers getting stuck during the install and never completing. Unfortunately when this happens, it looks like the master installer never times out the operation. The trick is to open up the Task Manager in detail mode, and look for a sub-installer process that is showing 0% CPU usage and 0% disk usage, indicating it has died. Then just kill that process and the master installation will resume. In my case, the name of the sub-installer was SecondaryInstaller.exe and according to the installation log it happened while it was trying to install some Android SDK components for the cross platform development modules. It had frozen permanently. I killed it and the master installer completed. When I ran Visual Studio it was fine, although I'm guessing I'll have to do some digging on the Android components install problem.
I temporarily disabled my antivirus (AVG) and restarted the install. That fixed it.
The current version of AVG Free antivirus is incompatible with Microsoft Visual Studio 2015.
It does not allow Visual Studio to be installed on the computer. It gets stuck at "Creating restore point". Visual Studio installs perfectly when AVG is turned off.
Any code compiled in "Release" mode targeting x86 platform/environment (in project properties) does not compile. It compiles successfully when AVG is turned off.
I posted the issues in AVG support forum but no one responded.
Same thing happened to me, and I also tried to terminate secondary process from task manager. Do not do that. It is not a solution, but rather a hack which may cause issues later. In my case, I was not even able to uninstall Visual Studio. I tried both web installation and ISO, same issue.
Here is how it worked finally. I restored my Windows 7 to earliest restore point as possible, when there was nothing installed, so I was sure that there would be no conflicts between the different tools (Java, Android API, etc.)
I started the installation of Visual Studio 2015 Community Release Candidate at 10 p.m. At 7 a.m., it was working on Android API 19-21. A hour later, it was finally preparing Visual Studio.
This means that all you need to do is to actually wait 8 to 9 hours. Don't terminate the secondary installer at risk of breaking your Visual Studio; just wait.
During the installation if you think it has hung (notably during the "Android SDK Setup"), browse to your %temp% directory and order by "Date modified" (descending), there should be a bunch of log files created by the installer.
The one for the "Android SDK Setup" will be named "AndroidSDK_SI.log" (or similar).
Open the file and got to the end of it (Ctrl+End), this should indicate the progress of the current file that is being downloaded.
i.e: "(80%, 349 KiB/s, 99 seconds left)"
Reopening the file, again going to the end, you should see further indication that the download has progressed (or you could just track the modified timestamp of the file [in minutes]).
i.e: "(99%, 351 KiB/s, 1 seconds left)"
Unfortunately, the installer doesn't indicate this progress (it's running in a separate "Java.exe" process, used by the Android SDK).
This seems like a rather long-winded way to check what's happening but does give an indication that the installer hasn't hung and is doing something, albeit very slowly.
I had the same problem when I tried to install VS 2015 RC from ISO. It got stuck during Android SDK Setup (API Level 19 & 21, System Images). For me the problem was metered Wi-Fi connection. The installer didn't download necessary files.
Turning off the Internet connection resolved the problem. When installation finished, it said that some components were not installed and it will try to download and install them later.
Check if your Windows has pending updates. After the restart, installation worked as expected.
Alright so after hours of googling and failed attempts at solving this including many of the suggestions above, I found a solution I tried on a whim and worked for me.
Attempt to install the program, then, when it gets "stuck", cancel it, but don't uninstall.
Then, go to the control panel, go to programs, go and attempt to uninstall it, select "Repair" instead of Uninstall.
"Repairing" Visual Studio appears to have completely worked and was very quick, under 5 minutes and everything seems to work fine.
This issue is becoming very now, specially for users installing visual studio on windows 10 platform. What Microsoft suggests is disable your anti virus and anti malware programs and always run setup with admin permission.
But in my case I have to do lot more things to get rid of this issue:
1. Disabled AVG realtime protaction
2. Disabled AVG from task manager
3. Remove all the files and folders from system temp folder. (You can open it by typing %temp% and hit enter in run prompt)
4. Run setup again as admin
Here is a complete list of incidents that I faced in this issue (visual studio 2015 installation got stuck)
And how I resolved it
I got stuck during Android SDK Setup (API Level 19 and 21) Turning OFF and ON the Internet connection resolved the issue and the installation completed successfully.
My VS 2015 install hung after hours of downloading. The VS installer window said it was still proceeding, but Windows Resource Monitor indicated there had been no networ, disk, or CPU usage by the vs_community.exe process tree for dozens of minutes. Windows Process Explorer revealed wusa.exe at the bottom of this tree (wusa is Windows Update Standalone Installer). Tempted to kill wusa.exe, I instead heeded the warnings in other answers to this question.
After studying other answers here (strongly recommended), I made an educated guess and initiated a restart of my Windows 7 Pro. The restart hung because vs_community.exe would not exit. I therefore selected Cancel on Windows' restart popup.
Windows returned to my user session, and now the VS 2015 install came to life(!) Process Explorer revealed wusa.exe no longer present. I therefore suspect that was the roadblock, but my conscience is clean (I didn't kill wusa.exe, Windows did!)
After awhile the installer displayed the following:
When I clicked Restart Now, Windows restarted to a "Configuring Windows" screen, and completed my VS install.
This solution is a safe mix of killing the sub tasks answer and the waiting answer:
when the installer gets stuck, simply launch the task manager and kill the process
if you attempt to run the app again, it will say that the app installation is not complete
run the installer again, and click on repair
installs fine
When stuck on Visual Studio Preparation:
I killed vs_enterprise.exe with higher PID, Visual Studio threw an error, that "pipe is being closed". Restarted PC & Logged in. Visual Studio started automatically and has completed within 1 minute.
A better approach to find whether one of the subinstallers is blocked is to monitor its Network and Disk I/O activity. Process Explorer from Sysinternals does an excellent job. Android SDK Setup downloads large amounts of data (more than 1GB) and the CPU sits idle waiting for an I/O-bound operation to be completed. Under no circumstances you should attempt to kill any process, or you might risk corrupting your installation of Visual Studio. In the worst case scenario, cancelling and rerunning the setup should help.
Mine froze on the Diagnostic Tools for 3 hours. I tried disabling my firewall and turning off internet among many other attempts to resolve this. In the end the following actions allowed the installer to complete and VS2015 Community edition to launch.
I then opened the latest log file in the %temp% folder, and navigated
to the end of the file.
In the last few log lines there was an entry: "MSI (s) (DC:4C)
[16:28:36:577]: Created Custom Action Server with PID xxxx"
I ended the process with the same PID, and then the installer
continued. I had to do it roughly 3 times in total and then the
installer completed successfully.
All seems to be working OK so far (fingers crossed!!)
For Windows10:
1) Kill VS2015 Process if hung
2) Disable Windows Defender
3) Open VS2015 as Administrator
4) Enable Windows Defender
5) Initial VS2015 startup is complete
I have similar problems, my savior became Windows Safe Mode
STEPS:
Restart Windows in Safe Mode (*run msconfig -> boot -> boot options -> check safe boot -> mode Network)
In Safe Mode:
Enable Windows Installer:
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\MSIServer" /VE /T REG_SZ /F /D "Service"
Start Windows Installer service:
net start msiserver
Run Visual Studio Updater / Installer
Restart in normal mode (run msconfig -> boot -> boot options -> uncheck safe boot)
I had an issue with the Visual Studio Update 3 installer getting stuck on the "Features" tab at ther very start of installation...it would show only "Update 2 (installed)" and nothing else, with no way to proceed.
After trying some of the other more complex advice here, it turned out, to my surprise, that all I needed to do was use "Run as Administrator" when kicking off the installer. I was under the impression MSI generally runs with Admin privileges (under the Trusted Installer service) but I suppose the VS bootstrapper in this case does not.
I had the same issue. It would hang immediately, as soon as it said "Applying Microsoft Visual Studio 2015." There was only a small sliver in the progress bar. I even let the install run overnight. There was no disk activity or CPU usage from the installer.
What finally worked was to kill the process in Task Manager and restart the computer. As soon as I rebooted, the installer opened up automatically and completed successfully.
In my case the Graphics Tools Windows feature installation was hanging forever.
I've installed the Optional Windows Feature manually and restarted the setup of VS 2015.
I just installed VS 2015 Enterprise on Windows Server 2012 R2. The install was fast until it reached Update 1 which is past the 90% mark on the progress indicator. At that point, it took about 2 hours to complete. Be patient before you try anything more radical.
Mine got stuck applying the .NET 4.6.1 blah... Turning off the internet and disabling Microsoft Security Essentials Real-time protection got things moving again.
Well, I cant find any SecondaryInstaller.exe to stop in task manager and even I dont have any AV rather then Windows Defender so I found something else..
I stopped windows Update from elevated cmd by writing command net stop muauserv and it worked for me...
The update will Retry again for KB2664825 so run the code again in cmd..(because the service starts automatically)
Keep trying and its done for me...!!
I had the same problem on a different context. After trying to repair, uninstall, and reinstall with no solution, I decided to wipe out all Visual Studio remnant by using TotalUninstaller by follower the steps by steps on the link below:
https://github.com/Microsoft/VisualStudioUninstaller/releases
Once everything is removed, I was able to successfully install the software.
Be aware that TotalUninstaller will remove everything related to Visual Studio 2013 to 2015. Earlier version will still be preserved.
I added this solution in case someone has the exact same problem.
I've got same problem and unfortunately the accepted answer which suggests killing SecondaryInstaller.exe messed up installing the optional items. What I've done is basically opening the task manager and locate SecondaryInstaller.exe and right click and click on Open file location. Then run SecondaryInstaller.exe as an administrator.
In my case UAC was disabled (the infamous regedit trick) and so the installer clearly could not handle it.
You could revert back to UAC for the installer, or simply try launching it as admin, it worked for me.
If you are using windows 10, "Windows defender" might be the reason for blocking. mine is hang while installing "Java SE development"
To disable windows defender during the installation phase:
Open Windows Defender by clicking the Start button Picture of the Start button. In the search box, type Defender, and then, in the list of results, click Windows Defender.
Click Settings, and turn off Real-time protection.
I have experienced similar problems with Visual Studio 2015 Update 3.
In my case core issue was corrupted windows installer cache (C:\Windows\Installer)
Here is the line from msi installer log:
MSI (s) (4C:64) [10:40:10:059]: Warning: Local cached package 'C:\WINDOWS\Installer\3442502.msi' is missing.
You should check installation logs if installation cache is corrupted same way.
If it is you should pray for sfc utility to recover system integrity or you would reinstall windows from scratch as corrupted windows installer cache is a complete disaster and a reason to perform clear windows installation immediately.
I had a similar problem. My solution was to switch off the antivirus software (Avast), download the .iso file, mount it (double click in the Windows Explorer on the .iso file), and then run it from the PowerShell with admin rights with the following switches:
.\vs_community.exe /NoWeb /NoRefresh
This way you don't have to go offline or remove your existing installation.
For me it helped to stop the installation service forcefully using task manager. If Visual Studio was installed in Features & Programs then uninstall it, restart computer and try to install it again.
When starting the installation make sure to be have reliable internet connection
My Visual Studio began crashing at start-up. In my search for finding a remedy, I found these two suggestions, but neither worked for me:
Launching Visual Studio while running in safe mode, and
Running repair on Visual Studio.
However, I found that if I logged into a different Windows account, Visual Studio was able to run from that account without crashing.
Here is an error code that that I observed in the crash report:
LCID: 1033
Can anyone provide a solution for returning my Visual Studio to working order?
For me it turned out to be the plugin that GitExtensions installed into Visual Studio 2013.
-- UPDATE: try this before uninstalling GitExtensions
#Enceradeira proposed in the comments to uncheck the Show current branch in Visual Studio option. In GitExtensions, you get there via Tools -> Settings -> Appearance:
-- END OF UPDATE
After uninstalling GitExtensions and reinstalling it with all VS plugin unselected my VS runs smoothly again.
I even put together a blog post about this issue because it bugged me so much.
Since you're able to run with another user login, something may be wrong with your local settings, you can try to reset them: devenv /resetsettings in Start menu -> Run.
Warning: this will restore visual studio to default settings.
In my case VS used to crash on a single solution. I resolved the problem by deleting the respective solutions's user file: SolutionName.suo
My colleague recently experienced a problem with Visual Studio 2013 crashing on start-up. Unfortunately, we found that the approach recommended in the answer by #Arun M did not solve the problem:
devenv.exe /ResetSettings
...however, using a different command line argument did:
devenv.exe /ResetUserData
An easy way to run devenv.exe is via the Visual Studio command prompt; on Windows 10, it can be found here:
Start Button => All Apps => Visual Studio 2013 => Visual Studio Tools =>
VS2013 x86 Native Tools Command Prompt
For more about these command line arguments for devenv.exe, see this answer to this related question: How do I truly reset every setting in Visual Studio 2012?. ⚠ In particular, please note the cautionary statement in that answer about the /ResetUserData command line argument!
Try to run VS as administrator. That's necessary in my case.
If coincident to these Visual Studio crashes you are getting "Heap corruption" (Exception code: 0xc0000005) errors in your Windows Application log (Faulting module name: WindowsCodecs.dll), here is something worth checking into: A faulty WIC component within Expression Blend can cause ALL versions of Visual Studio to crash upon launch, as well as cause Internet Explorer to crash upon visiting many, if not most sites. Even though Microsoft distributes this component, they call it a "non-Microsoft component". As such, a Visual Studio reinstall won't fix this,, an OS reinstall over existing Windows installation won't fix this, and a system file integrity check won't detect it.
If my case, the misbehaving codec was "C:\Program Files (x86)\Microsoft Expression\Common\Imaging\4.0.360.0\PSDCodec.dll", and simply unregistering this component got my Visual Studio working again from consistent startup launch crashes.
I post this in hopes this solution to one source of Visual Studio crashing might save others from the $500 Microsoft support incident fee and week of downtime this caused me.
I just changed the windows language in the bottom right to "EN", then started as admin. And it worked, interesting..
I had the very strange phenomenon that both Visual Studio 2010 and 2013 on a Windows 7 machine crashed when run in a remote desktop session, started from a Windows 10 pc. Debugging the crash showed a CultureNotFound exception. It was caused by regional settings on the Windows 10 pc, which could not be translated in something understood by Windows 7. I had language English(Belgium) with an Azerty keyboard. I added and selected English(UK) with an Azerty keyboard and the crashes disappeared. No other programs suffered from this.
For me it was being caused by Web Essentials and I was able to resolve by disabling it, restarting VS, enabling it back , restart again. Works now.
I had a crash on startup (or soon after startup, before opening any solution) occurring in git2-msvstfs.dll, caused by placing a 3GB temp file into a directory within my solution. Deleting the file fixed it.
Once I accidentally pressed a random key combination (maybe something like ctrl+', but I didn’t realize I was holding ctrl down so I forgot what keys I hit by the time I realized something bad had happened) that resulted in VS Professional 2017 15.3.5 crashing within half a minute. After relaunching, I found that VS would be interactive for a few seconds before it would crash within half a minute. It was really too fast for me to try to figure out what I had accidentally activated or for me to disable it before VS would crash. Also, it would even crash if I didn’t open any solution, so I figured it was not something that deleting a .vs (per project/solution Solution Explorer/open files state) folder would fix.
To fix, I followed Arun M’s comment and renamed my %LOCALAPPDATA%\Microsoft\VisualStudio\15.0_3f4d04be folder. You will need to adjust the path for the edition/version of VS that is crashing. On my machine, I think 15.0_3f4d04be is Professional and 15.0_0fed6c59 is VS Community Edition. You’ll probably have to guess based on the folder’s modification timestamp which is probably going to reflect the date you last used that edition of VS.
After renaming the versioned dotfolder, VS launched without crashing. It started with default settings but automatically restored some of my settings through the cloud sync stuff after a minute of running and it even remembered my account information so I didn’t need to sign in.
I did not need to rename my %LOCALAPPDATA%\Microsoft\VSCommon folder (which Arun M had also suggested).
I had a similar problem, both VS2015 and VS2013 would crash at startup. Tracked it down to an application I installed which put .net 4.7.2 on the system. Once i removed that app, removed .net, and reinstalled .net 4.6, Visual Studio started working again.