Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Has anyone else had issues with Xcode 26.1 failing to update from the app store? I updated to 15.7.2, without issues, and Safari, and the command line tools updates installed fine, but Xcode won't update through the app store. 26.0.1 was the same way, and then it worked several hours later.

Finally got it to update. What I did is run the existing Xcode 26.0.1, went through the initial set up process again, as it seems to have reset itself after the macOS update, and then tried the update again, and this time it worked. Now 26.1 is downloading the Simulators, and so forth a first run of Xcode does.
Hey I'm facing this problem but unable to update Xcode.
 
👍
BTW, look at MacPorts instead of Homebrew.
I used MacPorts in the past, before switching to Homebrew, I always seemed to have more issues with it than brew as a whole. With that said, I really can't speak to MacPorts at this point since I haven't used it in so long. My ultimate plan was simply to switch to Linux, and for 95% it's fine. One of the harder parts is finding open source alternatives to things, and again there, no problems for most of what I do. The main challenge in terms of using Linux full time, is finding a way access text messaging from the phone e.g. Text message forwarding. I tried KDEConnect, but couldn't figure out how to send and receive / access my messages. It's supposed to do that. So, in some ways. I've gotten stuck in moving forward. Buying a new Mac, or switching platforms. OCLP works for me, but I don't like it from a professional, and support stand, when it comes to getting official support for whatever I may need, but it lets me at least use the computer. I don't really want a new Mac and change to Apple Silicon and loose access to some of the legacy stuff Intel is good for, and Linux is a more open free platform, which I like, but lacks some of the specific features Apple offers that are a big help to me on a daily basis. Running Monterey (the last supported OS) still works for me, for the most part, but future app updates are dropping off more and more, so, the only option in a supported setup would be to put Sonoma in a VM, under Monterey, and only use it for apps that won't run under Monterey.

I've also thought about looking for a 2020, 27" iMac, but would it be worth it at this point. It would give me support for Tahoe, and Sonoma, Sequoia, etc, but then in a few years, it will be unsupported as well. This late 2015, iMac 17,1 still works and it's stable, it's just what is the best way to use it now.
 
  • Like
Reactions: macpro_mid2014
The same exact thing happened to me, although I let OCLP 2.4.1 continue downloading the new KDK. No worries. Tahoe has NOT been installed, God forbid!
It has happened that the OS has been downloaded and not installed for me in the past.
Look for the downloaded OS here:
/System/Library/AssetsV2/com_apple_MobileAsset_MacSoftwareUpdate/

Also for these files.
/System/Volumes/Update/Update.plist
/System/Volumes/Update/Preflight.plist

I deleted the files to be on the safe side.
 
It has happened that the OS has been downloaded and not installed for me in the past.
Best practice for all OCLP users is pretty clearly to make sure to switch off all automatic updates in system settings to avoid such issues and be in control of any decisions to update.
If you forget to do this and the update is downloaded and "staged" anyway and you get the dreaded "SystemVersion.plist BuildVersion Mismatch Error" it is difficult (but not impossible) to fix it. This may help if you end up with a downloaded and "staged" update that makes your Mac unusable. I have seen it and this has worked here FWIW.
But again, all OCLP users should probably switch off all automatic updates for now.

Edit: Apparently this is in the official documentation FAQ these days. Thanks @Neon Ball.
 
Last edited:
Best practice for all OCLP users is pretty clearly to make sure to switch off all automatic updates in system settings to avoid such issues and be in control of any decisions to update.
If the update is downloaded and "staged" anyway and you get the dreaded "SystemVersion.plist BuildVersion Mismatch Error" it is difficult (but not impossible) to fix it. This may help if you end up with a downloaded and "staged" update that makes your Mac unusable. I have seen it and this has worked here FWIW.
But again, all OCLP users should probably switch off all automatic updates for now.
This is also mentioned in the official documentation FAQ.
 
I have made 90 days defer profiles for a year now and it works. Using the settings below both new version of Sequoia and Tahoe is ignored.
Screenshot 2025-11-15 at 14.35.34.png
 
I have made 90 days defer profiles for a year now and it works. Using the settings below both new version of Sequoia and Tahoe is ignored.
I tried that and Apple, seemingly randomly at times marks updates as major and minor and then the profile will not help much as we still need to keep software updates off..
Are you using the iMazing editor or something else, and do you see provisions for this major/mini nomenclature?
 
Last edited:
I tried that and Apple, seemingly randomly at times marks updates as major and minor and then the profile will not help much as we still need to keep software updates off..
Are you using the iMazing editor or something else, and do you see provisions for this major/mini nomenclature?
The screen dump is from iMazing profile editor. I have not updated to Sequoia 15.7.2. The settings in the screen dump suppress both Tahoe and Sequoia 15.7.2. At the same time, an update to Command Line Tools is not suppressed.
 
