Windows update 2-10-2015

[chadashcroft22]

Anybody else get an update for visual studio 2010 kb3001652 that is taking forever to install been going on for 45min on an ssd 2600k system and has not moved the progressed bar at all? Doing the same on my laptop as well.

 

[mrpete]

Yes. A friend of mine has just told me that the exact symptoms that you mentioned are happening to him.

KB3001652 is either hung or taking forever to install. Surprisingly, that update was issued in October of 2014. I don't know why it came down for him today

 

[razel]

Installed fine here. I did get a 'accept' to continue prompt which is rare. You do not need that update. It is Visual Studio 2010 Tools for Office.

 

[Whisper2]

I had the same problem. I tried to cancel after a while, but no response. I tried to restart Windows but it responded that I had to wait until the updates were completed. After about a half-hour, I pushed the reset button. I returned to Windows Update and it completed the updates without incident.

I checked Win Update history and it does not show anything for the episode. Usually, it shows "Failed" for something like this.

 

[chadashcroft22]

Yeah had to hard restart my pc and told windows to ignore the update. Fine after that.

 

[WilliamM2]

Happening to mine here at work right now.

 

[MustISO]

The Visual Studio updates have a flaw where you need to accept the license agreement which you can't see if you do it through Windows update. This happened back in December or January and was a pain in the but for our workstations. Installing the patch manually was the way to go.

 

[MustISO]

http://www.infoworld.com/article/28...1652-causes-widespread-freezing-problems.html

 

[Chiefcrowe]

Thanks for posting.. if i see this one i will be installing manually also.

 

[MustISO]

It was originally pushed out in October according to our WSUS server. Found plenty of people having issues online. I'm checking a few systems to see if it shows up.

 

[razel]

The Visual Studio updates have a flaw where you need to accept the license agreement which you can't see if you do it through Windows update. This happened back in December or January and was a pain in the but for our workstations. Installing the patch manually was the way to go.

I saw it. I guess if you don't, just don't bother to install it.

 

[Chiefcrowe]

Thanks for posting. I was updating a laptop with this one and it was taking forever (30 minutes +), so I shut down and left it, and it was still continuing to install that update. Not sure how long it took after that but eventually it did complete.
MS really needs to test these things more!

http://www.infoworld.com/article/28...1652-causes-widespread-freezing-problems.html

 

[Whisper2]

It appears this problem is quite common. Several tech sites have mentioned it. Here is one:

http://www.neowin.net/news/microsofts-patch-kb3001652-is-causing-pcs-to-lockup

The article mentions that Microsoft has pulled this update.

 

[Matt1970]

Installed fine here. I did get a 'accept' to continue prompt which is rare. You do not need that update. It is Visual Studio 2010 Tools for Office.

People should make sure that prompt isn't behind another window.

 

[Chiefcrowe]

FYI - I installed the update manually and it seemed ok.

EDIT - today I saw that windows update had this one again so it seems like MS reissued it, and it installed fine.

 

[razel]

People should make sure that prompt isn't behind another window.

It wasn't behind another window when I ran it. I suppose it could if you did other things, but in that case, Windows will still blink the window in the taskbar.

Did you actually run into that issue yourself?

 

[TheRyuu]

I got this update a few months ago as well and just blocked it then. I'm a little surprised nobody realized this was a problem in that time. Was it only sent to computers which had VS2010 installed back then or something? I don't understand why it now got pushed to seemingly more installations now.

You can "end process" on the installer process from task manager after hitting cancel on Windows Update to avoid having to hard reboot the computer and risk data corruption, in which case Windows Update will just finish whatever it already did and you can rerun it after a reboot, block the offending update and install whatever didn't.

According to one of the articles they reissued a (hopefully) working version.