2 ms·
I've got the same on a stock M1 MBP. At some point in the past I've disabled SIP - probably when I was playing around with FUSE. Did all the Betas - never had
by mbirth 2y ago
I've got the same on a stock M1 MBP. At some point in the past I've disabled SIP - probably when I was playing around with FUSE.
Did all the Betas - never had any problem. However, after installing the RC/final version of Sequoia, I suddenly had a popup after bootup about an updated extension from "Apple Inc." and to please allow the updated version.
In Settings --> Privacy I was able to "Allow" the extension, however, this also requires a reboot. And after the reboot, the same popup appeared again.
I've put in a ticket - FB15087179.
Apple replied and said to first, toggle Activation Lock/Find My and wait 5+ minutes in-between. (Either off - wait 5mins - on, or on - wait 5mins - off.) Then boot into the bootloader and turn SIP on, then back off again.
However, when trying to turn SIP on, I get the same error as OP:
SDErrorDomain error 104.
I've found another user on Twitter with the same issue: https://x.com/davidhsherman13/status/1833264669793923151 https://x.com/davidhsherman13/status/1833264669793923151
After reporting my findings in the Apple Feedback thing, I've yet to get further instructions to try.
- mbirth 2y agoA Reddit user found a solution: https://old.reddit.com/r/MacOSBeta/comments/1fhl39c/system_extensions_issue_with_latest_beta/lo4v4hc/ https://old.reddit.com/r/MacOSBeta/comments/1fhl39c/system_e... I've noticed he disabled "Find My Mac" in the first step and only enabled it again after everything was done. This seems to be the key. I suspect the "SDErrorDomain error 104" is related to the "Activation Lock" aka. "Find My Mac". I've disabled Find My Mac, booted into recovery and was finally able to set it to "Full Security" and back to "Reduced Security" again without problems. After that and a fresh boot, the popup message about the updated extension was gone. Enabled "Find My Mac" again (after setting the system to "Full Security" first - as that's the setting I intended to use) and all is well. nb. SIP was enabled for me the whole time. It was the security mode running on "Reduced Security" (both checkboxes checked) which was probably the cause for the "updated extension" issue.