StooIT

If you don't want to go on the pre-release channel, you could temporarily disable the "Enable advanced scanning of browser scripts" in a policy, and apply it only to the machines that need the fix.

Same here, running 1334 and IE Mode no longer crashing with our legacy web app. 
Hopefully 1334 will go live soon, as I don't really want to put everyone in to a pre-release channel  

I tested on VM with Outlook 2016 and module 1334, looks like issue fixed. Requested to check users on their computers, who had issue with previous module.

Issues with IE compatibility mode in Edge should be resolved with the Browser protection module 1334 currently available on the pre-release update channel. If the new module doesn't resolve your issues, please raise a support ticket for further troubleshooting and investigation.

I made tests:
1. Windows 11 23h2 eng + all updates (build 22631.2715) + Office 2016 x64 RTM (no updates) + ESET ES 11.0.2032.0 - No issues with web add-ins.
2. The same as #1 + installed all updates to Office 2016, build 16.0.5422.1000 64-bit, add-ins started to crashing in Outlook.
3. The same as #2, but in ESET policy disabled option "Enable advanced scanning of browser scripts" - no more crashes. Users confirmed, that issue gone for them too.

As there's been zero response to this thread from ESET directly, I raised a ticket to report this as a bug. 
For others out there wondering why this isn't working anymore, here's the official response from ESET.
If you want to see this functionality returned, please raise a ticket asking for it to be fixed. If more customers report this, the better the chance of it being sorted out. 

If customers don't want this functionality, they can disable update warnings in the Management Agent policy. 
 

Good day,
Has anyone here found a way to run powershell scripts on client systems with elevated privileges so that system customisation would be possible? 

Hello @Rob Schember,
I assume that the computers are managed by ESET PROTECT / ESMC / ERA, right? 
 
I would first check the Action after scan in the scheduled tasks.
The policy / settings corruption might happen in 3 scenarios, see https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510/?do=findComment&comment=153054 for details.
If the issue occurs on your ESET PROTECT management console you need to
1. switch it to pre-release update channel to get the fixed Configuration module 
2. Manually fix the policies / scheduled tasks (if the policy is already corrupted, the Configuration module 2011.5 is not able to repair it, thus the manual fix is needed)
Please do not edit the policies using the older Configuration module, as it might cause further issues 
 
If it won't help, get an ESET Log Collector output from the affected machine, upload it to a safe location and send a private message with download details to me and Marcos to check with a reference to this post.
 
If correctly-looking policies would apply incorrectly on Endpoint 9.1 , the problem should be solved automatically (by just updating).
Peter
 

We have a fixed module (Configuration module 2011.5) prepared which will be rolled out today to the pre-release channel. You can temporarily switch to the pre-release channel until the module is fully released next week, or you could manually copy it to the root folder "C:\Program Files\ESET\ESET Security\Modules" in safe mode (it will have to be removed from there when fully released).

This should be unrelated to the issue discussed in this topic. Please report it in a new topic and provide logs collected as follows (only ESET staff can access attachments):
Please carry on as follows:
Enable advanced logging under Help and support -> Technical support Start logging with Procmon Reproduce the issue Stop logging Save the Procmon log and compress it. Collect logs with ESET Log Collector and upload both archives in the forum topic.  

Hello @JimChev3,
it has been reported at 
https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510
https://forum.eset.com/topic/32896-latest-endpoint-security-reboots-itself-after-updateagain/
I would recommend to check those for further updates.
We apologize for the inconvenience caused by it.
Peter

I've already raised the "Failed to copy files" under ticket 00388505, so will wait to hear back from that. 👍

We believe that we have nailed it down to the Configuration Engine 2011.4 that has been distributed to a couple of hundreds of ESET PROTECT users since yesterday so far. What is weird is that the module had been available for millions of Endpoint users without any such issue reported. We are working on it hard to figure out the cause and to bring a fix as soon as possible. We apologize for the inconvenience.

Hello guys,
our technology and tech support teams are on it, we are investigating this with a priority.
We probably already identified the module version causing the issue.
 
We apologize for the inconvenience caused.
Peter

As there's been zero response to this thread from ESET directly, I raised a ticket to report this as a bug. 
For others out there wondering why this isn't working anymore, here's the official response from ESET.
If you want to see this functionality returned, please raise a ticket asking for it to be fixed. If more customers report this, the better the chance of it being sorted out. 

If customers don't want this functionality, they can disable update warnings in the Management Agent policy. 
 

Thanks for the heads-up. This is a known issue which will be fixed in the next service release of ESET PROTECT / ESET PROTECT Cloud.
P_EP-25800