ESET Insiders gisuck 9 Posted 13 hours ago ESET Insiders Share Posted 13 hours ago (edited) My computer just did an in place product update to Cybersecurity 8, and the wizard now states that I need to enable ESET Full Disk Access even though it already has it. Edited 13 hours ago by gisuck Screenshot wasn't added AlterMann 1 Quote Link to comment Share on other sites More sharing options...
AlterMann 0 Posted 7 hours ago Share Posted 7 hours ago with macOS Sequoia.0.1 too. sorry, Japanese. Quote Link to comment Share on other sites More sharing options...
ESET Insiders gisuck 9 Posted 6 hours ago Author ESET Insiders Share Posted 6 hours ago Tried a complete reinstall. It installed 7, upgraded to 8 and then encountered the same issue. I tried clicking on the + and adding the ESET application, but that also didn't work. Filed a ticket with support. AlterMann 1 Quote Link to comment Share on other sites More sharing options...
AlterMann 0 Posted 6 hours ago Share Posted 6 hours ago (edited) I try clear install. 1. uninstall ver.8 "ESET Real-time File System Protection"(OFF) Remains on System Preference>Privacy & Security>Full Disk Access 2. "ESET Real-time File System Protection" delete on System Preference>Privacy & Security>Full Disk Access. use "-". 3. install ver.8. Onboarding.app ended without any problems. From this, I imagine that macOS will not be able to recognize that "ESET Real-time File System Protection" has become new, macOS will not be able to grant permissions, and Onboarding.app will not progress. The uninstaller also has a bug that cannot uninstall "ESET Real-time File System Protection". Edited 6 hours ago by AlterMann Quote Link to comment Share on other sites More sharing options...
AlterMann 0 Posted 4 hours ago Share Posted 4 hours ago Over time, full disk access rights are lost. Is it a bug on the macOS Sequoia side? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,324 Posted 3 hours ago Administrators Share Posted 3 hours ago According to your description of the issue, it sounds like the same bug in macOS that was in macOS Sonoma: https://support.eset.com/en/kb8709. Those who are experiencing the issue, are you able to fix it by following the instructions in the above KB? 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.