![]() ![]() It's not really feasible to expect end users to/will do this. ![]() If your Mac is using an outdated third-party extension, you may see a system alert. Say you have 1000 macs (or more) in your enviornment. On a Mac with Apple silicon, you may first need to use Startup Security Utility to set the security policy to Reduced Security and select the Allow user management of kernel extensions from identified developers checkbox. ![]() "To work around this issue, authorize the kernel extension again". Then saying upgrade to 10.13.6 as the fix.ģ. So if the Mac is on 10.13.6 there should be no issue? That seems contradictory to saying the issue does not occur on 10.14. Right after that it says to upgrade your Mac to at least 10.13.6. If the issues does not occur on 10.14 should we upgrade the mac's to 10.14 BEFORE updating SEP?Ģ. I have a few questions I was hoping anyone could answer.ġ. To work around this issue, authorize the kernel extension again. To resolve this issue, upgrade your Mac to at least 10.13.6. This issue does not occur with macOS 10.14. However, you already authorized the kernel extension on macOS 10.13. Kernel authorization unexpectedly required by macOS 10.13.x after an upgrade to version 14.2 or laterĪfter you upgrade your Mac from Symantec Endpoint Protection 14.0.x to 14.2 or 14.2 MP1, a prompt to allow the Symantec Endpoint Protection kernel extension appears. After you upgrade your Mac from Symantec Endpoint Protection 14.0.x to 14.2. Looking at the release notes for 14.2 MP1 and it mentions: Kernel authorization unexpectedly required by macOS 10.13.x after an upgrade. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |