Mac bugs and fixes October 22 2026: what broke
Chapters
Why are notifications missing after a clean install?
Clean installations can fail to request notification permission for some apps. The Mac Observer says clean installs can miss notification prompts for Apple apps in macOS 27.2 Golden Gate RC.
In the release candidate notes covered by the outlet, Apple lists Calendar, Maps, Find My, Home and Weather as examples. Apple's wording means the list is not necessarily complete. A freshly configured app can therefore remain quiet because its permission request never appeared. Calendar reminders and Find My alerts can stay disabled until someone checks the settings manually.
Apple's documented workaround is to open System Settings > Notifications, select each affected app and turn on its notifications. I would check every app that should produce a work alert, not only Apple's examples. The cost is manual configuration for each app and the possibility of missed alerts before that work is complete.
No shipped final macOS update is named as the fix. The known issue belongs to macOS 27.2 Golden Gate RC, so I would not present the release candidate as a notification repair. Apple has acknowledged the behavior through the notes, but the available remedy remains the settings change.
TL;DR
On Mac, clean installs of macOS 27.2 Golden Gate RC can omit notification prompts, while the same build can change external-display arrangements, The Mac Observer said on October 21, 2026. On October 21, 2026, 9to5Mac and BleepingComputer said browser blocks shipped but a macOS trust gap remained; 9to5Mac, published October 19, 2026, described Electron dragging failures. No public operating-system fix is named for these failures; use the available manual settings, browser protections and temporary restart workaround.
- Apple's notification workaround is System Settings > Notifications, The Mac Observer says.
- Apple lists no workaround for the external-display issue, according to The Mac Observer.
- Apple's browser protections have shipped, but 9to5Mac says the macOS trust gap remains.
- Restarting the Mac temporarily restores dragging in affected Electron-based apps, 9to5Mac says.
What changed with external displays?
External-display settings or screen arrangement can return incorrectly after a display is connected. The Mac Observer says external-display settings and arrangement might not restore correctly in macOS 27.2 Golden Gate RC.
The release candidate notes identify the known issue as 188643179. The behavior can leave an external monitor on a different side from the saved arrangement. Settings selected for that display might also differ from the previous configuration. Apple does not provide a workaround in the notes covered by the outlet.
I would open System Settings > Displays after connecting each screen. Check the arrangement and the settings assigned to every display before beginning work that depends on a specific desktop layout. Reapplying the arrangement is a practical response, but it is not a shipped fix.
The available account does not identify every affected display model or setting. It also does not say that macOS 27.2 final removes the problem. The honest status is an acknowledged release candidate issue with a manual check and no documented repair.
Has Apple closed the certificate problem?
Apple has blocked the compromised certificates in its browser protections, but the wider Mac vulnerability has not been fully closed. 9to5Mac says macOS may continue trusting compromised eMudhra certificates after browser makers block them.
The issue involves eight revoked intermediate certificates. Their private keys could be recovered by testing just 256 possible numbers, according to the reports. BleepingComputer says eMudhra attributed the weakness to a script error from April 2025. The company stopped issuing new certificates under its G3 root.
BleepingComputer says Mozilla blocked the certificates through Firefox's OneCRL system, Google Chrome blocked the six intermediates authorized for TLS, and Apple added protections on October 19. Those browser actions are the shipped fixes. They do not establish that macOS has stopped trusting every affected certificate.
9to5Mac says the built-in /usr/bin/curl utility may continue to trust the certificates because its certificate bundle does not check revocation information. The outlet says there is no evidence of use in the wild. It describes an upcoming Apple security update as a likely route to a fix, not as an update that has shipped.
Why can Electron app windows stop dragging?
A beta fault can make windows in Electron-based apps stop responding to dragging. 9to5Mac says beta 4 can leave Electron-based app windows unresponsive to dragging.
The report describes the failures as random. Restarting the Mac temporarily restores dragging, but the behavior can return. That makes a restart a workaround rather than a fix. The behavior can return, so another restart may be needed.
The same report identifies macOS 27.2 release candidate 1 as build 26B118. It does not say that build 26B118 fixes the Electron dragging problem. I would not infer a repair from the arrival of a release candidate when the cited report does not document one.
Save open work before restarting. If dragging fails again, record the affected app and whether other Electron-based apps behave the same way. No permanent macOS update fix is named in the available report.
Which fixes have actually shipped?
Only the browser-level certificate blocks are clearly described as shipped protections. BleepingComputer says Apple added browser protections on October 19.
The notification and display problems remain known issues in macOS 27.2 Golden Gate RC, according to The Mac Observer. Apple provides a manual notification workaround but no listed workaround for the display fault. The operating-system certificate gap also remains, according to 9to5Mac.
The Electron workaround is a restart, not a documented repair. Build 26B118 is identified as macOS 27.2 release candidate 1, but 9to5Mac does not confirm that it resolves dragging failures. I separate release availability from fix confirmation because installing another build is not proof that a named fault has gone.
For continuity with the previous status, compare my Mac bugs and fixes October 21 2026 report.
| Problem | Current status | Action available now | Source |
|---|---|---|---|
| Missing notification prompts | Known in macOS 27.2 Golden Gate RC; no shipped final fix named | Enable affected apps in System Settings > Notifications | The Mac Observer |
| External-display arrangement | Known in macOS 27.2 Golden Gate RC; no Apple workaround listed | Check arrangement and settings in System Settings > Displays | The Mac Observer |
| Compromised certificates | Browser blocks shipped; macOS trust gap remains | Use current browser protections and review reliance on `/usr/bin/curl` | 9to5Mac and BleepingComputer |
| Electron window dragging | No confirmed permanent fix | Save work and restart the Mac temporarily | 9to5Mac |
What can a Mac user do today?
Check the relevant settings and use the documented temporary measures today. The Mac Observer says Apple's notification workaround is manual activation in System Settings > Notifications.
If the Mac received a clean installation of macOS 27.2 Golden Gate RC, inspect Calendar, Maps, Find My, Home and Weather first. Then inspect every other app expected to deliver an alert. This work requires checking and configuring affected apps manually.
For an external display, open System Settings > Displays after connecting it. Confirm the screen arrangement and the setting assigned to each display. Apple has not supplied a documented workaround, so treat manual correction as temporary.
Keep browser protections current for the revoked certificates. Do not assume that a browser block also settles command-line trust. If a work process depends on /usr/bin/curl, ask the person responsible for that process to review the certificate exposure before sensitive retrievals continue.
For an Electron window that will not drag, save open work and restart the Mac. Expect only temporary relief because 9to5Mac says the fault can return. I would wait for a source to name a fixed macOS build before calling any of these unresolved Mac known issues closed.