macOS 15 Sequoia on Unsupported Macs Thread

[ksec]

The only solution found (Firefox) to bypass CloudFlare verification with an extra eye candy: Neptune Firefox >

Ran into CloudFlare verification issues. It seems as it currently stands after fair amount of testing.

CloudFlare verification does not work on Patched macOS with OpenCore Patcher. Orion, Safari Technology Preview, Safari Beta, and Safari itself wont work. All of these are on Webkit engine. I am on MBP Early 2015.

Chrome and Firefox works fine.

I cant seems to find much information on the internet. I assume because people are using Chrome on Desktop macOS? But if others could confirm I think this issue should be better known.

 

[air.man]

Ran into CloudFlare verification issues. It seems as it currently stands after fair amount of testing.

CloudFlare verification does not work on Patched macOS with OpenCore Patcher. Orion, Safari Technology Preview, Safari Beta, and Safari itself wont work. All of these are on Webkit engine. I am on MBP Early 2015.

Chrome and Firefox works fine.

I cant seems to find much information on the internet. I assume because people are using Chrome on Desktop macOS? But if others could confirm I think this issue should be better known.

I can confirm that my non-metal macs (iMac12,1 and MBP8,2) have the Cloudflare verification issue, while my metal MBP14,2 works flawlessly. All run Safari 18.4.

 

[OKonnel]

Due to the problems I have described in my previous posts, I have now permanently returned to Sonoma in my internal 2TB SSD and have resumed working with my late 2013 27” i7 iMac (see my signature) as smoothly and stably in everything, as if it were a new Mac.

However, out of seriousness and intellectual honesty towards everyone and myself, I'm using an external drive with Sequoia to check if the new Sequoia’s 15.5 Beta and/or OCLP updates will allow me to achieve the same stability and proper functioning of everything as with Sonoma 14.7.5

So far, instead, even with the 15.5 beta, Preview doesn't work properly, AirPlay doesn't work properly, the fan starts up often and/or for a long time, the conversion of file graphics or CODEC manifest various issue and, in general, one feels that one is using a complex system that Apple now only conceives of as a function of Silicon CPUs and for the new and complex AI developments.

So, I wonder, what is the point of agreeing to act as a guinea pig?..., I am not a hamster.... 😂😂😂

 

[ksec]

I can confirm that my non-metal macs (iMac12,1 and MBP8,2) have the Cloudflare verification issue, while my metal MBP14,2 works flawlessly. All run Safari 18.4.

Thank You. I was suspicious they are detecting some sort of WebGL / Graphics features. Wondering if you could also test https://world.org. ( A World Crypto started by OpenAI founder Sam Altman ) It is resulting in

Application error: a client-side exception has occurred (see the browser console for more information).

And on Dev Console it is showing WebGL error.

I am trying my way to get this reported to Cloudflare.

P.S - Safari 18.4 is surprisingly fast on Sequoia compared to 17 on Monterey.

 

[MacinMan]

I've already received this warning with my MacBook Pro running macOS Big Sur (without OCLP). I waited for the next application update (Amazon Prime Video) and the problem was gone...

yep. that's what I'm going to do as well. Wait for the next update. Prime video isn't something I use a lot on the computer, nor is any other streaming service, other than YouTube, but nice to have around if needed.

 

[sdds]

