Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacUse-R

macrumors regular
Original poster
Dec 24, 2017
185
21
Haven´t found an answer to this exact question when searching online, but on my M2 Mac with MacOS Sonoma (14.2.1), when i go to "System information - Software - Extensions" all Apple Kext are reading as "not signed".
It also says: "Validation Failures: Kext has a CFBundleExecutable property but the executable can´t be found....."

And that is the case with almost everything listed in "Extensions", except a very few.

On my 2011 High Sierra Mac all of these are signed by "Apple code signing certification authority, Apple root CA"

And the kexts in question does not have executables when looking at them with "show package content", but the High Sierra mac has executables in all of the kexts.

So is this how its suppose to be on Sonoma, or on the M silicon Macs?
 
Haven´t found an answer to this exact question when searching online, but on my M2 Mac with MacOS Sonoma (14.2.1), when i go to "System information - Software - Extensions" all Apple Kext are reading as "not signed".
It also says: "Validation Failures: Kext has a CFBundleExecutable property but the executable can´t be found....."

And that is the case with almost everything listed in "Extensions", except a very few.

On my 2011 High Sierra Mac all of these are signed by "Apple code signing certification authority, Apple root CA"

And the kexts in question does not have executables when looking at them with "show package content", but the High Sierra mac has executables in all of the kexts.

So is this how its suppose to be on Sonoma, or on the M silicon Macs?
It’s normal, and because the entire system volume is signed and sealed, it’s not a problem.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.