First macOS Tahoe 26.4 Beta Now Available for Developers - MacRumors
Skip to Content

First macOS Tahoe 26.4 Beta Now Available for Developers

by

Apple today provided the first beta of an upcoming macOS Tahoe 26.4 update to developers for testing purposes, with the update coming just a few days after Apple launched ‌macOS Tahoe‌ 26.3.

macOS Tahoe 26 Thumb 2
Developers can download the ‌macOS Tahoe‌ 26.4 update by opening up the System Settings app, selecting the General category, and then choosing Software Update. Beta Updates will need to be enabled, and a free developer account is required.

‌macOS Tahoe‌ 26.4 could introduce some new Siri features, though at least some of the capabilities that we were expecting have been delayed. The update is also expected to introduce new emoji characters.

The beta is available to developers right now, but a public beta is expected in the next week or two.

Related Roundup: macOS Tahoe
Related Forum: macOS Tahoe

Top Rated Comments

E
ericfroemling
8 weeks ago
Compact tabs is back :)

Attachment Image
Score: 10 Votes (Like | Disagree)
T
tywebb13
8 weeks ago
build number is 25E5207k

others:

macOS 15.7.5 RC 1 (24G607)
macOS 14.8.5 RC 1 (23J407)
iOS 26.4 beta 1 (23E5207q)
iPadOS 26.4 beta 1 (23E5207q)
tvOS 26.4 beta 1 (23L5208m)
audioOS 26.4 beta 1 (23L5208m)
visionOS 26.4 beta 1 (23O5209m)
watchOS 26.4 beta 1 (23T5209m)
Score: 3 Votes (Like | Disagree)
T
tywebb13
8 weeks ago

Same here! :-( My external drives work fine on another Mac not running this beta, of course.
maybe disable fsck_hfs before attaching drives?


* 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):
[LIST=1]
* Boot into Recovery Mode (Command+R) and run csrutil disable in Terminal to disable System Integrity Protection.
* Restart the system.
* 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
Score: 1 Votes (Like | Disagree)
johnsawyercjs Avatar
johnsawyercjs
8 weeks ago

Checked file vault settings, but they were turned off, I thought Tahoe by default enabled encryption of home folder? :rolleyes:
I don't think Apple has ever enabled FileVault by default, since the user needs to know if their drive is encrypted, and select settings that work for them. A full setup requires the user to establish a "backup" unlock method in case you forget your macOS password. You can choose to use your Apple ID to reset your Mac's password to unlock your drive, or use a local recovery key (a long string of random letters and numbers).

Also, FileVault has encrypted the entire drive for years. You might be remembering "Legacy FileVault," which encrypted only the Home folder, but Apple moved away from that years ago (around Mac OS X Lion) since it was prone to errors and didn't protect system files or temporary data stored outside the Home folder. Modern FileVault uses XTS-AES-128 encryption with a 256-bit key to secure the entire volume.
Score: 1 Votes (Like | Disagree)
auslad88 Avatar
auslad88
8 weeks ago
I updated, but instant issues with external drives. I have a few RAID volumes formatted as macOS Journaled - all of these are readable but not writable - prompts to run disk utility in recovery mode - did that and still no joy. Even a Samsung T7 that is formatted macOS Journaled has the same error. I formatted as APFS and it works fine, but formatting back to Journaled throws the same error. so for some reason my upgrade does not like Journaled anymore :/.. I had also updated another Mac to 26.4 and has the same issue :)
Score: 1 Votes (Like | Disagree)
L
Larsen2k4
8 weeks ago

FINALLY.

I'll slow down on my complaining about Tahoe now lol
HOORAY!
Score: 1 Votes (Like | Disagree)
Read All Comments