Sequoia runs very well on my MBP12,1 (early 2015 13" MBP), even the recent update to 15.4.1 went well. I can however not log in to my Apple /iCloud Account in System Preferences (I get an "unknown error"). Anyone else experiencing this?

 

[rehkram]

Sequoia runs very well on my MBP12,1 (early 2015 13" MBP), even the recent update to 15.4.1 went well. I can however not log in to my Apple /iCloud Account in System Preferences (I get an "unknown error"). Anyone else experiencing this?

I've seen that type of error on a couple of occasions on a 2012 rMBP10,1. Each time I rebooted and/or waited for a while before trying to log in to iCloud again. That worked for me.

 

[David403]

Due to the problems I have described in my previous posts, I have now permanently returned to Sonoma in my internal 2TB SSD and have resumed working with my late 2013 27” i7 iMac (see my signature) as smoothly and stably in everything, as if it were a new Mac.

However, out of seriousness and intellectual honesty towards everyone and myself, I'm using an external drive with Sequoia to check if the new Sequoia’s 15.5 Beta and/or OCLP updates will allow me to achieve the same stability and proper functioning of everything as with Sonoma 14.7.5

So far, instead, even with the 15.5 beta, Preview doesn't work properly, AirPlay doesn't work properly, the fan starts up often and/or for a long time, the conversion of file graphics or CODEC manifest various issue and, in general, one feels that one is using a complex system that Apple now only conceives of as a function of Silicon CPUs and for the new and complex AI developments.

So, I wonder, what is the point of agreeing to act as a guinea pig?..., I am not a hamster.... 😂😂😂

I too have gone back to Sonoma 14.7.5 .

I will maybe try Sequoia again when the final version with security updates are added several months after Sequoia’s successor has been released???

 

[iMac-Oldschool]

Update to Beta 4 (24F5068b) failed with the message rather unhelpful message "An error occurred preparing the update."
Nobody on this thread appears to encountered this problem, but various websites reported the message on supported hardware. Suggested solutions were to connect the Mac to the internet over ethernet or disable the Find my Mac function. Connecting over ethernet solved the problem. Performance is very slow on the external hard drive, but the main apps appear to work.

 

[ksec]

Google Earth Doesn't work on MacBook Pro Early 2015.

It seems there are quite a few Safari Metal issues that is preventing it.

 

[Larsvonhier]

Update to Beta 4 (24F5068b) failed with the message rather unhelpful message "An error occurred preparing the update."
Nobody on this thread appears to encountered this problem, but various websites reported the message on supported hardware. Suggested solutions were to connect the Mac to the internet over ethernet or disable the Find my Mac function. Connecting over ethernet solved the problem. Performance is very slow on the external hard drive, but the main apps appear to work.

Had this a couple of times on various machines, way before macOS 15.
It also has been covered in this thread earlier (much earlier).
The solution here was to reset NVM (via OCLP or key combo just at power-up). This helped sometimes during the re-done 2nd boot phase of the update, in other cases even the 1st stage had to be re-run (from the USB installer stick).
If you watch the log outputs in verbose mode, you can see that some read-mod-write of NVM data goes wrong until some of the old settings and contents have been zapped.

 

[Larsvonhier]

I've seen that type of error on a couple of occasions on a 2012 rMBP10,1. Each time I rebooted and/or waited for a while before trying to log in to iCloud again. That worked for me.

Check that your serial and mainboard numbers are not overwritten by OCLP (leave spoofing off in SMBIOS settings). Or, if you have faked those numbers before, try the same pair again for the patch. Apple services check those infos against their own data base to see if such a machine is rolled out at all and has been activated.

 

[iMac-Oldschool]

Had this a couple of times on various machines, way before macOS 15.
It also has been covered in this thread earlier (much earlier).
The solution here was to reset NVM (via OCLP or key combo just at power-up). This helped sometimes during the re-done 2nd boot phase of the update, in other cases even the 1st stage had to be re-run (from the USB installer stick).
If you watch the log outputs in verbose mode, you can see that some read-mod-write of NVM data goes wrong until some of the old settings and contents have been zapped.

Thanks for the reply. NVM reset did not solve the problem. Just plugging in an ethernet cable seemed like a fairly easy solution that was unlikely to cause problems.
Haven't used verbose mode very much, but will try it if the problems recurs with the next update.

 

[TOM1211]

Google Earth Doesn't work on MacBook Pro Early 2015.

It seems there are quite a few Safari Metal issues that is preventing it.

Same on mid MacBook Pro 2014 but fine in Firefox browser .

 

[hvds]

Update to Beta 4 (24F5068b) failed with the message rather unhelpful message "An error occurred preparing the update."
Nobody on this thread appears to encountered this problem, but various websites reported the message on supported hardware. Suggested solutions were to connect the Mac to the internet over ethernet or disable the Find my Mac function. Connecting over ethernet solved the problem. Performance is very slow on the external hard drive, but the main apps appear to work.

This occurs with my non-Metal MBP5,2 relatively often (about one in three times), whether doing an OTA update or from VME installer. The volume name then usually gets an extra "-Data" appended. In a few of these cases needed to erase the volume, in the others I could just repeat installing despite this undesired volume name.
Did not happen with my Metal MBP11,1.

 

[hvds]

Ran into CloudFlare verification issues. It seems as it currently stands after fair amount of testing.

CloudFlare verification does not work on Patched macOS with OpenCore Patcher. Orion, Safari Technology Preview, Safari Beta, and Safari itself wont work. All of these are on Webkit engine. I am on MBP Early 2015.

Chrome and Firefox works fine.

I cant seems to find much information on the internet. I assume because people are using Chrome on Desktop macOS? But if others could confirm I think this issue should be better known.

I have the CloudFlare problem (only) when logging in to ResearchGate pages on my Metal MBP11,1. Using Firefox in this case works.

 

[TOM1211]

Been using the 2014 Mac mini for a few days now and must say I’m impressed with it quite happy with it as a day to day machine on Sequoia with OCLP . Even if it doesn’t support the next Mac OS for the ease of use it’s perfect for me , and my next Mac will probably be a mini.

 

[sdds]

I've seen that type of error on a couple of occasions on a 2012 rMBP10,1. Each time I rebooted and/or waited for a while before trying to log in to iCloud again. That worked for me.

Thanks for sharing your experience. I've rebooted and waited few times and that did not help.
Logging in to my Apple Account using the webbrowser (FF) works fine, 2FA gets invoked as usual. 2FA never gets invoked through sys prefs. Last night I tried to look for hints in the logs but honestly don't know what to look for (what process? what possible keywords to look for?)...

 

[Pachnes]

macOS 15.4 got released 5 weeks ago, still no public beta of macOS 15.5. Apple might be busy, to prepare the OS for macOS 16, which will have a complete new design.

 

[adrianlondon]

macOS 15.4 got released 5 weeks ago, still no public beta of macOS 15.5. Apple might be busy, to prepare the OS for macOS 16, which will have a complete new design.

Public beta is available for 15.5.

Apple Seeds Fourth Beta of macOS Sequoia 15.5 [Update: Public Beta Available]

Apple today seeded the fourth beta of an upcoming macOS Sequoia 15.5 update to developers for testing purposes, with the software coming a week after...

www.macrumors.com

 

[hvds]

Public beta is available for 15.5.

Apple Seeds Fourth Beta of macOS Sequoia 15.5 [Update: Public Beta Available]

Apple today seeded the fourth beta of an upcoming macOS Sequoia 15.5 update to developers for testing purposes, with the software coming a week after...

www.macrumors.com

indeed (and also available as InstallAssistant.pkg)

 

[rehkram]

Thanks for sharing your experience. I've rebooted and waited few times and that did not help.
Logging in to my Apple Account using the webbrowser (FF) works fine, 2FA gets invoked as usual. 2FA never gets invoked through sys prefs. Last night I tried to look for hints in the logs but honestly don't know what to look for (what process? what possible keywords to look for?)...

Thinking back, what happened to me was as follows. I have set both the Macs I use here to save the Desktop to iCloud. This means I don't have to remember which Mac something is on, they both can see it.

On first login after updating the unsupported rMBP it was apparent it hadn't synced with iCloud because there were no files showing on its desktop. BTW after an update I don't like to log in to iCloud as it's booting, preferring to wait until I'm logged in to macOS successfully.

As usual, the Mac was pretty busy doing post update "stuff" at the time and activity monitor confirmed it. I figured OK, let it do what it needs to do before trying iCloud login later. That's what I did, waited for the fans to go to idle, checked activity monitor, rebooted and logged in to macOS

I don't remember whether it had automatically logged in to iCloud or whether I had to manually connect, but all the desktop files reappeared at some point.

 

[Snide]

I just bought an early 2015 MBP (3.1 GHz, !6GB, 500GB SSD), and promply upgraded to Ventura. It ran fine with no noticeable issues or slowdowns. I read many posts stating Sequoia ran just about as well, so I thought what the heck and did an upgrade to 15.4.1. First thing I noticed is it took MUCH longer to log in, and took a long time for Wi-Fi to connect with the icon grayed out. FWIW, this was originally a fresh install of Catalina - set up as new vs Time Machine or iCloud restore.

So I formatted the HD while preserving the 128GB Windows partition, and reinstalled Sequoia via the OCLP installer. Can't tell any difference with the slow log in and delayed Wi-Fi connection. Has anyone else experienced this? Any fix?

On another note, often when I boot into Windows, the curser doesn't appear, but generally will after a restart. I ask because a Windows update prevented Mac OS from booting (black screen with Apple support text). Booting from the USB drive and reinstalling the patches fixed it.

 

[Neon Ball]

I just bought an early 2015 MBP (3.1 GHz, !6GB, 500GB SSD), and promply upgraded to Ventura. It ran fine with no noticeable issues or slowdowns. I read many posts stating Sequoia ran just about as well, so I thought what the heck and did an upgrade to 15.4.1. First thing I noticed is it took MUCH longer to log in, and took a long time for Wi-Fi to connect with the icon grayed out. FWIW, this was originally a fresh install of Catalina - set up as new vs Time Machine or iCloud restore.

So I formatted the HD while preserving the 128GB Windows partition, and reinstalled Sequoia via the OCLP installer. Can't tell any difference with the slow log in and delayed Wi-Fi connection. Has anyone else experienced this? Any fix?

On another note, often when I boot into Windows, the curser doesn't appear, but generally will after a restart. I ask because a Windows update prevented Mac OS from booting (black screen with Apple support text). Booting from the USB drive and reinstalling the patches fixed it.

Sonoma/Sequoia are heavier and they're demonstrably slower especially on dual core chips like yours, anyone who says they aren't just probably has better tolerance for slowness. On a Core 2 Duo, it's even easier to witness Sonoma and Sequoia being frustratingly slow compared to Ventura and older. There is no fix OCLP can do for that.

 

[peppolone]

Sonoma/Sequoia are heavier and they're demonstrably slower especially on dual core chips like yours, anyone who says they aren't just probably has better tolerance for slowness. On a Core 2 Duo, it's even easier to witness Sonoma and Sequoia being near unusably slow compared to Ventura and older. There is no fix OCLP can do for that.

That's interesting to hear about your experience. I have a 2014 MBP myself, and I found that Sequoia is actually faster than Big Sur was on my machine. It seems like performance can vary quite a bit depending on the specific model and configuration. Perhaps it's because my model has a discrete GPU.