this is due to the incomplete up gradation of ens 10.2 to ENS 10.5 please recheck all the modules threat protection, webcontrol and ENS platform all are upgraded to 10.5 if threat protection is not upgraded and remaining modules are upgraded to 10.5 than this will happens, for upgrading you need to run the upgrade task now option because normally its not upgraded on machines with schedule tasks.
This is what appears to be happening. Is there anyway to get ePO to properly upgrade TP to 10.5?
Try to check the randomization option on the deployment schedule task might be its work but i have check the machine and run deployment task now on these machines and its upgraded the issue is basically the conflict of threat prevention 10.2 with webcontrol 10.5 and threat prevention 10.2 script scanning option actually conflict with webcontrol 10.5 if you just uncheck the script scanning option from threat prevention from epo its resolved also but the better solution you just upgraded it to 10.5 and enable the script scanning option.
*On a system migrated to ENS 10.5, disable locally the whole module of threat prevention, and reproduce the problem. If the problem is still happening, it might be related to the firewall, then you should add as exclusion iexplorer.exe on:
Endpoint Security Firewall :Firewall > Options > My Default ---> Trusted Executables
if the problem disappears, then check:
You will see which rule is blocking iexplorer.exe, and then you should set the exclusion for the process.
If that doesn't work, follow the next articles to enable the debug mode, reproduce the issue, gather a MER, and open a ticket with support:
How to enable debug and event logging in Endpoint SecurityHow to use MER tools with supported McAfee products
NOTE: if you have web control enabled, and then you are trying to use inPrivate mode, and this is the crash you are facing, let me talk you this is an expected behaviour of the product, as inPrivate mode is not possible to upload any plug-in consequently, ENSWC not longer allow inPrivate mode.
Disabling script scanning before upgrading seems to work. Thanks!