I hope someone can explain this behavior, it’s utterly confusing for me.
My best guess is the 14.7.3 RC I’m on atm.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I hope someone can explain this behavior, it’s utterly confusing for me.
My best guess is the 14.7.3 RC I’m on atm.
Anyone else having issues with videoconferencing apps crashing WindowServer?
(Late 2012 Mac mini, running Sonoma 14.7/OCLP 2.0.2)
(Late 2012 Mac mini, running Sonoma 14.7/OCLP 2.0.2)
If I have macOS Sonoma 14.7 (installed via OCLP 2.0.2) on a Late 2012 Mac mini, and want to go to Sonoma 14.7.2 (not quite ready to make the big leap to Sequoia just yet), do I update OCLP to 2.2.0 first, and then try the OS update? Because I think OCLP 2.2.0 came out before 14.7.2, and if I bring up OCLP 2.2.0 on the system and try to install the root patches, it gets errors and complains about seeing 14.7 and wanting to see 14.7.1 for some reason.
Less:
- [...]
- Running sanity checks before patching
- SystemVersion.plist build version mismatch: found 14.7.1 (23H222), expected 14.7 (23H124)
An update is in progress on your machine and patching cannot continue until it is cancelled or finished
- Unmounting root volume
- Failed sanity checks, cannot continue with patching!!!
Is it possible that 14.7.1 has already been partially installed, causing the reported mismatch? Maybe try updating OCLP in safe mode?
I also sometimes see advice to revert patches in OCLP, restart, and reapply patches.
That's what's weird. I don't know where it's getting that 14.7.1 reference from. Not from the system .plist:
Less:
% grep 14 /System/Library/CoreServices/SystemVersion.plist
<string>14.7</string>
<string>14.7</string>
With older versions of macOS Apple doesn't do the whole developer/public beta testing cycle, so, as far as I am aware, they are always labeled as RC until the final version is released.
Smooth OTA upgrade from Sonoma 14.7.2 to 14.7.3 on my HackBookPro6,2. Patching with OCLP 2.2.0. Running Safari 18.3 without issues so far. Well done, Devs!
Have a look at this:
/System/Volumes/Update/Update.plist
/System/Volumes/Update/Preflight.plist and delete update if it is here: /System/Library/AssetsV2/com_apple_MobileAsset_MacSoftwareUpdate/
Thanks, @paalb ... here's what I have:
Less:
% grep 14.7 /System/Volumes/Update/Update.plist
<string>14.7.1</string>
% grep 14.7 /System/Volumes/Update/brain_path.plist
<string>14.7.1</string>
% grep 14.7 /System/Volumes/Update/Preflight.plist
grep: /System/Volumes/Update/Preflight.plist: No such file or directory
% ls -lt /System/Library/AssetsV2/com_apple_MobileAsset_MacSoftwareUpdate
total 144
-rw-r--r-- 1 root wheel 35697 Jan 28 12:21 com_apple_MobileAsset_MacSoftwareUpdate.xml
-rw-r--r-- 1 root wheel 35693 Jan 28 12:21 com_apple_MobileAsset_MacSoftwareUpdate.xml.purged
drwxr-xr-x@ 5 _nsurlsessiond wheel 160 Nov 4 16:30 22316ca52ed78feea905472d6be72fcff6bf43c5.asset
Last edited:
My note sais:
"Deleted this:
/System/Library/AssetsV2/com_apple_MobileAsset_MacSoftwareUpdate/*
/System/Volumes/Update/Update.plist
/System/Volumes/Update/Preflight.plist"
So yes, you delete those three inside of com_apple_MobileAsset_MacSoftwareUpdate and the Update.plist
If I remember right, the downloaded os is inside the 22316ca52ed78feea905472d6be72fcff6bf43c5.asset folder.
Maybe you have to delete the brain_path.plist too? I do not know.
OK, I nuked those files/directories. I don't have a Preflight.plist file.
I have OCLP 2.2.0 installed now. Do I have to run it (i.e. the 'Build and Install OpenCore' stage) first before I can attempt the OS upgrade to 14.7.3?
Follow the instructions here: https://dortania.github.io/OpenCore-Legacy-Patcher/INSTALLER.html#downloading-the-installer If you already have done some of it you can skip, but it can never do any harm to do "Build and Install OpenCore".
I ended up doing the OpenCore 2.2.0 upgrade and installed it to disk, and after rebooting I did the OTA upgrade to Sonoma 14.7.3.
Unfortunately, the upgrade seemed to kill my keyboard and mouse (connected to the USB 2.0 hub built into my Dell U3014 30” monitor) so I’m dead in the water now 😞
What keyboard are you using?
Unplug the keyboard from the monitor, plug in to your mini.
Even better, get a USB 3.0 hub of some kind, and plug THAT into your mini. I have a 4 port hub plugged into my 2012 mini. Gives me enough extra USB ports for most USB needs.
Unplug the keyboard from the monitor, plug in to your mini.
Even better, get a USB 3.0 hub of some kind, and plug THAT into your mini. I have a 4 port hub plugged into my 2012 mini. Gives me enough extra USB ports for most USB needs.
In the latest video from Mr. Macintosh, he showed the check for the booted OCLP version that is installed. I see a difference between the installed OCLP 1.5.0 and booted into OCLP version 2.2.0
In both macOS Sonoma 14.7.3 (RC) and macOS Ventura 13.6.7
Booted Information: OCLP 2.2.0
I struggled earlier to update to OCLP 2.2.0 within macOS Sonoma updating 14.7.1 to 14.7.2. Made me clean install macOS Sonoma 14.7.3, which seemed RC.
In my current boot screen, I also see the version: REL-101-2024-08-05
Any thoughts?
In both macOS Sonoma 14.7.3 (RC) and macOS Ventura 13.6.7
Booted Information: OCLP 2.2.0
I struggled earlier to update to OCLP 2.2.0 within macOS Sonoma updating 14.7.1 to 14.7.2. Made me clean install macOS Sonoma 14.7.3, which seemed RC.
In my current boot screen, I also see the version: REL-101-2024-08-05
Any thoughts?
Sorry if I wasn’t clear. This is on a 2013 Mac Pro trash can, not a Mac mini.
It’s an old Apple Keyboard II via an ADB-to-USB adapter. Worked perfectly on Sonoma 14.7.
My Dell U3014 monitor has a built-in USB 2.0 hub which worked fine with the keyboard & mouse until the OTA upgrade from 14.7 to 14.7.3. That’s why I’m baffled that they stopped working.
Also, what’s strange is that System Info sees all of the USB devices (whether plugged in directly to the onboard USB ports, or via the Dell monitor’s USB ports), yet the keyboard & mouse still don’t work. A Logitech Webcam and a PIV badge reader plugged directly into the onboard USB ports both work; but of course they are probably not USB 1.1 devices like the keyboard & mouse (a Microsoft IntelliMouse Explorer 3.0 mouse) presumably are.
Last edited:
Does this mean you were successful doing the clean install of 14.7.3?
I was able to get the OTA update to 14.7.3 within macOS Sonoma 14.7 to work, but it left me with a system that isn’t working as my keyboard & mouse are no longer functional.
Actually your other suggestion worked! Thanks!
I went to Best Buy® and bought an Insignia™ 4-port portable USB 3.0 hub. It works perfectly.
The only thing connected to the Dell monitor's USB ports now is the host connection to the Mac Pro trash can, nothing else. I still have no idea what knocked out the keyboard & mouse but I'm too lazy to plug anything else in to the Dell ports (it's a pain, basically have to put the monitor on its side to get at the damn things). I'm just happy to be back in action again ...
Here is what my USB tree looks like now, in System Report:
Attachments
So, now that I have my (MacPro6,1) machine back ...
Is anyone else having the issue with the "red blocking" and freeze-ups appearing in Microsoft Teams?
With the other apps that have the same issue (Slack, Brave Browser, Microsoft Edge, Google Chrome and so on) you can work around it via opening them from the command line via
but for some reason, that workaround doesn't work with Teams ...
Is anyone else having the issue with the "red blocking" and freeze-ups appearing in Microsoft Teams?
With the other apps that have the same issue (Slack, Brave Browser, Microsoft Edge, Google Chrome and so on) you can work around it via opening them from the command line via
Less:
open /Applications/<App name>.app --args --use-angle=glYes, I clean installed 14.7.3 successful.
I've never ever used Bluetooth mice and/or keyboards since 2008 starting using the Mac Pro 3.1. I'm really attached to any of my hardwired connections, even for my home network (UniFi) my Call of Duty is: can it be wired, just do it.
It works like Magic!
