Search results

Also chiming in: no issues.

Best post your EFI (as a zip) so the boffins here can take a look.

Cheers for the link. My problem is not that apps get reopened (I like it that way honestly, like Mail, Tidal, Tweetbot et cetera) but that all of them now open a window and can't start hidden like under Monterey. Even my ScanSnap Manager, a program that only needs to be active in the background...

The weird portrait About This Mac and similarly ugly and frankly confusing System Preferences Settings (I don't own any iOS stuff) are what I find really ugly about Ventura. There's also little annoying stuff like the removed 'Hidden' option for Login Items, which makes Ventura open up...

Don't want to start a whole new thread but the new Monterey release 12.6.2 installed without a hitch in about 30 minutes with two reboots on my system. Now that Ventura has reached 13.1 I think I'm gonna take the plunge.

I take it the bios sees all 64 gigabytes and the right XMP profile is set? I would then try an nvram reset.

And the award for most unhelpful post goes to... This is nothing to go on. Add -v to your boot arguments to see where it snags, then provide the details.

Ah yes. I don't know if that's even possible, not without almost building your own variant of RestrictEvents. Is it really worth the hassle for something cosmetic?

You'll need the RestrictEvents kext.

Thankfully everything works and I can use the web interface to update / install, but it never just died on me like this. Small mystery but one I can live with, I think.

My installed programs work, but CC won't open with this error. Do I need to hit it with amdfriend? I'm lost, it worked fine before.

Now that it's fixed I can be that guy ;) and say you really need to keep a backup of your efi somewhere (say, on some emergency boot-usb) so you won't get caught out like this again!

PSA: there are some pretty bad holes in macOS (and mobile OS variants) that have been fixed with new patches. "Apple is aware of a report that this issue may have been actively exploited", according to the release notes. So it's imperative you get these installed as soon as possible. In case...

Are you using the latest kernel patches?

I'm not sure, but I would upgrade to 0.8.2 to be sure and also make sure you are on the latest kernel patches in case you want to upgrade to Ventura at some point.

Interesting, I got the 12.5 update offered. I made a SuperDuper backup (was about that time again) and now it isn't offered anymore. Curious... EDIT And then I got it offered again. Installed, no issues!

Haha, said it before an say it again: the new "About This Mac" is so ugly! It shouldn't matter but those orphaned words on the next lines... it's so sloppy. Is that window resizeable at all?

Unless MSI fixes some fundamental problem with their bios releases Big Sur is end of the line. There's conflicting reports that a fix is underway, but honestly I think that's a long shot unless there's some MSI dev looking out for hackintoshers...

That fugly About This Mac might even prevent me from upgrading! 😅 I can't understand why designers would allow that orphaned 'Xeon W' of 'GB' to exist.

Did you do set the ProvideCurrentCpuInfo quirk in config.plist?