Mac bugs and fixes October 31 2026: current status

What has macOS 27.2 fixed?

macOS 27.2 final build 26B123 fixes the Electron window-dragging bug, according to 9to5Mac. During beta testing, Electron-based app windows could randomly stop responding to drag attempts, while restarting the Mac restored dragging only temporarily before the problem returned, 9to5Mac says.

For this release, 9to5Mac says people with beta updates enabled may need to disable them before Software Update displays final build 26B123 on an affected Mac. I would check the installed build after updating rather than assume that the visible macOS version confirms the final release.

The shipped fix matters more than another temporary restart. Most Mac problems worth tracking arrive with a point release or security update and leave with another one. The useful question is therefore which build contains the correction. For continuity with the preceding status, see my Mac bugs and fixes October 30 2026 report.

Why might macOS 27.2 refuse to install?

Mezha says temporarily disabling Lockdown Mode let macOS 27.2 install. In this report, a 15-inch MacBook Air M5 repeatedly downloaded the update, began installing, restarted, and then returned to macOS 27.1 build 26A434 without a clear onscreen error.

Mezha also records unsuccessful attempts through System Settings, safe mode, the Install macOS 27 Golden Gate application, a bootable USB installer, and a DFU Revive before the Lockdown Mode change succeeded. Apple has not confirmed why that setting affected installation, according to Mezha.

I would treat the workaround as a specific test, not a confirmed general fix. Make a complete Time Machine backup first. Temporarily disabling Lockdown Mode means operating without that setting enabled. Turn it back on after the installation attempt. Do not erase the Mac solely because the update rolls back. The cause remains unknown, and Mezha describes one machine rather than an Apple-acknowledged Mac known issue.

What can you do about dasd using the CPU?

Back up the Mac before considering the database-reset workaround. OS X Daily said on October 26, 2026 that clearing the PowerLog background-processing database and restarting stopped dasd consuming 100% CPU.

In this case, OS X Daily observed dasd hovering between 90% and 100% for several days, with battery drain and processor resources consumed. Activity Monitor, a normal restart, and safe mode did not resolve the behavior, according to OS X Daily.

In this account, OS X Daily names no shipped macOS fix for dasd. The workaround deletes a system file that is actively being written, and OS X Daily warns that something could go wrong. I would not use that Terminal procedure without a current Time Machine backup. The cost is risk to the Mac’s system data and time spent recovering if deletion fails. A restart after the database reset is part of the reported procedure.

Which security fixes have shipped, and which have not?

SecurityWeek said on October 27, 2026 that macOS 27.2 fixes 163 vulnerabilities. SecurityWeek says the newest iOS and macOS releases address 286 vulnerabilities in total, including memory-corruption flaws involving WebKit, the kernel, images, fonts, PDFs, audio, and video files.

I would treat macOS 27.2 as an Apple security update, not merely a feature release. SecurityWeek also describes privilege-escalation flaws, sandbox escapes, Gatekeeper bypasses, and security holes affecting Screen Sharing, Remote Management, and SMB.

MacRumors said on October 25, 2026 that Apple had blocked eMudhra’s compromised TLS web certificates since October 19 in Safari, Mail, and apps using Apple frameworks. For this certificate issue, MacRumors says the automatic block requires no software update for most Apple device owners.

Command-line tools are the exception. For this exception, MacRumors says some tools can still accept the compromised certificates until Apple releases a macOS update containing an additional fix. That macOS fix has not shipped yet, according to MacRumors. Command-line users should follow Apple’s temporary certificate instructions described by MacRumors.

What can a Mac user do today?

Install the offered final release, verify the build, and stop before using risky workarounds without a backup. 9to5Mac identifies 26B123 as the final macOS 27.2 build. If Software Update does not show it, disable beta updates as 9to5Mac advises and check again.

If macOS 27.2 repeatedly rolls back, make a complete Time Machine backup before testing Mezha’s Lockdown Mode workaround. Disable the setting only for the installation attempt, then enable it again. Apple has not confirmed the cause, so I would not erase the Mac or assume storage failure from that symptom alone.

If dasd remains at 100% CPU, restart first and recheck Activity Monitor after the Mac settles. Consider the OS X Daily database procedure only with a current backup and confidence using Terminal. No shipped fix is named in that report.

Install macOS 27.2 for its documented security corrections. Most people need no action for the eMudhra certificates because Apple’s automatic block is active, MacRumors says. Command-line users should apply Apple’s temporary instructions while waiting for the additional macOS fix.