Simon B 0 Posted November 29, 2023 Share Posted November 29, 2023 (edited) Hi, We have an issue with ESET Antivirus after upgrade to version 11.0.2023.0 After upgrade MS Edge browser chrashes everytime on every page we tried. It shows on multiple PC's. Firefox works fine. If I disable "Enable advanced scanning of browser scripts" option, then MS Edge starts working. Systems are Windows 10 with all updates installed. MS Edge is the latest (119.0.2151.93). Is it safe to turn off adwanced scanning ... I rather not do it. Best regards, Simon Edited November 29, 2023 by Simon B Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted November 29, 2023 Administrators Share Posted November 29, 2023 Is Edge crashing also after switching to the pre-release update channel in the advanced update setup? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted November 29, 2023 Administrators Share Posted November 29, 2023 Also please provide logs collected with ESET Log Collector when Edge is launched and running. Link to comment Share on other sites More sharing options...
Darren Sully 0 Posted November 30, 2023 Share Posted November 30, 2023 We are seeing this behaviour too with version 11.0.2032.0 on all PCs with latest Edge, Chrome is fine Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted November 30, 2023 Administrators Share Posted November 30, 2023 18 minutes ago, Darren Sully said: We are seeing this behaviour too with version 11.0.2032.0 on all PCs with latest Edge, Chrome is fine Does the problem persist after switching to the pre-release update channel in the advanced update setup? Link to comment Share on other sites More sharing options...
Darren Sully 0 Posted November 30, 2023 Share Posted November 30, 2023 It still persists, it's not a 'crashing' of edge, it starts but does not display any sites, including settings etc. If I disable Advanced script scanning it works, if then re-enable it it still works but upon reboot does not. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted November 30, 2023 Administrators Share Posted November 30, 2023 51 minutes ago, Darren Sully said: It still persists, it's not a 'crashing' of edge, it starts but does not display any sites, including settings etc. If I disable Advanced script scanning it works, if then re-enable it it still works but upon reboot does not. If you don't use Sandboxie, please carry on as follows: With browsers closed, enable advanced logging under Help and support -> Technical support Launch Edge and make sure the issue occurs Stop logging Collect logs with ESET Log Collector and upload the generated archive here (only the ESET staff can access attachments). Link to comment Share on other sites More sharing options...
necknut 0 Posted November 30, 2023 Share Posted November 30, 2023 same problem here Link to comment Share on other sites More sharing options...
Darren Sully 0 Posted December 1, 2023 Share Posted December 1, 2023 Logs as requested ees_logs.zip Link to comment Share on other sites More sharing options...
Simon B 0 Posted December 1, 2023 Author Share Posted December 1, 2023 (edited) Hi, For me it helped to do reinstall of Eset. I started new Client task Then selection version 10 .... Although selecting older version 10.X I have still left on checkbox to allow to install newer versions ... And after reinstall on clients was finished, the Edge was again working. Best Regards, Simon Edited December 1, 2023 by Simon B Link to comment Share on other sites More sharing options...
Samuel12 1 Posted December 1, 2023 Share Posted December 1, 2023 Hi, we are having the same issue here, same as Simon B and Darren Sully but with ESET Endpoint Security 11.0.2032.0. Windows 10 with latest updates and latest Microsoft Edge (119.0.2151.97). The reinstall workaround proposed by Simon B does not work, after a reboot, the issue persists. Disabling "Enable advanced scanning of browser scripts" option works. For now, rolling back to ESET Endpoint Security 10.1.2058.0 resolved the issue. SAGP572 1 Link to comment Share on other sites More sharing options...
thspranger 0 Posted December 3, 2023 Share Posted December 3, 2023 Same problem with MS Edge. Changed to pre-released solved the problem. The problem located in the secure browser module. In version 1334 of this module, the problem was solved. I‘ll go back from pre-released modules, when updates available. Link to comment Share on other sites More sharing options...
Simon B 0 Posted December 3, 2023 Author Share Posted December 3, 2023 Hi, Samuel12 is right that reinstall only helps until machine restart. I switched to pre-release and unfortunately It doesn't help for all computers ... Here I have pre-relese and web protection updated to 1339 and it still doesnt help. Machine has been restared several times. Best regards, Simon Link to comment Share on other sites More sharing options...
Simon B 0 Posted December 7, 2023 Author Share Posted December 7, 2023 Hi, has this been resolved for you all, because pre-release doesn't work for me. Thanks you all for info. Best regards, Simon Link to comment Share on other sites More sharing options...
ESET Staff constexpr 46 Posted December 7, 2023 ESET Staff Share Posted December 7, 2023 1 minute ago, Simon B said: Hi, has this been resolved for you all, because pre-release doesn't work for me. Thanks you all for info. Best regards, Simon Please wait for Browser protection module 1336 that will be on prerelease today Link to comment Share on other sites More sharing options...
Samuel12 1 Posted December 8, 2023 Share Posted December 8, 2023 (edited) Hi, Since Secure Browser module version 1336, the issue is resolved for me. Thanks to all. Best regards, Samuel Edited December 8, 2023 by Samuel12 Link to comment Share on other sites More sharing options...
Gregecslo 8 Posted December 11, 2023 Share Posted December 11, 2023 Hi. We have same issue but with Firefox. Error 0xc0000005 After pre-release updates all if fine again. When can we expect this to be released to prod? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted December 11, 2023 Administrators Share Posted December 11, 2023 3 hours ago, Gregecslo said: When can we expect this to be released to prod? We are still in the process of releasing v1335. When finished, we'll continue with gradually releasing v1336. Link to comment Share on other sites More sharing options...
Alex Eduardo 0 Posted December 12, 2023 Share Posted December 12, 2023 Any update about it? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted December 12, 2023 Administrators Share Posted December 12, 2023 3 minutes ago, Alex Eduardo said: Any update about it? Does switching to the pre-release update channel resolve the issue? Link to comment Share on other sites More sharing options...
palliett 0 Posted December 12, 2023 Share Posted December 12, 2023 1 hour ago, Marcos said: Does switching to the pre-release update channel resolve the issue? yes Link to comment Share on other sites More sharing options...
zvz 0 Posted December 14, 2023 Share Posted December 14, 2023 I spent a frustrating 10 days trying to troubleshoot my Edge browser, but finally found the solution in a Microsoft support forum. The forum provided valuable information about the problematic module… ESET this is REDICULUS !!!!!!! Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted December 14, 2023 Administrators Share Posted December 14, 2023 1 hour ago, zvz said: I spent a frustrating 10 days trying to troubleshoot my Edge browser, but finally found the solution in a Microsoft support forum. The forum provided valuable information about the problematic module… Does the problem persist? Even after switching to the pre-release update channel? Link to comment Share on other sites More sharing options...
Jochen 0 Posted December 14, 2023 Share Posted December 14, 2023 On 12/11/2023 at 6:45 PM, Marcos said: We are still in the process of releasing v1335. When finished, w After switching to the pre-release update channel everything is fine Link to comment Share on other sites More sharing options...
Nicol F 0 Posted December 15, 2023 Share Posted December 15, 2023 On 12/1/2023 at 2:10 PM, Simon B said: Hi, For me it helped to do reinstall of Eset. I started new Client task Then selection version 10 .... Although selecting older version 10.X I have still left on checkbox to allow to install newer versions ... And after reinstall on clients was finished, the Edge was again working. Best Regards, Simon I have created a policy that disables the feature, as soon as they release the updated version, I will delete the policy Link to comment Share on other sites More sharing options...
Recommended Posts