Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
I ALWAYS backup prior to any updates, so no crickets here.

Additionally, not everybody who comes to this forum is a MacHead power geek user. So, prior to tossing everybody under the bus, think.
 
Need to fix Books!
Getting...

The operation couldn't be completed.
(BKAgentServieErrorDo,ain error 8.)


Anyone have help?

Thanks!
 
Catalina running great on my 2017 iMac but terrible issues running on 2019 MacBook Air. The worst update from Apple in years!!!! :rolleyes:
 
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).

excellent and informative post. I’ll have to check Catalina installation I have on my 2012 iMac for macOS version but I didn’t realize/thought that High Sierra was launched using “macOS” moniker vs OSX. Maybebecause it felt like OS X to me vs Craig’s macOS.
 
Also, how can a clean install generate more kernel panics than an upgrade from Mojave to Catalina?
 



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.

catalina_island.jpg

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
[automerge]1571276757[/automerge]
Holy hell.....Catalina was was an awful update. Never again. Relearned my lesson. Will wait a few months each time going forward and let others go through all of this....
 
  • Like
Reactions: Babygotfont
Heres another question. For those that aren’t getting daily kernel panics, do you have multiple monitors? I am fresh out of ideas here as to what’s wrong.
 
  • Like
Reactions: Babygotfont
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.

I only ever had it happen on Mojave, but I usually just close it then close the app itself, but yes its annoying.
 
I figured out how to reproduce this kernel panic issue consistently. It’s always when my monitors go to sleep. If I use the computer without taking breaks, it won’t cause an issue. Any thoughts on this?
 
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.

I'm sorry but you're completely wrong in thinking/stating that developers for the OSX/macOS platform did NOT see nor was ever informed prior to 2017 that 32-bit apps was going the way of the dodo!!

please do some research ... actually someone already linked arstechnica's history of OSX/macOS since the PowerMac G5 and OSX Panther launching 64-bit support on the CPU and in the OS with 32-bit Rosetta support as a beginning pre-cursor fo things to come.

Lazy and non-aspiring and experience developers and teams failed and well that's what you get.
 
Silly question probably...but if we download Catalina from the Mac App Store today, will we get Catalina with the supplemental update (since it has fixes for installation) or the original release?

:apple:
 
Bad experience for iPhone/iPad update and restore, no progress bar, no status bar and no even firmware download status

Edited: Can't manage my phone or ipad backup if no iOS device connected
 
Certainly the buggiest update I've experienced in 17 years of Mac ownership - Sidecar connects to iPad, but only shows a black screen, Apple ID constantly asking me to log in, something gone very wrong with bluetooth where it randomly disconnects all devices but also causes warbling audio issues (a significant issues when running webinars for work), and its also borked webex screen/app sharing (webex insists their app is up to date and compaitble, so issue is on my side).

All in all, really wish I'd waited, some pretty major issues for me (although mail, music etc etc are all fine :) )
 
I updated my work and home computers to Catalina, I'm an early adopter. Work has been fine, but I use iTunes for mixes, and syncing music has been horrible in Catalina, I would make a change on a playlist on my Mac, and it would not update on my phone. I'm not sure if the supplemental update addresses that, but they need to fix. Home Mac is back to Mojave....pending the fixing of the Music app.
 
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!

Well, if it is OK for you, that Apple nowadays is using everyone as a beta tester, than that's fine.
It looks like the companies are doing it these days and it is considered normal. Well, for me this is not, at least not something, than can cause harm to you or your [put here whatever word you want*]

* like data

I always wait, that the "dust settles" and then I move on. And only then install a new operating system if it seems, that everything will work for me.
 
I updated to Catelina and most things are working fine but I had a lot of issues with OBS because I saw something asking to grant mic and keyboard access to SH and I denied it becuase I had no idea what that was. I was able to get this working by updating the security settings after I figured out what happened. The other issue I had was my machines had trouble going to sleep and would just stay on and this update seems to have resolved that issue.

My only outstanding issue is OBS is not recognized as a trusted developer so I can't install any updates but I can run the current software fine. I'm hoping they resolve this but for now at least I can use the software so I'm okay with things. I don't have too many other issues but I also transitioned to mac fairly recently so pretty much all of my software purchases were already 64 bit so YMMV. There is a way to easily check what software is compatible before you do the upgrade so I would definitely suggest that but I didn't have too many issues with this part of it.
 
I did not jump in right away with updating to Catalina. Then I saw the supplemental release and thought, OK, maybe this week I'll update. But after reading this and other posts across several sites, it looks like maybe in the new year after one or two more update releases, I'll consider downloading. I was looking forward to some of the newer changes and improvements that Catalina has but I do not NEED them right now. I did wait on Mojave so I think this is going to be my MO for all OS updates.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.