KB3001652 – Another Faulty Windows Update Released by Microsoft

Microsoft have yet again released another Windows Update which has caused corruption and crashing on Windows computers.

So, having spent a few hours searching for todays culprit, we found that the update causing the issue is this one:

KB3001652

It turns out that its an update for Visual Studio 2010 so it may not affect the huge amount of machines that other corrupt updates have in the past.

So, what can you do to fix it?

The simple solution is that you have to uninstall it, but you should also ensure that you have declined it in your WSUS or SCCM or other popular Windows Update system and if you are using SCCM, you could create a task sequence to remove it en masse.

If you need to know the command line for removing this update, you should try this:

C:\Windows\System32\wusa.exe /uninstall /kb:3001652 /quiet /norestart

If you have any questions or comments on this, please feel free to use our comments system below.

81 thoughts on “KB3001652 – Another Faulty Windows Update Released by Microsoft”

  1. Hi, I found this guide really helpful, but I have one question: Is it normal after clicking &#34Check for Updates&#34 to have 100+ updates ready to be installed? I have not deleted the old SoftwareDistribution folder. Please get back to me, thanks.

    Reply
  2. I have Win8 on an Acer. did the rename, that worked. had 10 updates to run. 6 critical – got stuck on first one. Rebooted, then tried to run Windows Update from desktop, said there were 4 optional updates, clicked download, it got stuck at 10%. How long should downloads take, and should I just redo the above steps and rename softwaredist folder once again?

    Reply
  3. I searched In Google &#034keep your PC on until this is done&#034 and Post seek.com was the 4th ranking which is where I found your link to these instructions. The instructions worked perfectly on my Dell laptop running windows 8.1. Thank you for this very helpful instruction compared to what I saw in the Microsoft posts.Steve

    Reply
  4. Are you definitely elevating the command prompt – not just doing it as a local administrator account?

    Reply

Leave us a message...

This site uses Akismet to reduce spam. Learn how your comment data is processed.