Im also getting crashes when the supplemental update installs and my system starts up. What is going on with Apple?Then you downgrade and restore data.
Im also getting crashes when the supplemental update installs and my system starts up. What is going on with Apple?Then you downgrade and restore data.
I ALWAYS backup prior to any updates, so no crickets here.Yeah, the minority that reads the installation instructions and follows generally accepted data management practices. I've been doing this since MacOS 9. Backup, reformat, install, migrate data. Blaming Apple for poor personal data management is just laughable. How many of you with installation issues even bothered to back up your data? Yeah? Crickets.
Im also getting crashes when the supplemental update installs and my system starts up. What is going on with Apple?
people like me, with no lives, will report back that everything is goldenPeople with no issues “minority” as you call them, have no need to post here hence all you ever read on macrumors are negative posts.
Data corruption on a clean install?You possibly have data corr
Right back at you.
It’s got nothing to do with “monthly vigs” paid by Adobe to Apple. Adobe, and many larger developers, were patently negligent when it came to coding for 64bit apps on the Mac. They had over a decade to compile for 64 bit, and move away from Carbon, and decided to do nothing.
For the record, here’s the timeline for 64bit support on Mac OS X / macOS: (Taken from Ars Technica’s excellent macOS review)
- June 2003: The PowerPC G5 CPU is the first 64-bit-capable chip to show up in a Mac, and with Mac OS X 10.3 Panther, it can theoretically address up to 8GB of RAM.
- April 2005: Mac OS X 10.4 Tiger allows for 64-bit processes under the hood—they can be spun off from another process or run via the Terminal.
- June 2005: Apple announces that it will begin using Intel processors, which are still primarily 32-bit. Whoops!
- August 2006: Apple launches the Intel Mac Pro with a 64-bit Woodcrest CPU; mainstream 64-bit Core 2 Duo Macs follow shortly afterward.
- October 2007: Mac OS X 10.5 Leopard launches with actual support for regular 64-bit apps; Universal Binaries can run on 32-bit and 64-bit Intel and PowerPC machines, covering four architectures within a single app. Unlike Windows, Apple never ships separate 32- and 64-bit versions of Mac OS X.
- August 2009: Mac OS X 10.6 Snow Leopard still runs on 32-bit chips, but for the first time everything from the apps to the OS kernel supports 64-bit operation. Snow Leopard's 64-bit capabilities are a major component of Apple's marketing push, which infamously includes "no new features." However, most systems still default to loading the 32-bit kernel.
- July 2011: Mac OS X 10.7 Lion drops support for 32-bit Intel CPUs (Snow Leopard had already ended all support for PowerPC systems). Older Macs continue to default to the 32-bit kernel and 32-bit drivers, but new Macs introduced in this era typically default to the 64-bit kernel.
- July 2012: OS X 10.8 Mountain Lion boots into the 64-bit kernel by default on all systems that support it, including a few that previously defaulted to the 32-bit kernel. In the process, a few 64-bit systems with 32-bit graphics drivers and 32-bit EFIs are dropped from the support list.
- June 2017: Apple announces macOS 10.13 High Sierra and says it's the last release that will run 32-bit apps "without compromise."
- January 2018: All new apps submitted to the Mac App Store need to be 64-bit only.
- April 2018: High Sierra's 10.13.4 update begins warning users about "not optimized" (read: 32-bit) apps the first time they're launched.
- June 2018: All new apps and updates to existing apps submitted to the Mac App Store need to be 64-bit only. Apple announces macOS Mojave, which will be the last version of the OS to run 32-bit code.
- September 2018: Apple releases Mojave. 32-bit software continues to run but with more frequent and aggressive nag messages than High Sierra.
- June 2019: Apple announces macOS Catalina, which makes good on Apple's promise to drop 32-bit software support.
- October 2019: Catalina is released. 32-bit apps no longer run on the latest version of macOS.
Mojave will continue to receive OS security updates until the release of macOS 10.17, three years from now. Plenty of time to consider migrating to other options, or investing in an older Mac to continue to run your legacy software (which is what I have elected to do, see my sig below).
There's a link to it on this Apple support page: https://support.apple.com/macos/mojave
[automerge]1571276757[/automerge]
Alongside iOS 13.1.3, Apple today also released a supplemental update for macOS Catalina, addressing several bugs from the initial public release version, including a problem with Setup Assistant hanging during Catalina installation.
![]()
Today's supplemental update comes ahead of macOS 10.15.1, which was seeded as an initial developer beta last Friday.
Article Link: Apple Releases macOS Catalina Supplemental Update With Fixes for Installation, iCloud Login, and Game Center Bugs
I've been having this issue since High Sierra then Mojave but now it happens way less. It's possible it's related to some third party apps like Adobe or others. When I called Apple they're aware of it but they're not doing anything about it.
Yes, I'd argue the early 64-bit requirement for kennel extensions was planned obsolescence on Apple's part. Macs like the 6,1 iMac and 2,1 Mac Pro were obsoleted years before they should've been because the graphics kexts were never compiled for x64, which resulted in an effective cap at Mountain Lion (though with the Mac Pro you can upgrade the GPU and use a custom boot.eft to circumvent this). The official OS these Macs are stuck at is Lion, meaning they never even got the improvements / fixes found in Mountain Lion. It was a terrible exercise of planned obsolescence that never should've happened.
Now to the topic of apps. Nothing prior to June 2017 on the timeline ever hinted at 32-bit app support leaving the OS, meaning any app compiled for Intel Macs between 2006 and June 2017 could be 32-bit without the developer having known it'll stop working in future versions of MacOS. It's not always developer laziness, sometimes the reasoning is 32-bit dependencies. Or compatibility with those old 32-bit Intel Macs, because maybe the developer thinks a simple app or utility that doesn't need 64-bit features should run on as much hardware as possible. Regardless, if you can point me to a 32-bit app built after the June 2017 announcement on the timeline, then I will happily say that is the developer's fault.
new buildI got another Safari update tonight, but it is still called 13.0.2 just like before. Same list of bug fixes too. strange.
You can call Bèta testers idiots, but they are the frontline of solving bugs & problems before you and others can install an upgrade and unknowingly be abused as a bèta tester... Not better testers than the people in the working-field.
Please, put your hands together for the public bèta testers, because they make our software useable!