Now Reading
KB3133431 Windows Update fixes the Flash Player crashes caused by the botched KB3132372 Update

KB3133431 Windows Update fixes the Flash Player crashes caused by the botched KB3132372 Update

by AshwinJanuary 7, 2016

KB3132372 Windows Update won’t be forgotten by Windows 10 users, at least not in the near future.

KB3133431 Windows Update
This is because the patch, which was originally intended to fix security issues in Adobe Flash Player for Microsoft Edge and Internet Explorer, instead saw itself become a thorn for many a user.

The update instead caused many apps to crash, especially, when they were used to access/play some sort of Flash based content. Microsoft did warn that the update could cause a few crashes, but did not detail on how much exactly was “a few”.

As it turned out, it was quite a few, read our previous report about it to know more. While the Redmond company and Adobe were figuring out a fix for the issues, the only workaround was to uninstall the KB3132372 Windows Update to prevent the crashes, but this of course meant that the browsers were at risk. But fortunately, you no longer have to uninstall the update to fix the crash issues.

Microsoft has silently (read sneakily) released a new patch which fixes the above mentioned issues. The new patch is called the KB3133431Windows Update, and has already been rolling out to all users, since January 6th. I actually didn’t notice the update, until InfoWorld reported about it.

This is what the change-log (bit shocked that one exists) for the update says:

This update resolves a problem in which Adobe Flash Player does not load correctly in applications that are running in Internet Explorer or Microsoft Edge and that have Flash Player embedded. This problem occurs after security update 3132372 for Adobe Flash is installed on Windows 10.

Some unconfirmed reports suggest that the KB3133431 Windows Update makes the computer reboot automatically, probably for the Update to finish installing. We do hope that this isn’t the case, because that is extremely intrusive, but then again it is Microsoft, so you know.

The reboot triggers are said to have occured only when Microsoft Edge or Internet Explorer was opened, and it does seem logical, since they are the two browsers are the ones which need to be patched. And obviously since they are system components, they need be patched while they aren’t being used.

But honestly, a prompt to save your session, we need to patch the browser, could have been a much simpler, and efficient idea.

On a sidenote, if you install a language pack after the KB3133431 Windows Update was installed, you must reinstall the update.