14 DAY TRIAL // Microsoft released a total of seven bulletins as part of this month's Patch Tuesday rollout, but it appears that at least one of the updates is causing issues to a number of users running Visual Studio on their computers.
Bug reports published on Microsoft's Community forums indicate that KB3002339 fails to install properly no matter the Windows version, as there seems to be a compatibility issue with Visual Studio.
At this point, both Windows 7 and Windows 8.1 have been confirmed to be affected by the problem and Visual Studio 2012 is the only version suffering from this. There are no reports pointing to issues experienced with any other VS build number.
How to install it anyway
According to users who have already experienced this problem on their computers, installation of update KB3002339 fails to complete and it sometimes takes up to an hour to return an error.
This is undoubtedly frustrating, but users are not recommended to shut down or reset their computers, as interrupting the update process could lead to more issues.
Basically, the easiest way to deal with this problem is to hide the update from Windows Update, so after getting the error and rebooting the computer, you won't be prompted to reinstall it.
But there are some reports suggesting that manually downloading the update and installing it on PCs where this problem has been reported also solves all issues, so give this workaround a try before anything else.
Others, however, went ahead and restored their computers to make sure that KB3002339 was deployed correctly.
“I let it set for over 90 minutes on four computers the first time. Ended up having to restore the computers, hid Update for Visual Studio 2012 (KB3002339) and even then had to install the other December Microsoft updates in smaller chunks to get everything but KB3002339 installed,” one user explained.
The only botched update of the month
Microsoft is more or less used to fixing botched updates after breaking down a number of computers, as the same thing happened several times this year.
What's worse, however, is that in most of the cases Redmond needed quite a lot of time to fix the problems, so several users were left unprotected because of the issues blocking them from installing the updates.
This time, it appears that KB3002339 is the only update causing the problem, so let's just hope that the company moves a little bit faster this time to provide us with a fix.
