I am testing upgrading our enterprise environment, which is currently on 3.0 to 4.1. After installing the product with a silent install from the below directory:
waithidden msiexec.exe /i "c:\windows\temp\EMET\EMET Setup.msi" /qn /norestart
The installation works as expected, however, a bug remains: upon restarting the workstation, a Windows warning pops up briefly, indicating the "EMET Notifier has stopped working". This quickly goes away and from all appearances the notifier starts working.
The problem appears to be a remnant file left over from the installation process. EMET 4.1 installs itself to \Program Files (x86)\EMET 4.1, and removes most of the files from EMET 3.0, which were located in \Program Files (x86)\EMET\. However, the following files remain:
\EMET\Deployment
\EMET\DevExpress.XtraBars.v10.1.DLL
\EMET\Emet User's Guide.pdf
\EMET\EMET_notifier.exe
My question: why are these old files still on the root? It appears the issue is stemming from the old EMET_Notifier.exe being shut down and superseded by 4.1 - is this the case? I am looking for a transparent enterprise wide install, and would like to know what part of the installation and I performing incorrectly that is responsible for the error message. Thanks.
Also: checking MSCONFIG, I see there is an entry there to run EMET_Notifier.exe from the old directory. I have deleted the entire directory and disabled the startup item, and 4.1 seems to be running normally.