Mac bugs and fixes October 26 2026: current status
Chapters
TL;DR
On macOS 27 Golden Gate, dasd consumed 100% CPU for several days, according to OS X Daily, published October 26, 2026; no Apple fix is named. Separately, MacRumors, published October 25, 2026, says browser protections shipped automatically; The Mac Observer, published October 21, 2026, lists RC notification and display problems. The certificate gap for command-line tools and the macOS 27.2 RC issues do not yet have shipped operating-system fixes.
- OS X Daily names a risky PowerLog database reset for runaway dasd.
- MacRumors says browser certificate blocking needs no software update.
- MacRumors says command-line tools still need a future macOS update.
- The Mac Observer recommends enabling missing notifications manually.
What broke on macOS 27 Golden Gate?
OS X Daily says dasd consumed 100% CPU for several days on macOS 27 Golden Gate. The report describes usage hovering between 90-100%, with significant battery drain and resource misallocation. Restarting the Mac and starting in Safe Mode did not stop the excessive usage in the reported case.
The report associates the behaviour with telemetry and the PowerLog background processing database. It says backing up and erasing the PowerLog database, followed by a restart, returned dasd to 0% CPU. The report does not present that association as an Apple diagnosis.
No shipped macOS update fix is named. I also do not know whether Apple has acknowledged the dasd behaviour. Among the current macOS bugs, this one has only a third-party workaround in the cited reporting.
The workaround requires Terminal access and deletion of a system file that is actively being written. OS X Daily warns that something could go wrong and says to make a Time Machine backup first. Its cost is a restart, time spent creating the backup, and the risk attached to deleting an active system file. I would not use the procedure without a complete backup.
Has an Apple security update fixed the certificate gap?
No macOS fix has shipped for command-line tools, MacRumors says. The report says Apple has blocked the compromised eMudhra TLS web certificates since October 19 in Safari, Mail, and apps using Apple networking and security frameworks.
The blocking happens automatically and requires no software update, according to the report. Most people therefore do not need to change anything for ordinary Safari, Mail, or covered app use. The report says there is currently no evidence that the compromised keys were exploited maliciously.
The exception is macOS command-line tools. MacRumors says some can continue accepting the compromised certificates until Apple releases a macOS update with a fix. The report specifically mentions system administrators and says some macOS command-line tools can still accept the compromised certificates. The needed macOS update fix has not shipped.
If command-line certificate validation matters to your work, I recommend postponing that task or using another verified tool until Apple publishes the update. The cost is changing tools or delaying command-line work. I would not alter certificate files without documented instructions for the exact tool and configuration.
What Mac known issues remain in macOS 27.2 RC?
The Mac Observer says macOS 27.2 RC can omit notification prompts after a clean install. The report names Calendar, Maps, Find My, Home and Weather as examples. Apple uses “such as,” so the report says the affected list is not necessarily complete.
Without the prompt, alerts can remain disabled. The documented workaround is to open System Settings > Notifications and turn on notifications for each affected app manually. I recommend checking every app whose alerts matter after a clean installation or new Mac setup. The cost is manual checking and the possibility of missing an alert before the setting is corrected.
The report also lists known issue 188643179 for Macs connected to an external display. Display settings might not be restored correctly, and the display arrangement might change. Apple does not list a workaround in the cited report.
I would open System Settings > Displays after installing the RC and verify each screen’s arrangement and settings. I would not treat a release candidate as proof that either problem is fixed in the final release. No final-release fix is documented in the report.
What can a person do today?
Back up first, then choose the least disruptive action for the problem you actually have. OS X Daily says its PowerLog reset requires deleting a system file and making a backup first. Check Activity Monitor before considering that procedure. If dasd is not consuming excessive CPU, do not delete the database.
For certificate exposure, take no special action for normal Safari, Mail, or covered app use. Avoid relying on affected command-line tools for sensitive connections until Apple ships the promised macOS fix. Do not assume the automatic browser block covers every command-line workflow.
For a clean macOS 27.2 RC installation, open System Settings > Notifications and enable alerts for affected apps. With an external monitor, open System Settings > Displays and confirm the arrangement and individual settings. These checks cost time and may require restoring preferences manually.
I would also compare my previous Mac report before changing a working Mac. The honest status is mixed: browser protection has shipped, but the command-line certificate fix has not. The dasd workaround remains risky, and the RC issues still require manual checks.