Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This is the first Apple OS update I'm not going to install for a long time, if ever. Maybe if I ever buy a new machine. I had several application lockup problems, and that's not even counting 32-bit being removed, which i find more of a problem than that! And to top it off, my Time machine backup was messed up. I had to actually mount the sparse bundle and get at the backup data that way because the migration asisstant ran for days "loading backup" and ending up doing nothing, and I couldn't go back further than the install time by using time machine.
 
  • Like
Reactions: The Barron
Interesting idea - does this work? Has anybody tried this?
I tried it, but I had too many video crashes in the VM, what I wanted to run, wouldn't. I didn't try VMWare Fusion, that may have worked. I got sick of the problems, flattened the whole machine and reinstalled mojave...
 
  • Like
Reactions: VulchR
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).
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.
 
What a dog, hope it matures soon.

Another thing that's got my goat (?) is the insistent hawking of Apple services scattered around the OS.. Music, TV, iCloud... I'm sorry, but I don't like this kind of solicitation and would prefer paying money for an OS than this.
 
  • Like
Reactions: DeepIn2U
if you rely on 32bit apps, keep using Mojave, its going to be supported for another three years.

All developers have known since Snow Leopard, Apple would be switching to 64bit and ditching 32bit.

That what gets me. These developers have known for years that 32-bit has been deprecated but they just don't seem to care until they start getting nasty letters from users. Dymo has such a lock on the market they feel like they can do whatever they want.
 
  • Like
Reactions: The Barron
What a dog, hope it matures soon.

Another thing that's got my goat (?) is the insistent hawking of Apple services scattered around the OS.. Music, TV, iCloud... I'm sorry, but I don't like this kind of solicitation and would prefer paying money for an OS than this.

I don't mind the additional services, but they're bonus features. The OS itself has to work properly and right now it doesn't. I'm considering cancelling iCloud Drive and Apple Music until that's the case.
 
  • Like
Reactions: hrpuffnstuff
I have no problem of the ones mentioned in this thread (Im commuting so I have a lot of time to kill).
All apps works even illustrator cc 2018 Adobe things will not work and Papers3 (works better in Catalina).
The only app that does not work is media button enabler.
One person run into problems at work with the installation but he had very little free space on his boot ssd.

Im just lucky guy (MacBook Pro 2018 and 2012)
 
  • Like
Reactions: hrpuffnstuff
I did my upgrade after 4 download attempts, 3 of which ended with "deleting download" type messages and the install itself went fine, none of the Icloud issues or anything else. This was on an early 2015 Macbook Pro, pre exploding batteries.
I did have two casualties, I had to upgrade my VM Ware Fusion for for 80 bucks (kept getting black screens) and I had one 32 bit program I had deleted before the install, Scrivener. I should qualify this and say I tend to do a clean install and reinstall of software every year or so which helps.
Apple should have given an option to run 32 bit software much like when Windows 7 was installed you had a copy of Windows XP you could run inside it
 
Running 10.15.1 Beta (19B68f) and thank god it fixed the memory leak in the music app that caused constant crashes for thousands , lets hope they included it in this release for the general public. My music and movies are in a total mess after Catalina.

You are not alone. Mine was a disaster - but this update looks to have fixed the issue. Seeing my 32gb ram screaming for mercy as Mojave was using 98% capacity isn't much fun. 98% of 32gb!!! o_O
 
  • Like
Reactions: hrpuffnstuff
I've been thinking about upgrading, but am concerned about no support for 32-bit apps. I still occasionally use Dreamweaver CS5 (very occasionally), but am most concerned about games. Steam says it's 32-bit only on the system report, though I understand there is a 64-bit version available. I'm not sure about Rocket League or some of the older Call of Duty games I occasionally boot back up.

How big of a deal have people found that? This is the first time in a long time I haven't upgraded almost right out of the gate.
 
What a dog, hope it matures soon.

Another thing that's got my goat (?) is the insistent hawking of Apple services scattered around the OS.. Music, TV, iCloud... I'm sorry, but I don't like this kind of solicitation and would prefer paying money for an OS than this.

Props if your dog reference was related to the mistyped “kennel extensions” in the preceding post. :)

Personally, I’m holding off for at least a month or two.
 
So my MacBook Air does not show an update available. How can I force the issue?
as I need the supplemental because I cannot sign in yo my iCloud account after upgrading to Catalina
 
My installation of Catalina bricked my late 2013 iMac. The problem was some sort of conflict with my added RAM (Crucial) that would not permit Catalina to install. After removal of the offending RAM, the install completed but crashed again, when the RAM was reinstalled. After two days on with Apple Support, I lugged my iMac to the Apple Store. It took them 2.5 hours to get a clean install of High Sierra! The RAM that worked perfectly before Catalina was now presenting a problem.

So the choice was to toss my Crucial RAM ($200) and install Apple RAM for way too much money, or accept the $350 trade-in and buy a new iMac. I did the latter, reluctantly. The upgrade to Catalina cost me $2,100 basically.

And the final irony is my new iMac runs Mojave. I am not upgrading to Catalina until 2020, if ever.
 
  • Like
Reactions: The Barron
Apple doesn't have unlimited cash. Apple wants to be a service company, not a hardware/software company and it is starting to show. You can''t possibly defend the condition that iOS and MacOS were released in.

I Had only minor problems with beta iPadOS 13 and 13.1 and only maybe 1 small bug after final release of iPadOS 13/iOS 13. I don't have Catalina on my iMac yet because I still did not finish processing photos from 2019 wedding season + there are some 32-bit libraries in Ps/Lr that can cause issues (which is Adobe problem). However, my wife has Catalina on her 12-inch 2016 MB since day 1 and there were no issues during or after install+no issues during usage. From what I understand on this forums most users have problems with 32-bit apps compatibility (if I don't count post-install hangup which also happened to my friend with Mac Mini 2012 and the HDMI issue with 2018 Mac Minis).
 
So much negativity in here...

I made a clean install on my MBP mid 2014 and everything is perfect!
 
So much negativity in here...

I made a clean install on my MBP mid 2014 and everything is perfect!
You appear to be in the minority that has had good luck with this. If you go through all the comments just on this forum, the negatives and people who have nothing but hassles & regrets far outweigh the positive experiences. I'll continue to wait, thank you.
 
So much negativity in here...

I made a clean install on my MBP mid 2014 and everything is perfect!

I did a clean install on my 2015 MBP and the initial perfection was a false dawn. Yes it’s much faster now. But some key functionality is really broken. Fast and broken isn’t so useful.
 
  • Sad
Reactions: The Barron
You appear to be in the minority that has had good luck with this. If you go through all the comments just on this forum, the negatives and people who have nothing but hassles & regrets far outweigh the positive experiences. I'll continue to wait, thank you.

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 backup your data? Yeah? Crickets.
 
  • Sad
Reactions: The Barron
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 backup your data? Yeah? Crickets.
So tell me why I am getting kernel panics every day after a fresh install and NO DATA/SOFTWARE?

Mojave never had a kernel panic. Windows 10 never crashes.
 
You appear to be in the minority that has had good luck with this. If you go through all the comments just on this forum, the negatives and people who have nothing but hassles & regrets far outweigh the positive experiences. I'll continue to wait, thank you.
People with no issues “minority” as you call them, have no need to post here hence all you ever read on macrumors are negative posts.
 
I updated on Sunday. In Mojave my dual display set up with my Mid 2014 Macbook pro worked. After update, only one display is detected. Anyone else have this issue?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.