G11 1 Report post Posted February 18, 2015 Running latest stable release EIS on Window 7 Pro SP1. Why does it create a custom rule for Explorer.exe. Since this is part of windows shouldn't it be all allowed. EDIT: Manually changed status to "all allowed" and custom rule is now gone. Quote Share this post Link to post Share on other sites
Fabian Wosar 390 Report post Posted February 18, 2015 If a custom rule for explorer.exe was created, then the file was not recognized as being part of Windows. This is usually the case when the file was patched or changed. There are many legitimate reasons why this can happen. A lot of UI skinning and customization tools will patch Windows executables to make certain visual alterations. It could also be that your explorer.exe was infected by a virus in the past and the tool you used to clean the infection was unable to restore the file properly. If it doesn't show up as infected, I wouldn't worry too much about it though. Quote Share this post Link to post Share on other sites
G11 1 Report post Posted February 18, 2015 Okay, that explains it. Did clean Windows install, installed EIS then all the security updates after EIS, Quote Share this post Link to post Share on other sites
Fabian Wosar 390 Report post Posted February 19, 2015 Thanks for the feedback, G11. If you run into any other issues, please let us know . Quote Share this post Link to post Share on other sites
