Support for Windows Vista Service Pack 1 (SP1) ended on July 12, 2011. To continue receiving security updates for Windows Vista, make sure that you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft webpage: Support is ending for some versions of Windows.
This article describes the Enhanced Mitigation Experience Toolkit. A link is provided to download the toolkit.
Known issues in EMET 5.5 and 5.51
The EMET User Guide isn't available in the GUI
The EMET 5.5 and 5.51 User Guides are available for download. In this way, we can update the guides as need. However, the guides not available in the EMET GUI.
Paste the file into the EMET directory (usually C:\Program Files\EMET 5.5" or "C:\Program Files (x86)\EMET 5.5).
EMET 5.5 GUI crashes at startup
In some cases, the EMET 5.5 GUI crashes when it's started. When this occurs, Windows Event Viewer shows a call stack that resembles the following:
Application: EMET_GUI.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Exception at HelperLib.Config.GetStringValue(System.String, System.String, Boolean) at GraphicalApp.MainForm..ctor() at GraphicalApp.Program.RunEmetGUI() at GraphicalApp.Program.Main(System.String)
To resolve this issue, use either of the following methods:
Type the following command from an elevated command prompt:
EMET ASR mitigation is logged when you open a trusted site in Internet Explorer
EMET triggers an ASR mitigation notification and an entry in the event log when you open a trusted site in Internet Explorer.
In this situation, ASR is looking for the DLL file that's being loaded into the process. For iexplore.exe, one of the DLLs it looks for is vbscript.dll. Therefore if ASR is enabled for iexplore.exe (with the default settings), when iexplore.exe loads vbscript.dll, the ASR mitigation is triggered.
To resolve this issue, make sure that the zone exclusions for Trusted Sites and Intranet Zones are configured, and that all the content that uses VBScript is associated with one of those two zones.
To resolve this issue, do any of the following:
Add the URL domain name that's triggering Internet Explorer to load vbscript.dll to the Internet Explorer Trusted Sites list.
Work with the developers of the web application that owns that URL to recode it so that vbscript.dll isn't invoked.
Create an exception in EMET ASR for iexplore.exe by removing vbscript.dll from the list of DLLs that are being monitored. We do not recommend this option.
If you have already added the URL domain name to the Internet Explorer Trusted Sites list, you may want to investigate and troubleshoot the issue. The webpage may have some redirect or iframe that's receiving code from a different URL domain name that's not in the Internet Explorer Trusted Sites list. This could cause the vbscript.dll to be loaded.
Office 2010 doesn't start when EMET is enabled in Windows 7 or Windows Server 2008 R2
EMET 5.5 and 5.51 mitigations do not apply to Microsoft Edge because of the advanced technologies that are used to protect Edge. These include industry leading sandboxing, compiler, and memory management techniques.
What is the Enhanced Mitigation Experience Toolkit?
The Enhanced Mitigation Experience Toolkit (EMET) is a utility that helps prevent vulnerabilities in software from being successfully exploited. EMET achieves this goal by using security mitigation technologies. These technologies function as special protections and obstacles that an exploit author must defeat to exploit software vulnerabilities. These security mitigation technologies do not guarantee that vulnerabilities cannot be exploited. However, they work to make exploitation as difficult as possible to perform.
EMET also provides a configurable SSL/TLS certificate pinning feature that is called Certificate Trust. This feature is intended to detect (and stop, with EMET 5.0) man-in-the-middle attacks that are leveraging the public key infrastructure (PKI).
Are there restrictions as to the software that EMET can protect?
EMET can work together with any software, regardless of when it was written or by whom it was written. This includes software that is developed by Microsoft and software that is developed by other vendors. However, you should be aware that some software may not be compatible with EMET. For more information about compatibility, see the "Are there any risks in using EMET?" section.
What are the requirements for using EMET?
EMET requires the Microsoft .NET Framework 4.0. Additionally, for EMET to work with Internet Explorer 10 on Windows Server 20121, KB2790907 or a more recent version of the Compatibility Update for Windows Server 2012 must be installed.
Where can I download EMET?
To download EMET, go to the related Microsoft TechNet page:
After you install EMET, you must configure EMET to provide protection for a piece of software. This requires you to provide the name and location of the executable file that you want to protect. To do this, use one of the following methods:
Work with the Application Configuration feature of the graphical application.
Use the command prompt utility.
To use the Certificate Trust feature, you have to provide the list of the websites that you want to protect and certificate pinning rules that apply to those websites. To do this, you have to work with the Certificate Trust Configuration feature of the graphical application. Or, you can use the new Configuration Wizard. This enables you to automatically configure EMET with the recommended settings.
Note Instructions for how to use EMET are in the user's guide that is installed together with the toolkit.
How can I deploy EMET across the enterprise?
The easiest way to deploy the current version of EMET across an enterprise is by using enterprise deployment and configuration technologies. The current versions have built-in support for Group Policy and System Center Configuration Manager. For more information about how EMET supports these technologies, please refer to the EMET user's guide.
You can also deploy EMET by using the command prompt utility. To do this, follow these steps:
Install the .msi file on each destination computer. Or, put a copy of all the installed files on a network share.
Run the command prompt utility on each destination computer to configure EMET.
Are there any risks in using EMET?
The security mitigation technologies that EMET uses have an application-compatibility risk. Some applications rely on exactly the behavior that the mitigations block. It is important to thoroughly test EMET on all target computers by using test scenarios before you deploy EMET in a production environment. If you encounter a problem that affects a specific mitigation, you can individually enable and disable that specific mitigation. For more information, refer to the EMET user's guide.
What is the latest version of EMET?
A new version of EMET was made available on July 31, 2014. For more information about the latest version of EMET, go to the following TechNet website:
Customers who have access to Microsoft Services Premier and Professional Support, can receive fee-based advisory support through these channels. Customers who do not have Premier or Professional contracts can receive support through the following official support forum:
Every major version of EMET is supported for 24 months after its release date or for 12 months after the release date of the next major version, whichever comes first. The following table displays the lifecycle of all EMET versions.
Lifecycle start date
Support end date
EMET 4. x and earlier
EMET 4. x and earlier versions are not officially supported