Kynyo Posted November 8, 2013 Share Posted November 8, 2013 Who knows how I can avoid this annoying protection system Link to comment Share on other sites More sharing options...
Maniac10 Posted November 8, 2013 Share Posted November 8, 2013 What's the problem with seeing that dialog only once after you install an unsigned kext? The kext is loaded after all. 1 Link to comment Share on other sites More sharing options...
Huckleberry Pie Posted November 9, 2013 Share Posted November 9, 2013 Besides being that they don't appear in Retail and/or GM afaik. The logs would churn out warnings that the kexts are unsigned, though. Link to comment Share on other sites More sharing options...
p.H Posted November 9, 2013 Share Posted November 9, 2013 Besides being that they don't appear in Retail and/or GM afaik. The logs would churn out warnings that the kexts are unsigned, though. I think it did appear in GM 603. At least for my hack. Link to comment Share on other sites More sharing options...
Maniac10 Posted November 9, 2013 Share Posted November 9, 2013 It appears in the final version (from the store) in my hackintosh. Link to comment Share on other sites More sharing options...
jamiethemorris Posted November 10, 2013 Share Posted November 10, 2013 If you add them to AppeKextExclusion(I forget the exact name), it will eliminate these console messages. However, it doesn't seem to affect anything other than that. This has been documented several times on this forum so it shouldn't be too hard to find. I'm going to bed now (lol... it's 5 in the morning here), but I'll try find a link for you tommorrow. Link to comment Share on other sites More sharing options...
cvad Posted November 12, 2013 Share Posted November 12, 2013 Who knows how I can avoid this annoying protection system Now You can use Kext Utility to install kexts and avoid this annoying protection system. KU itself adds a records about the installing kexts in the AppleKextExcludeList.kext. 1 Link to comment Share on other sites More sharing options...
Kynyo Posted November 12, 2013 Author Share Posted November 12, 2013 The main problem was that FakeSMC takes a lot to boot because of this error. Now by installing manually with Kext Utility problem is solved. Thanks cVaD 1 Link to comment Share on other sites More sharing options...
Huckleberry Pie Posted November 16, 2013 Share Posted November 16, 2013 The main problem was that FakeSMC takes a lot to boot because of this error. Now by installing manually with Kext Utility problem is solved. Thanks cVaD Hmm, I might give that a try. The HWSensors installer should've patched the exclude list too, and so should other kexts that are installed via wizards. Link to comment Share on other sites More sharing options...
Recommended Posts