Yesterday I reported on KB 3132372, the last Windows 10 patch of 2015, released on Dec. 29. That forced patch broke Skype, HP Solution Center, Incredimail, several Serif programs, GameMaker, a bunch of games, skins for Mediamonkey, eBay Turbo Lister, and heaven knows how many other programs that still rely on Flash.
Last night -- a week after that initial patch brought down all those programs -- Microsoft released a fix. It's poetic, somehow, that the first forced Win10 patch of 2016 is entirely devoted to fixing the last forced patch of 2015.
According to the KB article (at least we got one!), KB 3133431:
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 people report that a reboot is triggered after installing the patch, although I didn't experience reboots on my PCs. There's some speculation that you're only required to reboot if you have Internet Explorer or Edge running when the patch is applied. Of course, I'd rather gargle with razor blades than run IE/Edge, so that may well be the reboot trigger.
At this point, every indication is that the patch-of-a-patch is working.
Now I'm waiting for a forced Win10 patch that knocks out even more PCs by clobbering a technology more important than Flash Player. If (when?) that happens, a week-long wait for a fix will seem like an eternity.