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.
They fixed Music née iTunes beach balling on playing the first song after opening the app. I don't know if it affected anyone else, my library is all local.
 
The update damaged two of my internal partitions. Just old macOS installers but still not a good sign.

My Mac doesn't support anything older than Sequoia and I wanted to delete the other ones anyway. I get those warnings now always when they are mounted after a reboot.

View attachment 2605546View attachment 2605547

I see this error with an external drive. HOWEVER, I plugged the drive into another Mac not running the latest beta and Disk Utility says the drive is OK.
 
I see this error with an external drive. HOWEVER, I plugged the drive into another Mac not running the latest beta and Disk Utility says the drive is OK.
yeah i would take error messages on betas with a big grain of salt.

like it’s saying something wrong with the drive when there isn’t.

the truth of the matter is there is something wrong with the tahoe beta, not your drive, but did it say that in the message? nope!
 
yeah i would take error messages on betas with a big grain of salt.

like it’s saying something wrong with the drive when there isn’t.

the truth of the matter is there is something wrong with the tahoe beta, not your drive, but did it say that in the message? nope!
Yeah, it appears fsck_hfs is broken in this beta.
 
  • Like
Reactions: Adora
Yeah, it appears fsck_hfs is broken in this beta.
could this be a workaround?

  • Kill the Process (Temporary Solution): If fsck_hfs is blocking access to a drive, use Activity Monitor or the Terminal command sudo killall fsck_hfs.
  • Disable SIP and Rename fsck_hfs (System-wide):
    1. Boot into Recovery Mode (Command+R) and run csrutil disable in Terminal to disable System Integrity Protection.
    2. Restart the system.
    3. Rename the utility: sudo mv /sbin/fsck_hfs /sbin/fsck_hfs.disabled.
  • Use fsck_hfs -n (No Repair): Run fsck_hfs with the -n flag, which forces it to never attempt to repair any damage found
 
  • Like
Reactions: Adora
seed release note only says this

  • HFS external media might fail to mount automatically. (168672160)

    Workaround: For macOS only, use CLI tool diskutil mount to attach the relevant disk device.
but that’s not quite the same thing.

at least they are aware there is something wrong with hfs on 26.4 beta 1
 
  • Like
Reactions: Adora
At least it didn't appear again after a reboot. Maybe after every update now once.


The update damaged two of my internal partitions. Just old macOS installers but still not a good sign.

My Mac doesn't support anything older than Sequoia and I wanted to delete the other ones anyway. I get those warnings now always when they are mounted after a reboot.

View attachment 2605546View attachment 2605547

View attachment 2605548

I get the same error from my two external HFS+ drives. I tested them on another Mac and they work just fine, so I suspect the issue lies with this beta rather than the drives.
 
  • Like
Reactions: Adora
Can anyone confirm if the background sounds/ambient music widget is present here, or just iOS?

I don't find a widget for it. It's in Accessibility settings and you have can put those in in the menu bar or control center to activate it, but the choice of the sound is only in System Settings and already had been there since a while.

Screenshot 2026-02-17 at 11.33.17.png
Screenshot 2026-02-17 at 11.32.48.png



Screenshot 2026-02-17 at 11.42.39.png
Screenshot 2026-02-17 at 11.49.00.png



Is any one else having problems with making screenshots of menu bar elements? I have a huge empty space everytime I do it. In control center it looks even two-colored. I seems the Menu bar items are all using the complete space from top to Dock. You can already see it in the preview when marking it.

As comparison:

Screenshot 2026-02-17 at 11.53.11.png
Screenshot 2026-02-17 at 11.53.28.png
 
Last edited:
I don't find a widget for it. It's in Accessibility settings and you have can put those in in the menu bar or control center to activate it, but the choice of the sound is only in System Settings and already had been there since a while.

View attachment 2605732View attachment 2605734


View attachment 2605733View attachment 2605736


Is any one else having problems with making screenshots of menu bar elements? I have a huge empty space everytime I do it. In control center it looks even two-colored. I seems the Menu bar items are all using the complete space from top to Dock. You can already see it in the preview when marking it.

As comparison:

