Mac bugs and fixes September 25 2026: no fix yet

What broke in macOS 27?

Mission Control was broken for some macOS 27 users, TechRadar reported on September 21, 2026.

TechRadar’s September 21, 2026 account says users encountered sluggish or broken Mission Control animations, while moving a desktop to another monitor could leave an unresponsive black screen behind. The report describes complaints from people who depend on multiple desktops, but it does not establish how many Macs are affected or identify a hardware pattern.

No macOS update fix for Mission Control is identified by TechRadar’s September 21, 2026 report or Macobserver’s September 21, 2026 account of macOS 27.2 Beta 2 build 26B5091g. Apple acknowledgement is also absent from the named reports. I therefore cannot call the beta a remedy.

The immediate workaround is to avoid dragging desktops between monitors and to use ordinary window switching when Mission Control becomes unreliable. That workaround costs the multi-desktop workflow that affected users rely on, and TechRadar’s September 21, 2026 report gives no indication that restarting or changing a setting permanently resolves the fault.

Why is battery life worse after macOS 27?

Poor battery life followed macOS 27 installation for some users, Osxdaily reported on September 22, 2026.

Osxdaily’s September 22, 2026 account describes reduced battery life alongside sluggish performance and a Mac becoming warm or hot, which it associates with substantial system activity running in the background. Its specific MacBook Air example fell to just over 2 hours of use after the final macOS 27 release, but one machine does not establish a general runtime.

The same September 22, 2026 Osxdaily report says temporary battery reduction commonly follows a major system update and may also involve third-party incompatibilities or bugs. It does not name a shipped point release that corrects the problem, so I would not install macOS 27.2 Beta 2 solely to chase longer runtime.

My practical workaround is to plan for external power while the Mac is warm, sluggish, or busy after the upgrade. The cost is reduced mobility. Osxdaily’s September 22, 2026 report does not promise when background activity will finish or that waiting will correct every battery complaint.

Does macOS 27.2 Beta 2 fix the known issues?

macOS 27.2 Beta 2 is a test build, not a public fix, Macobserver reported on September 21, 2026.

Macobserver’s September 21, 2026 report identifies the beta as build 26B5091g, replacing build 26B5086k from five days earlier, but says Apple supplied no separate consumer-facing change list. Claims that build 26B5091g fixes Mission Control, battery life, particular apps, performance, or battery endurance would therefore be premature.

Analyticsinsight reported on September 22, 2026 that Apple’s notes still listed possible Xcode crashes during code-completion ranking, notification trouble after a clean installation, and a Shortcuts “Describe a Shortcut” problem. Geeky Gadgets’ September 22, 2026 report also says the Spotlight-related Siri animation glitch, App Store subscription syncing, and missing Calendar or Maps notifications on clean installations remained unresolved.

These macOS bugs are reasons to treat build 26B5091g as evidence of continuing work, not evidence of delivered repairs. My previous Mac report also tracks the beta gaps without treating a preview as a finished release.

Has Sequoia 15.8.1 delivered a fix or security update?

Sequoia 15.8.1 RC 2 remained prerelease build 24H212, Macobserver reported on September 21, 2026.

Macobserver’s September 21, 2026 report says Release Candidate 2 targets Macs staying on the Sequoia branch, but Apple had not published specific fixes assignable to build 24H212. The RC label means Apple can promote the build after testing or replace it with another candidate, and the report gives no confirmed public-release date.

No Apple security update advisory was attached to the prerelease build in Macobserver’s September 21, 2026 account. Specific vulnerability claims must therefore wait for Apple to publish security content for a public update.

I would not install build 24H212 on a work Mac merely because it is near final. Macobserver’s September 21, 2026 guidance says people who do not test applications or managed deployments should wait for the public build and final release notes. Waiting costs early access to whatever undocumented maintenance changes the candidate may contain.

What can a Mac user do today?

Most users should remain on the public macOS release, Macobserver advised on September 21, 2026.

If Mission Control fails, I would stop moving desktops between monitors and use ordinary window switching until Apple names a fixed build. TechRadar’s September 21, 2026 report supports avoiding the trigger because a cross-monitor desktop move could leave an unresponsive black screen, although the report supplies no permanent workaround.

If battery runtime fell after macOS 27, I would keep power available while the Mac remains warm, sluggish, or busy. Osxdaily’s September 22, 2026 report associates those symptoms with background activity but leaves the duration and final outcome unknown.

A developer who must test build 26B5091g can use System Settings, General, Software Update, and Beta Updates, according to Analyticsinsight’s September 22, 2026 report. That report says Apple recommends backing up before beta installation because preview builds can contain bugs and compatibility problems. Macobserver’s September 21, 2026 report says a secondary Mac or separate test volume is safer, with the cost of dedicating storage or hardware to testing.

For everyone else, the honest action is to wait for a public point release with explicit notes. A release candidate or beta without named repairs does not close a known issue.