Newsletter Archives
-
Office 2010 won’t start with EMET enabled, bug in KB 3146706 and KB 3125574
Just saw this:
https://support.microsoft.com/en-us/kb/3163644
Microsoft Office 2010 doesn’t start when EMET is enabled in Windows 7 or Windows Server 2008 R2
Symptoms
This issue occurs when the Enhanced Mitigation Experience Toolkit (EMET) is enabled and security update 3146706 or convenience rollup update 3125574 is installed.Resolution
To fix this issue, install June 2016 update rollup for Windows 7 and Windows Server 2008 R2.Thanks to Susan Bradley.
-
Two April patches, KB3146706 and KB3147071, break AppLocker when used for whitelisting on an Admin account
From AB-
Two updates from April effectively break AppLocker, if you’re using it as an additional security measure (whitelisting) on an admin account.There’s some more info in this thread: http://www.wilderssecurity.com/threads/applocker-in- windows-7-silently-changed. 385669/ It’s not something that affects a lot of people, that’s why it’s probably gone unnoticed. But for the few of us who did use it, it’s potentially a lot of trouble. -
Does the new version of KB 3146706 cure the EMET-clobbering predilections of its predecessor?
I don’t know, and Microsoft isn’t saying.
InfoWorld Woody on Windows
-
Is Microsoft using security patch KB 3146706 to break pirate copies of Windows 7?
More evidence – and an English description of the mysterious “Ghost” pirate version of Win7, prominent in China.
An accident? Or a fortuitous attack vector?
InfoWorld Woody on Windows
-
Win7 security patch KB3146706 causing problems?
I’m seeing lots of reports of MS16-044 / KB 3146706 throwing errors – most commonly blue screen 0x0000006B – that go away if the patch is removed.
Remarkably, almost all of the reports (for example, this one on site vvcat) are in Chinese. Makes me wonder if there’s a conflict between KB3146706 and a program that’s commonly run in China. We saw something similar three years ago with KB 2823324, which triggered BSODs on many computers in Brazil.
AskWoody denizen LL wrote to me and said that it looks like Microsoft is still distributing the patch through Windows Update, but isn’t checking it — which is typically a precursor to yanking the patch entirely.