Last updated on April 1st, 2023 at 07:49 pm
So, having spent a few hours searching for todays culprit, we found that the update causing the issue is this one:
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.
If you want to be notified when we post more quality guides like this one, sign up to our free subscription service and you will receive an email when a new post is live.
No need to worry, we will not be filling your inbox with spam and you can unsubscribe anytime you like.