View attachment 2605738View attachment 2605739
Thanks for confirming this!

I already have Shortcuts set up for my background sounds and volume, but a widget will look nicer.
 
Got hit with the external HFS+ drive issue. Unfortunately the workaround (mounting via diskutil) also fails. Such is the life of a beta test
 
  • Sad
Reactions: Adora

There is a 7 day trial.

View attachment 2605741
I use LaunchOS
1771348837266.png

All of the Launchpad features are free, but if you pay a one time fee, you get a TON of customization, but if you just want Launchpad as it was in Sequoia but Liquid Glassified, I highly recommend LaunchOS.

It also brings over your Launchpad layout if you had one created.
 
I use LaunchOS
View attachment 2605845
All of the Launchpad features are free, but if you pay a one time fee, you get a TON of customization, but if you just want Launchpad as it was in Sequoia but Liquid Glassified, I highly recommend LaunchOS.

It also brings over your Launchpad layout if you had one created.

I forgot the name and only found the other one on my Mac. Not sure which is better. As said I never really was a Launchpad user.

Maybe try both. @ivan86



There are also some more.
 
I don't get any alert when I launch Intel apps. ☹️
Music to my ears - who likes popups about some feature years away from being deprecated?

Some notification setting on your end perhaps - e.g. 'Don't disturb' active? Or simply a bug. 😛
 
From the release notes:

External Media​

Known Issues​

  • HFS external media might fail to mount automatically. (168672160)

    Workaround: For macOS only, use CLI tool diskutil mount to attach the relevant disk device.


Here are the full release notes:

AppKit​

Resolved Issues​

  • Fixed: Window resize pointer does not follow the window's corner shape. (149726089)

Background Assets​