I've really just got a big kick out Sequoia performance on this iMac, 17,1. After doing some reading on Reddit, I have turned off a few things in the OS, I don't use, and 1 thing I didn't realize made a difference, and things are almost instant now, and login is a lot faster too on reboot.

What I disabled was:
Siri (i don't use Siri on the Mac)
Animate opening Applications (didn't think this would help, but apps open faster)
Reduce Motion (even removing the little animations, makes things run faster, I was so used to it, that I was surprised when I saw the difference.)
Use iPhone Widgets (up there with I don't use desktop widgets, and I just use the phone widgets on the phone.)
Show Widgets on Desktop and Stage Manager (I don't use desktop widgets), I keep them in the notification center where they've always been prior to Sonoma.
I tried Reduce transparency, but I didn't make a difference for me in performance, and it makes the dock look tacky. So, I left that on.

Now, I'm going to investigate Telemetry. Not because I have issues sending data that can help improve things, but to see if it makes a difference with performance.

Here is the Reddit link I've been reading, and got these suggestions from:

Thanks for the reddit link, now less beachball, quicker pointer, I still have stage manager I just like it to much.
 
I'm basically surprised that any of you had any of those options still enabled! I turned all of them off years ago.

See the Law of Conservation of Energy for deeper meditation with respect to available CPU cycles: https://en.wikipedia.org/wiki/Conservation_of_energy

To put it another way to suit this context: software ideas may have infinite capacity. The hardware it's running on can only have a finite capacity to fulfill requests to execute said ideas. If your m/c was built in, say, 2012, keep turning off as much extraneous "fluff" that has appeared since then.

Computer fundamentals, baby! ;)
 
Last edited:
MBP11,1: updated to 15.7.2, USB installer, OCLP 2.4.1. No problems. >>> Thank you developers <<< !
(Waiting with Tahoe 26.1 on that machine; 26.0.1 running OK with minimal patches.)

The MBP11,1 is the only legacy machine I still have. The 5,2 developed a hardware fault I couldn't repair and is garbage now.
As the signature also shows we have an M1 MBP 14" and an M4 MBA 15", both running 26.1.
The latter is my production machine now. I appreciate the 15" display and the speed (and need both features in a new job).

But I keep the MBP11,1 as a backup machine and I'm looking forward to 26.x on it.
 
  • Like
Reactions: rehkram
I'm basically surprised that any of you had any of those options still enabled! I turned all of them off years ago.

See the Law of Conservation of Energy for deeper meditation with respect to available CPU cycles: https://en.wikipedia.org/wiki/Conservation_of_energy

To put it another way to suit this context: software ideas may have infinite capacity. The hardware it's running on can only have a finite capacity to fulfill requests to execute said ideas. If your m/c was built in, say, 2012, keep turning off as much extraneous "fluff" that has appeared since then.

Computer fundamentals, baby! ;)
I've always had my settings I've changed for my setups, but usually I haven't needed to worry about the graphical settings as things just work. Even with Sequoia, the defaults work fine, but adjusting the ones I mentioned I did personally just give a performance boost to help things a bit.

Edit: I thought I had posted this earlier, but apparently I forgot, and when I came back to the site, it was still in the edit field for a new post.
 
  • Like
Reactions: rehkram
MBP11,1: updated to 15.7.2, USB installer, OCLP 2.4.1. No problems. &gt;&gt;&gt; Thank you developers (Waiting with Tahoe 26.1 on that machine; 26.0.1 running OK with minimal patches.)

The MBP11,1 is the only legacy machine I still have. The 5,2 developed a hardware fault I couldn't repair and is garbage now.
As the signature also shows we have an M1 MBP 14" and an M4 MBA 15", both running 26.1.
The latter is my production machine now. I appreciate the 15" display and the speed (and need both features in a new job).

But I keep the MBP11,1 as a backup machine and I'm looking forward to 26.x on it.

Feels like we are at a point where us that haven’t upgraded are seeing when the M1 will be unsupported and with rumours that the new design MacBooks are two years away and maybe the cheaper one with iPhone chip next year is a limbo moment for us holding out , I can cope with my MacBook another two years hey it’s been 11 years nearly 12 already but also if a hardware fault occurred would also force our hands (and if needed for work) . MacBook Pro been the best laptop I’ve owned and I’m sure it would be the same with a newer model and that’s without mentioning what OCLP could pull out of the bag with Tahoe.
 
Hi Guys I posted a year ago and didn't get anything - I've tried lot of things but still struggling. 2017 MacBook retina.

If I close the lid it stays on I can see the display light when its closed and it stays on until battery dies.

If I click sleep - it sleeps and I then close the closing wakes it again!

If I do the above but wait longer than 10 seconds it stays off.

Please help I'm pulling my hair out I just want to close it and it to sleep or hibernate like it used to.

Thanks
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.