macOS Tahoe 26.4 Beta 1 - Bug fixes, changes, and more

[losthismarbles]

if plugged in while turned off, is more of an issue for me

That shouldn't be an issue for you, though i do understand the sentiment.
(what you're after would have been a lot more complex, phrased/offered differently and with potential security risks involved; you'd need to keep a part of the CPU and its internal mini-OS active, deeper than the deepest sleep state currently possible, controlling something actively without the monitoring it would/should have had when operating under a non-sleep state. Or, have them manufacture a separate chip, on waffer, or of a different nanometer process [costs] linked through the interposer, dedicated to just doing that; this would seriously complicate waffer yields or assembly process respectively. And then they'd need to figure a way to power that, so that even when the rest is down, it could function independently.. No way)

What i did to avoid your "issue" (in conjunction with using using Battery Toolkit currently, but it applies for a post 26.4 OS as well), was construct my own remote start.
Magsafe cable -> Apple Charger -> Apple Charger's power cable -> Remote Start -> Remote start's power cable to power distributor/straight to wall plug.
Remote Start has a simple switch configuration, perma-adhesive taped in a nice matching "aluminium" coloured DIY metal mini-chassis under my desk. If i need to power the Mac down and keep it down, for whatever reason, i plug the switch, i kill the power delivery, even though charger's still plugged. Nice and simple, 100% control.

Software ensures the MacBook adhers to my 80% limit when powered on, remote start ensures this sticks after a shut down. No plugging and re-plugging. Charger hasn't been touched since late July, when i bought this MacBook 🙂

 

[PotentPeas]

The fact it ignores that limit and charges up to 100% if plugged in while turned off, is more of an issue for me!

I wonder how much of an issue Apple "thinks" this is.
How many people actually "turn off" their MacBook? (Genuinely curious.) If you do fully power it off regularly ....... Why?

I leave mine powered on all of the time (just allowing the display to power off on idle). I personally disable "sleep mode" on mine, because I want to be able to leave it running jobs or access it remotely. It is so "efficient" at idle that it can last >24 hours "awake" (with screen off) on battery power. And it doesn't generate much heat or need to run the fans, so I don't even shut it down for travel. I just shut the lid and stick it in the carrying pouch, like I would for an iPad.

But, even beyond me, I suspect that "most people" just allow it to idle to sleep, rather than completely shut it down.

If Apple has metrics that says that most people use sleep and not full shut down, their motivation to "fix" this will be low. I have to believe that they could fix it in firmware, but right now they have implemented this as an OS-level control only.

I'm also wondering what the behavior is on iPhones that support the charge limit. My iPhone 12 Pro doesn't have this function, it is too old. But would a newer iPhone, with charge limit set, fully charge the battery if left plugged in while "powered off"?

 

[Wolf1701]

But, even beyond me, I suspect that "most people" just allow it to idle to sleep, rather than completely shut it down.

If the aim was to partially replicate the functions of “Al Dente,” okay, but if I choose to recharge to 80% in the operating system, it's reasonable to expect it to do so. Of course, I can put it on standby, but I believe that everyone can and should use their device as they see fit.

 

[adrianlondon]

That shouldn't be an issue for you, though i do understand the sentiment.
(what you're after would have been a lot more complex, phrased/offered differently and with potential security risks involved; you'd need to keep a part of the CPU and its internal mini-OS active, deeper than the deepest sleep state currently possible, controlling something actively without the monitoring it would/should have had when operating under a non-sleep state. Or, have them manufacture a separate chip, on waffer, or of a different nanometer process [costs] linked through the interposer, dedicated to just doing that; this would seriously complicate waffer yields or assembly process respectively. And then they'd need to figure a way to power that, so that even when the rest is down, it could function independently.. No way)

There's enough going on while charging so that it knows whether to charge or not and what colour to put on the little light on the connector!

They could just write "80%" to NVRAM somewhere. They store other stuff there, so it should be easy to do.

However, as @PotentPeas says, I suspect most people just shut the lid and get on with their life! Not me. I sometimes shut down at night and boot it back up the following morning. But then I also turn my modem/router off those nights too, so I know I'm not normal 😁

 

[Wolf1701]

But then I also turn my modem/router off those nights too, so I know I'm not normal 😁

Okay, you're not normal. 😂 But you should be able to do it.

 

[Dirty Mac]

Not sure if anyone else is having this issue but aftter I updated, my trackpad and bluetooth keyboard will not connect. I also ran into the issue that one of my hard drives would be read only. Anybody having issues like this?

If I shut down or restart my mac mini, the trackpad and keyboard won't connect so can't login. Have to connect the keyboard by wire to login.

 

[mlemonds]

Not sure if anyone else is having this issue (or has a similar setup). I have a 4-bay Sandisk G-Raid and it seems that the driver for that is not getting along with this beta. I get a pop-up when mounting that the drive can not be repaired and is in read only mode.

No issues when connecting to a 26.3 machine

 

[PotentPeas]

Not sure if anyone else is having this issue (or has a similar setup). I have a 4-bay Sandisk G-Raid and it seems that the driver for that is not getting along with this beta. I get a pop-up when mounting that the drive can not be repaired and is in read only mode.

No issues when connecting to a 26.3 machine

If it is formatted HFS+, it's the same issue widely reported earlier in this thread. Known issue, maybe fixed in the next beta.

 

[losthismarbles]

They could just write "80%" to NVRAM somewhere. They store other stuff there, so it should be easy to do.

With due respect, but for the second and last time, you do not appear to grasp what you're requesting, not even the basics frankly (absolutely nothing to do with memory), let alone the degree of difficulty to implement it.

Regarding your router and by all means ignore, there isn't a single scenario where shutting it off could be of assistance. You're only wearing it down powering it on and off every day, it isn't meant to function like that. But, it's your device, so by all means 🙂


On topic again!
Since all i got was "opinion" on "why it should or shouldn't", and nothing on whether this occurs to others or not?

If you're running the Beta, put the charging cap in 80%, plug the Mac in your charger, leave it consta-plugged in for at least a full day.
Then -again, at least a day later-, unplug from the charger so it's on battery and while unplugged, reboot immediately.

When it logs you back in, is your battery showing at 83, 84, 85% ?
* this hasn't ever happened to me with either Al Dente or Battery Toolkit, so was wondering if it's.. me, or more of a general thing.

 

[b183]

My 2019 MacBook Air(Intel) when I click about this Mac states processor is M4 2025 Have rebooted it twice and still no change

 

[Wolf1701]

My 2019 MacBook Air(Intel) when I click about this Mac states processor is M4 2025 Have rebooted it twice and still no change

Try to reset NVRAM/PRAM

Although I would keep the free upgrade 😉

 

[Adora]

My 2019 MacBook Air(Intel) when I click about this Mac states processor is M4 2025 Have rebooted it twice and still no change

Could be just a displaying bug. Something is wrong with System Information in general. I don't even see all USB devices listed that are connected and working.

And the "Micro Firmware Version" in the Thunderbolt/USB4 section is showing 0.0.0 for all three Thunderbolt 5 busses.

Was already the case in the final 26.3.

 

[WilliApple]

My 2019 MacBook Air(Intel) when I click about this Mac states processor is M4 2025 Have rebooted it twice and still no change

This sounds more like an OpenCore Legacy Patcher issue, the 2019 MacBook Air is not supported with macOS Tahoe and unsupported Macs should be discussed here:

macOS Tahoe 26 on Unsupported Macs Discussion

macOS Tahoe is officially the last macOS to support Intel Macs, as confirmed by Apple. This will be quite a long thread, I'm sure. The official minimum requirements are as follows: Current state: See post #258: The devs have initial patches for many Macs already, but non-Metal macs will not be...

forums.macrumors.com

 

[Adora]

 

[nmt1900]

That shouldn't be an issue for you, though i do understand the sentiment.
(what you're after would have been a lot more complex, phrased/offered differently and with potential security risks involved; you'd need to keep a part of the CPU and its internal mini-OS active, deeper than the deepest sleep state currently possible, controlling something actively without the monitoring it would/should have had when operating under a non-sleep state. Or, have them manufacture a separate chip, on waffer, or of a different nanometer process [costs] linked through the interposer, dedicated to just doing that; this would seriously complicate waffer yields or assembly process respectively. And then they'd need to figure a way to power that, so that even when the rest is down, it could function independently.. No way)

What i did to avoid your "issue" (in conjunction with using using Battery Toolkit currently, but it applies for a post 26.4 OS as well), was construct my own remote start.
Magsafe cable -> Apple Charger -> Apple Charger's power cable -> Remote Start -> Remote start's power cable to power distributor/straight to wall plug.
Remote Start has a simple switch configuration, perma-adhesive taped in a nice matching "aluminium" coloured DIY metal mini-chassis under my desk. If i need to power the Mac down and keep it down, for whatever reason, i plug the switch, i kill the power delivery, even though charger's still plugged. Nice and simple, 100% control.

Software ensures the MacBook adhers to my 80% limit when powered on, remote start ensures this sticks after a shut down. No plugging and re-plugging. Charger hasn't been touched since late July, when i bought this MacBook 🙂

All this hints that new native charge limit setting option is not able to achieve more than AlDente Pro can offer. Actually even less because AlDente Pro has a setting that can keep machine awake (with screen off) until charge limit is reached and then put it to sleep. Only shortcoming of AlDente is that it has to be running for limit to be applied...

 

[Saturn1217]

deleted

 

[Jinhu]

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

It's temporary and not damaged, I wrote a quick guide to allow mounting

Workaround: macOS 26.4 beta won’t mount HFS+ volumes properly

Problem

On macOS 26.4 beta, some HFS+ (Mac OS Extended) external drives/partitions fail to mount normally or appear read-only. This is a known beta bug. The data is usually fine — the OS just can’t auto-mount them correctly.

Good news
You can often mount them manually via Terminal and access your files.

Step-by-step workaround

1. Find the disk identifier
Open Terminal and run:
diskutil list
Look for your partition, e.g.:
* disk5s2
* disk5s3
* etc.

2. Create a mount folder (one per partition)
Pick a simple name and create a folder under /Volumes, for example:
sudo mkdir /Volumes/Drive1
You can repeat this for other partitions, e.g.:
sudo mkdir /Volumes/Drive2
sudo mkdir /Volumes/Drive3

3. Mount the partition manually (HFS+)
For each partition, run:
sudo mount -t hfs /dev/disk5s2 /Volumes/Drive1
(Replace disk5s2 and /Volumes/Drive1 with your actual disk ID and folder.)
Repeat for other partitions, e.g.:
sudo mount -t hfs /dev/disk5s3 /Volumes/Drive2
sudo mount -t hfs /dev/disk5s4 /Volumes/Drive3

4. Check it worked
ls /Volumes/Drive1
If you see your files, it’s mounted.
You can also run:
mount
to see all mounted volumes.

Important notes
* This is a temporary workaround for the beta bug.
* You may need to repeat this after a reboot.
* Treat the drive gently:
* Reading and copying data is fine.
* Avoid big deletes, moves, or heavy write activity until Apple fixes the bug.
* Do not reformat unless you already have a verified backup.
When to stop using this
When Apple releases the next beta or a fixed build:
* Reboot
* Check if the drives mount normally again
* If they do, you can go back to using them as usual and delete the temporary folders in /Volumes.

 

[Adora]

It's temporary and not damaged

Thanks but I already found by booting into Sequoia. I deleted them there because they were not needed anymore.

macOS Tahoe 26.4 Beta 1 - Bug fixes, changes, and more

I have a problem. I just booted into a clean Sequoia installation that is just sitting there on another partition waiting for my never happened downgrade since months. I started Disk Utility and ran first aid on all four "damaged" internal HFS+ partitions that only included bootable macOS...

forums.macrumors.com

 

[losthismarbles]

..
How are you "testing" the Beta when instead of troubleshooting, you just go on and remove the problematic aspect? 🙂

On the topic of external drives;
Since 26.1 it's been a roller coaster for so many third party apps having to do with external storage. Some even had to resort to major rewrites. I'm kinda guessing the collective /sighs this little update will have brought about.
(and in terms of SMB in particular, reading said apps' change notes? I'm honestly not so sure what Apple's thinking here)

* Also, my dear invisible senior Apple developer, reading this now (hah). Could you please, even now, after all these years, add native, full SMART support for external drives? Like really? Some of us work on these machines, we don't buy them for social status; just in case it's escaped you.

 

[Wolf1701]

* Also, my dear invisible senior Apple developer, reading this now (hah). Could you please, even now, after all these years, add native, full SMART support for external drives? Like really? Some of us work on these machines, we don't buy them for social status; just in case it's escaped you.

We apologize, we have carefully evaluated the proposal and decided that LG and SMART are an oxymoron.

 

[losthismarbles]

..we have carefully evaluated..

That's the wording alright, spot on 😁

* being happy with my brand new MacBook, i've purchased and maintain a Win-doze machine just so i can have something with which to occasionally monitor my ext. drives.. i mean, is that an oxymoron or what?

 

[Wolf1701]

That's the wording alright, spot on 😁

* being happy with my brand new MacBook, i've purchased and maintain a Win-doze machine just so i can have something with which to occasionally monitor my ext. drives.. i mean, is that an oxymoron or what?

On a more serious note, I did the same... with three Macs at home, I had to keep a PC mainly for SMART and NVME firmware upgrades.

 

[mikecwest]

Weirdest issue... I think your date and time settings or language and region settings might be messed up because theres no way Apple would ship this even in a beta lol

 

[mikecwest]

Weirdest issue... I think your date and time settings or language and region settings might be messed up because theres no way Apple would ship this even in a beta lol

Apparently Apple removed the ability to set the time date format...not sure HOW it got set this way, but after a very frustrating with this jerk ChatCPT, I finally solved it yesterday.

>>
defaults delete -g AppleICUTimeFormatStrings
defaults delete -g AppleLocale

killall Finder

>>

I tried updating the first post, but was having issues.....it said it was "disabled for lent?", I will try again.