Apple’s Worldwide Developers Conference to kick off June 10 at 10 a.m. PDT with Keynote address

The Keynote will be available to stream on apple.com, the Apple Developer app, the Apple TV app, and the Apple YouTube channel. On-demand playback will be available after the conclusion of the stream.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Forced upgrade to Sonoma: can it be stopped?

Numerous users are reporting that their computers have been forcibly "upgraded" to Sonoma without their consent. It seems to have started on my Monterey boot drive today: I am currently booted from another drive and am afraid to go back to using my main system drive (Monterey). I ALWAYS have Auto updates turned off, with only "Check for updates" and "Install security responses and system files" enabled. Is there a fix for this? I don't want to have to spend a chunk of time getting rid of Sonoma and restoring Monterey, and it's ridiculous that anyone should have to.


TidBits Thread on forced "upgrades"

Mac Studio (2022)

Posted on Jan 11, 2024 5:39 PM

Reply
Question marked as Best reply

Posted on Jan 17, 2024 8:56 AM

I was forced to upgrade on 1/16/2024. I find it interesting and my Time Machine backup stopped working. The USB stopped working. An unplug and replug usually fixes this. However, this time a restart was necessary. After the restart, which took suspiciously long, the login screen came up Sonoma.


Not cool Apple. In 20 years, I've never experienced this.

48 replies

Jan 30, 2024 7:54 AM in response to kahjot

Nice to know one is not alone in this. I sent my sob story to Apple in complaint. What was weird for me was that I was failing to get the Ventura installer to work off a USB, and as others have mentioned the recovery wasn't allowing me to reinstall from a TM backup, which I had. After two hours I gave up and contacted support. The person on that chat asked me why I wanted to downgrade so I explained. Then she asked me to do some checks which I did and then went silent for a while, then asked me to shut down and boot into recovery and select the USB which I had already tried, and it hadn't shown up as a volume for me to select. I said I had already tried that and there was no reply and then the chat got terminated. What the **** I thought I've nothing to lose now by shutting down. So I tried it and this time the installer volume appeared so eventually I was able to get back to Ventura.

Jan 12, 2024 7:55 AM in response to etresoft

Have seen over in Sonoma the same


Suggested to this User and maybe to yourself to download the Full Version of Sonoma manually - Terminal


Keep it in the Applications folder and never actual launch Sonoma


Only meant as a possible workaround while Apple Investigates this issue


PS - Major Winter Storm with bitterly cold 70 kmp winds coming

Jan 13, 2024 12:43 PM in response to i.tom

i.tom wrote:

Same today, 13 Jan 2023, after a system restart I had the forced upgrade from Monterey to Sonoma despite my settings being not to allow automatic updates. I'd been swithering about updating to Ventura too. Ha ha. Well done Apple.

Well, now's your chance. An easier option is to just erase the hard drive and restore the OS from recovery. But if you do that, your only restore option is Ventura. 😄 In all fairness, I have been using Ventura on my 2023 Air for several months now. It's not awful. It does fix the Finder Airdrop lockup bug. And the Finder-based UI for a USB-connected device is much improved. Those are the only two noticeable improvements from Monterey.


However, I am disappointed in the Time Machine restore. It wasn't 100% successful. iCloud is confused. I had to re-download all of my e-mail. Spotlight is broken. I'm going to have to redo it all as it it was a new machine. Hopefully Recovery will allow me to restore Monterey this time. How ironic that this is the only time I've really needed to use Time Machine.

Jan 13, 2024 2:54 PM in response to etresoft

In Recovery, after erasing your primary SSD drive, (re)connect to a WiFi network, then insert your bootable Monterey USB stick. Then wait a moment or two until Monterey appears as a device, select it, and proceed with the installation. It took about an hour to install from my ancient USB flash drive.

Then I selected the latest Time Machine backup device (a USB-connected 7200rpm HDD), and it restored about 275GB in about 90 minutes.

Jan 13, 2024 5:17 PM in response to kostby

kostby wrote:

In Recovery, after erasing your primary SSD drive, (re)connect to a WiFi network, then insert your bootable Monterey USB stick. Then wait a moment or two until Monterey appears as a device, select it, and proceed with the installation. It took about an hour to install from my ancient USB flash drive.

Yeah. That all worked fine. Not quite as fast as the Sonoma install, however. 😄

Then I selected the latest Time Machine backup device (a USB-connected 7200rpm HDD), and it restored about 275GB in about 90 minutes.

That would be nice. I have a 1 TB and it took overnight to restore. I'm going to have to redo it though. Spotlight isn't working. Last time I had this kind of Spotlight problem was when I tried to install an additional OS version. I had to wipe the hard drive to fix it.

Jan 13, 2024 9:48 PM in response to etresoft

If still need be…


Open Terminal and run each of these one at a time


/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user


sudo /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -seed -lint -r -f -v -dump -domain local -domain system -domain user -domain network


killall Dock


sudo mdutil -E /


sudo mdutil -i on /


Rebuilding a drive index can take a long time, so be prepared to wait whether you do it through the System Preference panel or the command line.

Jan 14, 2024 4:44 AM in response to BDAqua

BDAqua wrote:

If still need be…

Open Terminal and run each of these one at a time

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

sudo /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -seed -lint -r -f -v -dump -domain local -domain system -domain user -domain network

killall Dock

sudo mdutil -E /

sudo mdutil -i on /

Rebuilding a drive index can take a long time, so be prepared to wait whether you do it through the System Preference panel or the command line.

Thanks for the list. I'll try all of that. But I'm not hopeful. I did all of that on my new computer after I had tried to install both Ventura and Sonoma. The only thing that worked was a wipe and reinstall. At least now I'm ready for it and I have the Air to use. The other day I only had the 2017 Intel. That was painful.

Jan 17, 2024 2:15 PM in response to Bryan Mac

Bryan Mac, this reminds me that when it happened to me, I restarted because I was trying to copy files to an external hard drive via USB. They wouldn't copy and it kept hanging so I restarted to try and resolve the issue. It did resolve the file copy issue but lo and behold Sonoma appeared.

I'm not sure if dumping the USB like that is part of the install process, but it's something that happened to me too.

Forced upgrade to Sonoma: can it be stopped?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.