Warning to Windows 7 users

Hello. I'm sure you pretty much already solved this issue if you've been keeping up with your updates, but I'd just like to clarify a few things.

NOTE: If you are running anything other than Windows 7, this bug does not exist, and will not cause your PC any potential harm. If you are also experiencing no problems with windows updates, then your PC has not received the bug, and your update (KB3024777) has already deleted it. You may discard this thread if any of these mentioned apply to you.

On December 10th, 2014, there was a Windows Update called "KB3004375" which included bug fixes, however it created a bug that did not allow future updates. This is only true for a few Windows 7 users. I happened to be one of them. It all depends on if your PC handled update KB3024777 correctly. It was assigned to immediately uninstall update KB3004375. However, some users didn't have this, so they will have to manually uninstall KB3004375 like I have. Go to your Windows Update page and check your last check for updates and when they were installed. Should look something like this:



Click on "Installed Updates" in the bottom left corner. It should take a while to load all your previous updates if you've been updating correctly. Type in the search bar "KB3004375", and right-click and Uninstall all of the programs that have "(KB3004375)" at the end of their name. Once you've done this, restart your PC and you should be able to update to future updates.

Source: http://answers.microsoft.com/en-us/...b3024777/88369b50-80df-4a1b-90ed-a5a95f80a868

 

uhh I own windows 7... and usually all the updates only happen once I turn off my computer but there was this one (the most recent one) that FORCED me to shut it off in 15 mins or less or it would reboot... so I decided to get it over with... I better go check right now if this was that one you speak of.


edit: just checked, I'm safe. it didn' t install any such update thankfully.

 

Thank god I didn't have it

 

My computer can play games.
I'm good

 

Would also like to note that update KB3004394 should be handled in the exact same way, as this was another buggy update stated by the source provided above.