Chas4 10 Posted June 13 Share Posted June 13 2nd click on an item and none of the ESET context menu items do anything Full updated Win 11 & updated ESET Internet Security v17 Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,267 Posted June 13 Administrators Share Posted June 13 On Windows 11 the shell extender menu is added as an app package using a PowerShell cmdlet Add-AppxPackage. Since further investigation is required, we recommend that you raise a support ticket. Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 13 Author Share Posted June 13 Just now, Marcos said: On Windows 11 the shell extender menu is added as an app package using a PowerShell cmdlet Add-AppxPackage. Since further investigation is required, we recommend that you raise a support ticket. It worked in the past, and the context menu items show fine, but look to be all broken Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 13 Author Share Posted June 13 Case 00775388 Included logs in the case Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 14 Author Share Posted June 14 So far they have not wanted to help and actively avoid helping trying to push it to someone else, first email I got from them they failed to read a word of the ticket. Quote Link to comment Share on other sites More sharing options...
Anne_W 0 Posted June 20 Share Posted June 20 I have the same problem. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,267 Posted June 20 Administrators Share Posted June 20 On 6/13/2024 at 7:10 PM, Chas4 said: Case 00775388 Included logs in the case I read that you have a general problem opening ESET's gui based on your statement "the ESET GUI does not open at all", right? So it's not just a problem with the context menu when you right click a file. Egui.exe is running according to the logs. Is it that you are not seeing the ESET icon near the clock? Or when you double click the icon the gui doesn't show up at all? Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 20 Author Share Posted June 20 4 minutes ago, Marcos said: I read that you have a general problem opening ESET's gui based on your statement "the ESET GUI does not open at all", right? So it's not just a problem with the context menu when you right click a file. Egui.exe is running according to the logs. Is it that you are not seeing the ESET icon near the clock? Or when you double click the icon the gui doesn't show up at all? None of the context menu items work, nothing happens when you click any of them, some v17 update or module update broke the context menu code I can open the ESET gui fine other ways Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,267 Posted June 20 Administrators Share Posted June 20 Did you try turning off integration in the context menu, saving the settings and then turning it on? Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 20 Author Share Posted June 20 Just now, Marcos said: Did you try turning off integration in the context menu, saving the settings and then turning it on? I did already and nothing changed Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,267 Posted June 20 Administrators Share Posted June 20 Does the problem occur when you select Show more options: and then try to run a scan via both options in the menu? Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 20 Author Share Posted June 20 (edited) 2 minutes ago, Marcos said: Does the problem occur when you select Show more options: and then try to run a scan via both options in the menu? Those work fine You have already done 200 times more troubleshooting than the support team, who wanted to try the nuclear option. Modern context menu is broken, classic one is not Edited June 20 by Chas4 Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,267 Posted June 20 Administrators Share Posted June 20 Please try the nuclear option and uninstall / reinstall ESET since it's the only option that the developers can recommend at this point. Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 20 Author Share Posted June 20 5 minutes ago, Marcos said: Please try the nuclear option and uninstall / reinstall ESET since it's the only option that the developers can recommend at this point. Can they double check the code that the modern context menu actions are not commented out or disabled, as I am not the only one seeing this bug? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,267 Posted June 20 Administrators Share Posted June 20 We were unable to reproduce the issue and it works for us alright. We will welcome if other users share their findings here as well. If uninstallation and reinstallation does not make any difference, it's likely one of many bugs in this new shell extender menu that Windows 11 has introduced and Microsoft has yet to fix. Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 20 Author Share Posted June 20 @Marcos Quote Link to comment Share on other sites More sharing options...
Anne_W 0 Posted June 20 Share Posted June 20 6 hours ago, Chas4 said: Those work fine You have already done 200 times more troubleshooting than the support team, who wanted to try the nuclear option. Modern context menu is broken, classic one is not That worked for me as well. The problem might be due to the recent update in Windows 11, I guess. Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted June 21 Author Share Posted June 21 I test with the same file and notepad worked fine from that menu (notepad is not part of the OS but a Microsoft Store app) Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted July 9 Author Share Posted July 9 Not fixed in version 17.2.7.0 update Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,267 Posted July 9 Administrators Share Posted July 9 5 minutes ago, Chas4 said: Not fixed in version 17.2.7.0 update It is unclear where the issue lies. It's very likely a bug in Windows itself as we didn't find anything wrong in the code. There have been several bugs with the new shell extender on Windows 11 already and probably not all have been fixed by Microsoft yet. Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted July 9 Author Share Posted July 9 6 minutes ago, Marcos said: It is unclear where the issue lies. It's very likely a bug in Windows itself as we didn't find anything wrong in the code. There have been several bugs with the new shell extender on Windows 11 already and probably not all have been fixed by Microsoft yet. All the other items in the modern context menu work fine tho Sent Process Monitor recording to support Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted August 6 Author Share Posted August 6 So far support has not done much of anything and ignoring that it is just ESET context menus that are broken in the modern context menu. Was told Process Monitor recording failed to capture it and never received instructions on how they want it captured, I asked for instructions for a 2nd time. Being asked about unrelated things in logs I sent them. Quote Link to comment Share on other sites More sharing options...
Chas4 10 Posted August 7 Author Share Posted August 7 Case 00775388 support has refused to help and called me a liar and lied to me. I am requesting and escalation since na support refuses to investigate even after sending requested info Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.