New Features​

  • You can now check the status of an asset pack while offline by calling local<wbr>Status(of<wbr>Asset<wbr>Pack<wbr>With<wbr>ID🙂 or asset<wbr>Pack<wbr>Is<wbr>Available<wbr>Locally(with<wbr>ID🙂 on the shared asset pack manager. The former method returns all available status information. The latter returns only a Boolean value but can be called synchronously. Not all status information is available offline. (164498466)
  • You can make the latest version of an asset pack available locally by calling ensure<wbr>Local<wbr>Availability(of:<wbr>require<wbr>Latest<wbr>Version🙂 on the shared asset pack manager and passing true to the should<wbr>Update parameter. (166237389)

Known Issues​

  • Setting a URL override could break apps from the App Store that use Apple-Hosted Background Assets. (169558509)

    Workaround: Remove any URL override that you previously set before installing or using an app from the App Store.
  • Apps might crash when downloading asset packs. (169648111)

    Workaround: If an app crashes due to this issue, then relaunch it. The app should then have local access to the asset pack that it was downloading when it crashed.

CoreMIDI​

New Features​

  • Audio MIDI Setup now supports Network MIDI 2.0 sessions in the redesigned MIDI Network Setup panel. You can create MIDI 2.0 connections over your local network using UDP transport for Universal MIDI Packets, enabling both Legacy MIDI and MIDI 2.0 protocol communication. Network MIDI 2.0 sessions appear alongside existing RTP MIDI sessions and support automatic device discovery through mDNS and data integrity features for reliable wireless performance. (118728162)

External Boot​

Known Issues​

  • When installing an external disk, some configurations of M1 Apple Silicon Macs might panic at boot. (170263142)

    Workaround: Install to a secondary volume in APFS container instead of external disk to validate secondary boot sequences.

External Media​

Known Issues​

  • HFS external media might fail to mount automatically. (168672160)

    Workaround: For macOS only, use CLI tool diskutil mount to attach the relevant disk device.

Internet Accounts​

Known Issues​

  • Exchange syncing for Calendar, Reminders and Notes might fail. (168082477)

    Workaround: To continue syncing Calendar and Reminders, disable Notes syncing in Internet Accounts.

Login​

Known Issues​

  • Touch ID might not be available to unlock the screen of a standard user account after updating to this release. This occurs when FileVault is enabled and a standard user account is logged in prior to any administrator logging in following the update. (169743642)

    Workaround: An administrator user should sign in to the Mac before any standard users.

macOS Recovery​

Known Issues​

  • When deleting a boot volume from the Activation Lock window in macOS Recovery, full erase functionality might not work. (170280070)

    Workaround: Use the "Erase All Content and Settings" functionality from the booted OS instead of triggering from recovery.

Networking​

Resolved Issues​

  • Fixed: Multiple processes leak CFRun<wbr>Loop<wbr>Source objects when Automatic proxy configuration (PAC) or Auto proxy discovery are configured.

    For clients of the CFNetwork<wbr>Execute<wbr>Proxy<wbr>Auto<wbr>Configuration<wbr>URL and CFNetwork<wbr>Execute<wbr>Proxy<wbr>Auto<wbr>Configuration<wbr>Script API, please check to make sure your process is not working around the leak by overreleasing the CFRun<wbr>Loop<wbr>Source<wbr>Ref returned by those functions or the CFArray<wbr>Ref and CFError<wbr>Refpassed to the completion. (166839810) (FB21376045)

Resource fork​

Resolved Issues​

  • On macOS 26.4 and later, file systems that do not natively support extended attributes restrict partial writes to the first 286 bytes of the resource fork extended attribute (com.apple.ResourceFork).

    To modify the resource fork, replace the entire 286-byte range, or write beyond the 286-byte offset. (156896699)

Rosetta​

Deprecations​

  • As announced at WWDC in 2025, macOS Tahoe 26 is the last release to support Intel based Macs. Additionally, Rosetta support for apps will end after macOS 27. Starting in macOS Tahoe 26.4, users will be notified when they launch apps that use Rosetta of the upcoming incompatibility.

    During the beta period, the cadence of notifications will be accelerated, enabling Apple and developers to address any issues that might occur.

    There will continue to be support for older, unmaintained gaming titles leveraging Rosetta along with software running Intel binaries in Linux VMs.

    Organizations using a device management service can control the notification experience with the allow<wbr>Rosetta<wbr>Usage<wbr>Awareness key. (169228455)

StoreKit​

New Features​

  • New fields revocation<wbr>Type and revocation<wbr>Percentage have been added to Transaction . (148858551)

SwiftUI​

Resolved Issues​

  • Fixed: SwiftUI does not surface the latest .user<wbr>Activity as the current user activity. (163136831)
  • Fixed: On macOS, a non-opaque window that hosts glass content will correctly update the backdrop content behind the glass even if the window is inactive. (166828089) (FB21375029)

Known Issues​

  • Multiple implicit SwiftUI animations (triggered by Reality<wbr>View<wbr>Content<wbr>.animateor Entity<wbr>.animate) that modify a RealityKit component's properties, are combined only when the implicit animations target the same set of component properties.

    For example, if you initiate an implicit animation on Transform.scale and then initiate an implicit animation on Transform.scale and Transform.translation then the animations affecting the scale property will be independent of each other, and will not combine. In this case, the most recently initiated animation will overwrite the scale property. (169723142)

    Workaround: Ensure the same component properties are animated by subsequent implicit animations when possible.

Virtualization​

Resolved Issues​

  • Fixed: On certain hardware configurations, new macOS Tahoe virtual machine installations may boot to a black screen. (169654019)


Also, DMGs may not mount either, giving an error like this:

1771351625688.png


A workaround for DMG files that won't mount:
hdiutil attach /Path/to/my.dmg
Replace /Path/to/my.dmg with the actual path to your DMG file.
 

Additional Notes
  • Please know, Memory Management has always been an issue on any OS (not just Apple's). If you believe there is a Memory Leak, please go to the Apple Menu > Restart > Restart to fix it.

I've been reading this for too long without making a comment on it.

No, memory management is NOT an issue on all O/Ss. And no, restarting your computer is not the fix when it does occur.

I'm aware this is a wiki and anyone can edit it but I'd rather not make a change unilaterally.

Yes, memory management is hard and is also typically app-dependent, but to say it's a universal issue is just plain wrong.

If people are blindly restarting and not reporting memory management issues to Apple then it's really unhelpful all the way around and not in the spirit of either public or developer betas.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.