Office 2010 won’t start with EMET enabled, bug in KB 3146706 and KB 3125574

Topic

New Reply

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
[See the full post at: Office 2010 won’t start with EMET enabled, bug in KB 3146706 and KB 3125574]

Reply | Quote

Replies

Haven’t seen this one myself. Running Office 2010 and EMET on two laptops. Both have had KB3146706 installed for almost two months. No issues on either.

But I’m still running EMET 5.2. Maybe only manifests with EMET 5.5? KB3163644 doesn’t say. (But it should.)

And then we have a supposed workaround: “Disable EFT flag in EMET for Office 2010”.

OK… but what the HEX is the “EFT flag in EMET”?! Not mentioned in *any* EMET manual I can find. And Bing can’t find any info on it, either. (Google helpfully suggests maybe I mean “EAF”. Well, maybe I do, but only MS really knows for sure.)

Yet *another* stellar piece of documentation from MS. (And the grammar isn’t so good, either.)

Reply | Quote

this sounds similar to what i wrote here: https://www.askwoody.com/2016/an-official-fix-for-slow-windows-7-update-scan-times/comment-page-2/#comment-89474 (Malwarebytes AntiEyploit has shield settings which are similar to the ones in EMET.) I didn’t try with Office 2010, though; but just disabling AntiExploit did the thing for me for IE, FF & Chrome, while EMET 5.5 ran untouched.

@Woody: EFT Flag ?? Typo or trash ?

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

Reply | Quote

Not sure what you mean by EFT Flag….

Reply | Quote

EFT-Flag:

Workaround: To work around this issue, you can do one of the followings: · Disable EMET for Office 2010. · Disable EFT flag in EMET for Office 2010.

(from: https://support.microsoft.com/en-us/kb/3163644)

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

Reply | Quote

AHA! I don’t know if that workaround will work with this new incarnation. Good question!

Reply | Quote

The Flag to disable is EAF & EAF+. This will let Office 2010, 2013, and 2016 run, even with EMET configured for ‘Maximum Security’.

Reply | Quote

I had EMET installed few years ago when there was a known Internet Explorer vulnerability for which Microsoft did not have a patched yet, but was recommending EMET instead with Group Policies configured for that purpose.
After few weeks when the vulnerability was patched through the regular Windows Update, I uninstalled EMET and never used it since.
I found it too complicated to configure and maintain, with too many issues like this one which is described in this blog post.
I am not sure why regular people use EMET, but I would be interested to know more about its usefulness which would counterbalance the annoyances which I already mentioned.

Reply | Quote

EMET 5.52 is released and it seems to fix that
https://www.microsoft.com/en-us/download/details.aspx?id=54264

EMET 5.52 is a minor update from EMET 5.51 to address the following:
• An issue with the EAF mitigation that causes some applications to hang on Windows 7 SP1.
• A fix to the MSI installer to allow in-place upgrade behavior.
• Removed EAF+ mitigation for Chrome from “Popular Software.xml”
• Fixed import behavior for System Mitigations.

Reply | Quote