I had this error with almost every boot into Monterey.
I upgraded to Ventura (not without other problems), had to wipe and reinstall, and have not seen it since.
Mine wasn't that smooth! Ventura slowed down massively after the recommended Software Update path, so I wiped and installed Ventura from a USB, bringing my data partition back using CCC. No problems since.
I had a few, but the 9560 plowed through unattended and booted after a couple of...
I rarely use my touchscreen, but you prompted me to check.
I upgraded to 13.1 after significant difficulties. I update kexts with OCA and have VoodooI2C 2.7.1 and VoodooI2CHID 1. I am set up with a huge 4K monitor run through the DP of a TB16 dock. My touchscreen works on both the external...
My 9560 had been chugging along pretty well until I started having problems with iCloud. I am asking for help here because some of the symptoms keep changing.
When I first set it up, it was clear that upon startup, my wifi dongle (en0) had to connect first to make things good with Apple; I have...
It's a kext. Interestingly, I started getting the error again, although far less often, and when I checked my config.plist to reply to you it had been turned on. I'll try turning it on again.
<dict>
<key>Arch</key>
<string>Any</string>...
I don't remember where I read it now, but I was getting the error at every boot. The advice was to disable FeatureUnlock. I did so and haven't seen the error in several reboots.
I have good news in that I got Monterey 12.4 to work. However, after I upgraded OC to 0.8.1 and my kexts with OCAuxiliary Tools, my 4K external monitor wouldn't connect, either using DP via my TB16 dock or directly by HDMI.
Reverting to my backed-up 0.8.0 EFI folder fixed it. Can you experts...
Thanks for all the help. While I could get Monterey running on the external SSD, it would not install on the internal one, so I went back. OC seems to be an improvement, except that it's not clear how to set up legacy booting for my Windows and linux partitions.
Should I use rEFInd? Put Clover...
Thanks, it was and is enabled. So then the output of VerifyMsrE2.efi shown in my photo above is not a problem because AppleXcpmCfgLock just circumvents it? That's what was unclear.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.