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 Sequoia 15.4 Beta 1 - Bug fixes, changes, and more
- Thread starter WilliApple
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
With Beta 1 several tools can't fetch current playing songs/videos anymore (DockMate/MediaMate). Doesn't matter if the source is the Music.app or Youtube in Safari etc.
Can you be less cryptic ?? What should I do to make parallels working ?It doesn't work for someAnd for those that have the issue there a specific tool to be run, available on the developers website.
View attachment 2486364
Do you have a link to this page?It doesn't work for some
View attachment 2486364
These betas are designed for developers.
A developer would (a) know how to roll back and/or re-install, and would probably keep the beta and use any required virtualisation on another computer.
A developer would (a) know how to roll back and/or re-install, and would probably keep the beta and use any required virtualisation on another computer.
Well I’m a developer, I’m using a silicon MacBook Pro. And I’m on the beta. Both docker and parallels work just fine for me. And as I’ve linked for when it doesn’t work there is a package to download.
Are you a signed up developer and have tried to download the package and fix your issues?
Yes i did it... starting any virtualization environment causes kernel panic and hard crash.
Last edited by a moderator:
So it seems like one of the earlier Sequioa beta bugs is back. MBA 15 M3- when it sleeps and display locks automatically, I'm unable to unlock/log back in. I have to do a hard restart every time.
Not good...🙁
Not good...🙁
so no virtualisation, not working apple inteligence in many cases, and sleep. that must be the worse beta i have ever seen in macos.
LOL That is why it’s a Beta
All of the above works on my machine. Please do give your feedback through your developer account to Apple so they can work to fix it. 👍 I often get the feedback back in the feedback app. 👍This didnt help me at all. This seems to be for running macOS virtualized, not using a Mac TO virtualize. This problem seems isolated to M4 series, I have M4 Max.It doesn't work for some
View attachment 2486364
Exactly! I'm not patient enough, especially when apple is screwing with people like that
It seems issue was there in developer beta and they just decided not to hold of with public beta and release this major bug with it.on top of everything mirroring also doesn't work..
no it's a final solutionis that even a workaround?
Can anyone confirm an AIFF bug with the Music app in this beta? Sound Check is not working when AIFF files have been added to the local music library (WAV & MP3's are fine).
Very loud AIFF's should be normalized to a lower level, but when Sound Check in on, it appears to be playing them at full volume. Comparing a WAV and an AIFF of the exact same song shows clear level differences (assuming it's a rather loud song).
Very loud AIFF's should be normalized to a lower level, but when Sound Check in on, it appears to be playing them at full volume. Comparing a WAV and an AIFF of the exact same song shows clear level differences (assuming it's a rather loud song).
It's even in the Known Issues section of the release notes now, I was really hoping for a reissued beta with a fix for thisExactly! I'm not patient enough, especially when apple is screwing with people like that
on top of everything mirroring also doesn't work..
no it's a final solution
Virtual Machines
Known Issues
- Upon update to macOS 15.4 beta 1, M4 Macs will be unable to launch virtual machines and attempts will result in a system restart. (145309647) (FB16542958)
Workaround: Do not launch virtual machines. If virtual machine applications launch upon login, boot to Safe Mode and disable in system settings.
This was added afterwards people found it, it did not come orginaly.
Don't think so, probably it will be weeks before i can run docker on my m4 again ... I refuse to downgrade knowing how many issues it may cause.
Correct, hence the "now" in my comment. I agree, I scanned before installing and it was not there.
The 15.4 b1 borked my M4 Pro mini.
After updating I selected Restart and mini repeatedly rebooted about 6 times in quick succession with the white power light going on and off. The mini then started to flash an orange light repeatedly instead of white.
I then tried to enter Recovery mode and the same flashing white followed by the flashing orange light persisted.
I assumed a firmware issue so established pronto an appointment at my local Apple Store to have them perform the DFU.
At the Apple Store the DFU->Revive failed. I requested they try again because otherwise the next step would be to Restore and that wipes the internal SSD which obviously I don’t want. If the Restore fails then it’s off to the repair shop and a new logic board will have to be installed.
The 2nd attempt to Revive failed……bugger, as did the DFU->Restore. Apple Store said logic board needs to be replaced and will take a week (that is Mar 2nd).
In order to further understand why my M4 Pro mini suffered in such a catastrophic way I will detail how it was configured at the time I performed the latest beta build.
My mini is setup for dual booting using two volumes groups (Production and Test) in a single container on the mini’s internal 512 GB SSD. The issue arose after or during unattended update to 15.4 b1. I estimated it was some 90 minutes from starting the build’s download to when I returned to the mini to find the issue that has caused the DFU process to be needed.
My M4 Pro mini has 512 GB internal SSD and 64 GB of memory. It was considered by Apple to be a CTO purchase.
1) My mini’s power connector is connected directly to my house’s electrical outlet.
2) I have an OWC TB5 Hub directly connected to one of the TB5 ports on backside on the mini.
3) The OWC TB5 Hub which is powered is used for allowing my 27” Studio Display and my ancient Apple TB 27” Display to be connected to it. I use the Apple USB-C to TB2 adapter for the ancient TB 27” Display connection.
4) I have a TB5 OWC Envoy Ultra (4TB in capacity) connected directly to the mini’s backside TB5 port.
5) The 3rd TB5 port on the backside of the mini is open/unused.
6) All of my other external storage devices are connected via running a TB4 cable from the OWC TB5 Hub to an OWC TB4 Hub from which all further external storage devices are connected.
7) The OWC TB5 Hub has 4 TB ports, one USB port, and one TB port is left unused.
8) The OWC TB5 Hub has its own white light built-in power on/off push button which is unusual for a Hub, but find it useful when leaving JUST the mini powered on with NO devices attached to it except for any device connected directly to the mini backside and/or frontside ports.
For the past 3 months since installing my mini last November, it has been heavily used with many TBs of data being moved around, its System Settings > Energy Setting set to ‘High Performance’, and its processor cores quite likely all being used for long stretches of time. The GPU is not heavily used when running my Production workload that is CPU, Memory, and I/O intensive.
There are 3 Admin user accounts configured. I use only one of these as the other two are for backup and testing different user accounts etc.
Prior to the issue arising from doing the beta update I had been pounding on Photos for several days. My Photos library is located on the connected TB5 OWC Envoy Ultra and is some 400 GB in size.
After updating I selected Restart and mini repeatedly rebooted about 6 times in quick succession with the white power light going on and off. The mini then started to flash an orange light repeatedly instead of white.
I then tried to enter Recovery mode and the same flashing white followed by the flashing orange light persisted.
I assumed a firmware issue so established pronto an appointment at my local Apple Store to have them perform the DFU.
At the Apple Store the DFU->Revive failed. I requested they try again because otherwise the next step would be to Restore and that wipes the internal SSD which obviously I don’t want. If the Restore fails then it’s off to the repair shop and a new logic board will have to be installed.
The 2nd attempt to Revive failed……bugger, as did the DFU->Restore. Apple Store said logic board needs to be replaced and will take a week (that is Mar 2nd).
In order to further understand why my M4 Pro mini suffered in such a catastrophic way I will detail how it was configured at the time I performed the latest beta build.
My mini is setup for dual booting using two volumes groups (Production and Test) in a single container on the mini’s internal 512 GB SSD. The issue arose after or during unattended update to 15.4 b1. I estimated it was some 90 minutes from starting the build’s download to when I returned to the mini to find the issue that has caused the DFU process to be needed.
My M4 Pro mini has 512 GB internal SSD and 64 GB of memory. It was considered by Apple to be a CTO purchase.
1) My mini’s power connector is connected directly to my house’s electrical outlet.
2) I have an OWC TB5 Hub directly connected to one of the TB5 ports on backside on the mini.
3) The OWC TB5 Hub which is powered is used for allowing my 27” Studio Display and my ancient Apple TB 27” Display to be connected to it. I use the Apple USB-C to TB2 adapter for the ancient TB 27” Display connection.
4) I have a TB5 OWC Envoy Ultra (4TB in capacity) connected directly to the mini’s backside TB5 port.
5) The 3rd TB5 port on the backside of the mini is open/unused.
6) All of my other external storage devices are connected via running a TB4 cable from the OWC TB5 Hub to an OWC TB4 Hub from which all further external storage devices are connected.
7) The OWC TB5 Hub has 4 TB ports, one USB port, and one TB port is left unused.
8) The OWC TB5 Hub has its own white light built-in power on/off push button which is unusual for a Hub, but find it useful when leaving JUST the mini powered on with NO devices attached to it except for any device connected directly to the mini backside and/or frontside ports.
For the past 3 months since installing my mini last November, it has been heavily used with many TBs of data being moved around, its System Settings > Energy Setting set to ‘High Performance’, and its processor cores quite likely all being used for long stretches of time. The GPU is not heavily used when running my Production workload that is CPU, Memory, and I/O intensive.
There are 3 Admin user accounts configured. I use only one of these as the other two are for backup and testing different user accounts etc.
Prior to the issue arising from doing the beta update I had been pounding on Photos for several days. My Photos library is located on the connected TB5 OWC Envoy Ultra and is some 400 GB in size.