I'm wondering if the installer is hung up on something, and if there's any way around this issue but today I went to upgrade this extension to the latest, and its been in the following state for the past half hour to an hour now, on a pretty quick machine (I've had this same installation finish in under ten minutes on a much slower machine than the one I'm trying to install it in now):

Is this normal? Has anyone experienced something similar? What is it trying to do in the background, because as it says, "This might take awhile." throws me off since my "while" might be a lot different than Microsoft's "while", and at what point would you consider cancelling the installation?

I'm running Visual Studio 2013 on Windows 8.1 Pro x64. All other extensions are installed and up to date.

I'm wondering if the installer is hung up on something, and if there's any way around this issue but today I went to upgrade this extension to the latest, and its been in the following state for the past half hour to an hour now, on a pretty quick machine (I've had this same installation finish in under ten minutes on a much slower machine than the one I'm trying to install it in now):

Is this normal? Has anyone experienced something similar? What is it trying to do in the background, because as it says, "This might take awhile." throws me off since my "while" might be a lot different than Microsoft's "while", and at what point would you consider cancelling the installation?

I'm running Visual Studio 2013 on Windows 8.1 Pro x64. All other extensions are installed and up to date.

• windows
• visual-studio-2013
• javascript
• visual-studio-extensions

• Mine took a while, but it did eventually install. This was the case on two different machines; both of which were i5s I am running the same Studio configuration as you. – codechurn Commented Apr 7, 2014 at 19:53
• Still waiting? I have seen these issues a lot when running with a network attached user folder. – Patrick Hofman Commented Apr 7, 2014 at 19:55
• Running 2013 myself, but this kind of installation problems isn't unmon to me. Although they tend to be very hard to analyze. – Patrick Hofman Commented Apr 7, 2014 at 20:51
• 1 You guys were right, it did finish afterall...it only took about 6 hours... – Alexandru Commented Apr 8, 2014 at 12:05
• What are your system specs? – Neil Monroe Commented Apr 8, 2014 at 22:53

5 Answers 5

Mine installed, but VS2013 still lists it as a needed update which annoys me. If I go to install it again, it gives repair or uninstall options, so I know it got installed.

In the end it pleted after a handful (~6) of hours and productivity was lost because it kept kicking off installers for all of the Visual Studio's on my machine.

So, after having to experience this heartache for a second time, I was inspired to clear out and watch my C:\Users\{username}\AppData\Local\Temp directory to see what kind of log files are produced.

In two hours time it created 360 files that occupied 642MB of space.

Judging by the types of log files it's producing, it looks like not only did it uninstall the previous version of itself but it also reapplied the VS2012.4 Update as well as the VS2013.2RC Update. What the justification is for that, the world may never know, but at least you know why it takes so long.

Hope that helps...

Use task manager to close the installer. Find Visual Studio in apps list and run it. It may say "It cannot run when setup is running" as it did for me. In that case make a new windows local account or use an existing one. And open Visual Studio. It shall run and ask you to sign it meaning its installed... Try checking it in your own account it would start running as well... well at least it did for me.

If it still didn't work try restarting your PC.

PS Use task manager only when its done downloading and starts configuring your system.

I had the same problem and it was due to one of the sub-installers launched by the main installer being stuck. Here's how I resurrected the install:

Visual Studio Express 2013 for windows with update 2 installation Taking Too much time in "Configuring Your System"