You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Apple kernel extensions are not signed after installing Ventura on MacBook Pro

Just made clean installation of macOS Ventura from USB stick over Big Sur, preserving Bootcamp partition.

I was really surprised, seeing that the Apple OS kexts are not signed and not loaded (most of them).

Is it normal situation, or should I immediately wipe out this installation?

(Intel MacBook 2018/32G/1Tb/Rad560x)



[Re-Titled by Moderator]

MacBook Pro 13″, macOS 10.14

Posted on Aug 2, 2023 2:20 AM

Reply
Question marked as Top-ranking reply

Posted on Mar 19, 2024 10:09 AM

Kurt Lang wrote:

Agreed. But I figured simply saying eugene's statement was "wrong" wouldn't mean much without clarification.

It doesn't mean anything at all. Eugene left the chat almost 9 months ago. Your metacarpals will turn to dust long before you ever manage to "clarify" anything to cyber-stalker. You will fail - guaranteed. He will be back in a month, or a year, asking about kernel extensions, ClamXAV, EtreCheck, with a new alias if this one gets banned too. The only winning move is not to play. Do not respond. Do not challenge. Do not insult. Do not engage at all.


If you sincerely want to try anyway, I would humbly request that you do it in Usenet, where you and his other disciples can spend your golden years in endless rounds of mutual insults and stalking side-quests.

Similar questions

23 replies

Aug 2, 2023 6:07 PM in response to eugene.davidson

eugene.davidson wrote:

Is it normal situation, or should I immediately wipe out this installation?

It's normal. The operating system lives on a cryptographically signed snapshot. For compatibility reasons, there are stubs of various files in the normal filesystem. But the actual executables aren't present. Therefore, when you check the code signature, it fails. But that's OK, because none of these extensions are actually loaded from those locations. They are loaded from one of the other system locations. That's why none of those extensions are reported as loaded, because they aren't. But if you check using kmutil, you'll see that many of them actually are loaded.


Apple kernel extensions are not signed after installing Ventura on MacBook Pro

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.