Mac bugs and fixes November 1 2026: what shipped
Chapters
Did macOS 27.2 fix unresponsive window dragging?
No confirmed macOS update fix appears in the cited report. 9to5Mac says macOS 27.2 build 26B123 follows reports of failed Electron-app dragging, while restarting helped only temporarily.
The release is available, but availability and a documented repair are different facts. I would install macOS 27.2 for the current release build, then test dragging in every affected app. I would not tell a user that the fault is fixed without a release note or a clean test.
If a window stops responding, save open work before restarting the Mac. Restarting the Mac temporarily resolved the issue. The problem can return, according to 9to5Mac, so restarting is a workaround rather than a durable answer.
I also cannot tell from the report which Electron-based apps fail most often or what triggers the failure. The release candidate carried a different build, so anyone with beta updates enabled may need to disable them before build 26B123 appears. I treat the dragging fault as unresolved until a named release explicitly closes it.
TL;DR
Electron-based app windows on Mac randomly stopped responding to dragging, 9to5Mac reported on October 26, 2026. macOS 27.2 is available as build 26B123, but the report does not explicitly confirm a drag fix. LibreOffice 26.8.2 fixes its macOS 27 startup crash, while Apple's additional certificate fix has not shipped.
- 9to5Mac identifies macOS 27.2 release build 26B123 but does not explicitly document a fix for unresponsive window dragging.
- OS X Daily, published October 26, describes a risky database-reset workaround for dasd consuming 100% CPU.
- MacRumors, published October 25, says an additional macOS certificate fix has not shipped.
- Linuxiac, published October 29, says LibreOffice 26.8.2 fixes a startup crash on macOS 27.
What can stop dasd consuming 100% CPU?
A PowerLog database reset can stop the CPU load, but no shipped Apple repair is documented. OS X Daily says clearing the PowerLog background-processing database and restarting resolved dasd consuming 100% CPU.
OS X Daily describes dasd remaining between 90% and 100% CPU for several days, with battery drain and misplaced processor use on macOS 27 Golden Gate. The report says an ordinary restart, Activity Monitor, and Safe Mode did not resolve the condition.
The workaround involves Terminal 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. I would not use the procedure without a verified backup. Do not use the command if you are uncomfortable deleting a system file.
Check Activity Monitor before taking that risk. If dasd settles after the Mac has finished starting, leave the database alone. If it remains stuck, preserve the backup copy described by OS X Daily before deleting anything. No cited source names an Apple acknowledgment or a point release containing a repair.
Has Apple closed the compromised-certificate gap?
Apple has automatically blocked the compromised eMudhra certificates in Safari, Mail, and apps using Apple networking and security frameworks, but the command-line exception remains unfixed. MacRumors says Apple has blocked the compromised eMudhra certificates since October 19 without requiring a software update.
The block covers Safari, Mail, and apps using Apple networking and security frameworks, according to MacRumors. The report says private keys associated with eight eMudhra intermediate certificate authority certificates were weak. It also says there is no evidence of malicious exploitation.
The remaining exception matters to people using macOS command-line tools. MacRumors says some tools can still accept the certificates until Apple releases a macOS update with an additional fix. That fix has not shipped. I would not present the automatic block as complete protection for command-line work.
For sensitive connections, use a protected Apple application rather than an affected command-line path until Apple names the repaired release. I do not know which command-line tools remain affected. I do not know when Apple will ship the remaining repair.
Which application fix has already shipped?
Install LibreOffice 26.8.2 if LibreOffice crashes during startup on macOS 27. Linuxiac says LibreOffice 26.8.2 fixes the macOS 27 startup crash and non-breaking hyphen rendering on Apple Silicon.
The release also addresses crashes and document problems across Writer, Calc, and Impress, according to Linuxiac. The Mac-specific startup correction is the relevant shipped repair for today. It is an application update, not a macOS point release.
Close documents and make sure they are saved before updating LibreOffice. Reopen the files that previously triggered trouble and confirm that startup and rendering now work. If the crash continues on LibreOffice 26.8.2, record the installed macOS version and whether the Mac uses Apple Silicon.
I hold that most Mac problems worth writing about arrive with a point release or a security update and leave with the next one, so the honest daily question is which build introduced the behaviour and which build, if any, has already taken it away. A named application release already contains one repair, while the operating-system dragging fault and command-line certificate exception remain undocumented as fixed.
What can a Mac user do today?
Install the available updates, test the affected workflow, and avoid the risky database reset unless dasd remains stuck. Thelivenagpur, published October 28, says CERT-In advised Apple users to install Apple's released security updates.
The advisory covers multiple versions of macOS, Safari, and other Apple software. CERT-In warned that the flaws could permit malicious code, sensitive-information access, protection bypass, elevated privileges, or disrupted device operation.
I would first open Software Update and check for macOS 27.2 build 26B123. Disable beta updates if the release build does not appear, as 9to5Mac advises. Then update LibreOffice to 26.8.2 if it is installed.
Restart only after saving work if Electron-app dragging fails. Treat that restart as temporary. Avoid affected command-line certificate handling until Apple ships the additional repair. Back up before considering the PowerLog database procedure. Compare any changed status with my earlier Mac report. The day's Mac known issues do not share one fix, so verify each version separately.