About Windows Installer, the .NET Framework, and Visual Studio.
Our first public release of Visual Studio Update for Microsoft Visual Studio 2013 is available. There are, however, a couple of known issues in hopefully uncommon scenarios.
We have fixed this in future versions of Visual Studio Update. This post is kept for historical reasons should any users have problems upgrading from pre-release versions of Visual Studio 2013 Update 1 to the final release bits of VSUpdate 1.
Technically, this was fixed for VSUpdate 1 RTM, but the fix has to be in the release getting upgraded, so going from VSUpdate 1 RTM to any future CTP or release bits will not exhibit this problem.
When upgrading an older install of VSUpdate 1 pre-release for Visual Studio 2013 to a newer version including VSUpdate 1 RTM, the process may run very slowly. Often times, it will appear stuck on “Microsoft Visual Studio Preparation” with the progress bar almost full.
Update: We have confirmed that this issue should not reproduce when moving from VS2013 Update 1 RTM to a newer Update build. This only affects upgrades from pre-release versions of VS2013 Update 1.
There is no current workaround that will save time. You might consider starting the upgrade before taking a lunch or heading out for the day.
In an effort to improve reliability for the product when installing or uninstalling updates, when an update is removed the base product is repaired. This, in turn, may trigger other repair operations for other add-ins or patches to Visual Studio installed with Burn (the WiX chainer). Past versions required that you do this separately or you may have problems loading VS or one of its add-ins.
When a newer version of VSUpdate, for example, is installed it uninstalls the previous version – much like a major upgrade in Windows Installer. This in turn repairs RTM. While this is most often necessary when simply uninstalling an update, it is not necessary when the uninstall occurs because of an ongoing upgrade.
This has been fixed in future versions of VSUpdate and Visual Studio, so that installing VSUpdate 2 over VSUpdate 1 does not incur the performance penalty of repairing RTM.
Saw an update, started the update, lost my whole afternoon of development and have my manager on my back. Shouldn't have click update!!! ;_; still updating 2 hours later.
This update really should come with a warning. I had to let it run overnight to complete.
Thanks for the explanation, my upgrade took 90min :-/
And they wonder why nobody wants to update any Microsoft product, since it's so painful.. not to mention risky.
Earlier this week Android Studio told me there was an update. I clicked on "update", and before I returned with a coffee the IDE was ready for me to work on.
No reboots, long downloads, roll-backs, or re-installing dependencies in a certain order - It just worked! And this is pre-release.
Please stop with the punishment - it's no longer worth it.
VS is very slow and Microsoft does not care that is what is wrong
Seriously, 3 effing hours. Not like its for an assignment that's due tomorrow or anything. I shoul dhave stuck with PHP like EVERYONE else in my class. No wonder everyone hates microsoft.
Never had any problem upgrading Android Studio.
Never had any problem upgrading xcode.
Just with MS products. Ever been like that. Ever will be.
Heh, that “Microsoft Visual Studio Preparation” is also happening now when I do upgrade from Update 2 RC to Update 2 RTM. It just hangs there for an hour already.
This also happens when you try to remove a feature from the installed base. I tried to remove and re-install Lightswitch... which gets itself seriously upset if you install a new SQL2014 Developer edition... why who knows.
But really annoying that this happens.
Will try the Update 2 upgrade before I try to get Lightswich working again. Please can someone in MS look at this whole localDB vs Developer DB version is realy sucks to have so many databases installed... :(
Just letting you know that this fix appears to have been reverted. VS2013 Update 2 is also slow - taking several hours, and there was no pre-release versions in the mix. Perhaps you test on SSD's and we deploy it foolishly on laptop hard drives ?
@VS2013 Update 2 is also slow, please run http://aka.ms/vscollect and upload %TEMP%\vslogs.cab to a share so we can investigate. This has not been the norm.