PeZzy Posted April 20, 2017 Report Share Posted April 20, 2017 Antivirus/Anti-Malware programs are silently preventing the Adobe Flash control panel from opening in Windows 10 Creators Update. In EIS 2017.3.1.7353, I have to exclude "FlashPlayerCPLApp.cpl" and "FlashPlayerApp.exe" in order to open the Flash control panel. https://forums.adobe.com/message/9456894#9456894 Link to comment Share on other sites More sharing options...
GT500 Posted April 21, 2017 Report Share Posted April 21, 2017 Do you know if it happened on 32-bit Windows 10 or 64-bit Windows 10? Link to comment Share on other sites More sharing options...
PeZzy Posted April 22, 2017 Author Report Share Posted April 22, 2017 Mine is Windows 10 Pro 64-bit, Version 1703, OS Build 15063.138 I use Flash with Firefox. Link to comment Share on other sites More sharing options...
GT500 Posted April 22, 2017 Report Share Posted April 22, 2017 OK, thank you for letting me know. One of our forum moderators let me know that they ran into the same issue, so we'll have to look in to why it is happening. Link to comment Share on other sites More sharing options...
stapp Posted April 22, 2017 Report Share Posted April 22, 2017 @PeZzy Could you post a screenshot of how those Flash Player exclusions look in EIS Exclusions Panel? Thanks Link to comment Share on other sites More sharing options...
PeZzy Posted April 23, 2017 Author Report Share Posted April 23, 2017 I realise entering it under scanning exclusion was unnecessary. Link to comment Share on other sites More sharing options...
stapp Posted April 23, 2017 Report Share Posted April 23, 2017 I am using EAM on Creators Update and, like you, cannot open Flash Player settings manager from Control Panel. I have entered the same Flash related exclusions as you have above and even rebooted (just in case!) but still cannot open the Flash Settings manager. I have the same Event Viewer error as is mentioned here https://forums.adobe.com/thread/2303130 Perhaps in my case it is not related to EAM. I will keep looking. Link to comment Share on other sites More sharing options...
GT500 Posted April 25, 2017 Report Share Posted April 25, 2017 I was going to test this over the weekend, and every time I installed the Creators Update in my test environment it ended with a black screen. It appears to be an issue with VMWare Tools in the version of VMWare Workstation that I have, and I will have to try again without VMWare Tools installed. That being said, our QA team did test our products extensively with the Creators Update, and no issues with the new update were found. That being said, they don't normally install third-party software when testing our products with new updates to Windows. Link to comment Share on other sites More sharing options...
GT500 Posted April 27, 2017 Report Share Posted April 27, 2017 Issue confirmed and debug information collected. Currently only excluding FlashPlayerApp.exe from monitoring is necessary to prevent the crash. On 32-bit editions of Windows it will be in the following location: C:\Windows\System32\FlashPlayerApp.exe On 64-bit editions of Windows it is in the following location: C:\Windows\SysWOW64\FlashPlayerApp.exe 1 Link to comment Share on other sites More sharing options...
stapp Posted April 27, 2017 Report Share Posted April 27, 2017 I did it a slightly different way (I always choose the hard way ) I turned off Emsi service and was then able to open the Flash Player settings manager in Control Panel, also provided debug logs https://support.emsisoft.com/topic/27249-flash-player-settings-in-control-panel-using-eam-on-creators-build/ At least now the devs will be able to fix this. Link to comment Share on other sites More sharing options...
Recommended Posts