Mac bugs and fixes October 20 2026: what shipped

What broke on Mac?

The reported break is Cursor 3.25.6 failing to install from the update menu on macOS 27, and Forum Cursor documents no shipped fix. The report gives one reproduction step: install the latest update from the menu. It does not provide a successful installer path, a build number, or a working workaround. It does not include confirmation from Cursor or Apple that the installation failure is a known bug.

I would put the Cursor failure on a Mac known issues list, but I would keep its scope narrow. The evidence is one bug report about the in-app update path. It does not establish that every Cursor 3.25.6 installation fails. It also does not establish that macOS 27 itself blocks the installer.

My earlier Cursor updater report provides continuity for the same updater topic. The useful distinction remains the same: a reported failure is not a documented operating-system regression until a named source connects the behavior to macOS. I do not have that connection yet. I also do not have a manual-install result, so I would not present manual installation as a verified workaround.

Has a macOS update fix shipped?

No public macOS Golden Gate 27.2 fix has shipped; MacRumors says Apple seeded only the release candidate to developers. The report says the release candidate followed the fourth beta and describes a launch toward the end of October. A release candidate is therefore available through the beta path described by the report, not as the finished public release.

The report also says macOS Golden Gate 27.1 fixes unspecified bugs. It does not identify the Cursor installer failure among those fixes. It does not connect macOS Golden Gate 27.2 to Cursor 3.25.6 either. I therefore cannot call either point release a fix for the reported installation failure.

I would not describe the release candidate as an Apple security update. The cited report does not provide that characterization or name security fixes for the release candidate. I treat the point-release status as central because Mac problems often arrive with one release and leave with another. Waiting silently is not useful advice. The honest status is that no cited source names an operating-system fix for Cursor, and the next public point release has not shipped.

Which fixes have actually shipped?

Default Folder X 6.3.3 is the shipped fix for the Save-dialog regression described by TidBITS. The account says Default Folder X 6.3.1 corrected a Golden Gate bug that immediately opened a folder after a single click in a Save dialog. That release also addressed pop-up menus in Save dialogs and pinning recent items in a topmost menu.

The account says Default Folder X 6.3.2 resolved a conflict that could prevent selection from Save-dialog pop-up menus while Apple's Weather icon appeared in the menu bar. It also improved the drag target used when dragging files in the Finder.

The account says Default Folder X 6.3.3 revisits the previous pop-up menu fix because that fix broke Save dialogs in macOS 12 Monterey and earlier. The revised fix is described as working on all systems. TidBITS also documents the hidden Work around macOS 27 process ID bug option, reached by holding Option while choosing Settings from the Default Folder X menu.

I would keep these macOS bugs separate. Default Folder X 6.3.3 is a shipped application fix. It is not evidence that Cursor 3.25.6 can now update, and it is not the public release of macOS Golden Gate 27.2.

What can you do today?

Forum Cursor documents no shipped fix, while TidBITS documents Default Folder X 6.3.3 as shipped. For Cursor, I would keep the currently working version and avoid repeating the failed in-app update. The cost is remaining without Cursor 3.25.6. Save the exact error, note whether the failure occurs before installation begins, and record the update path used.

If you submit more detail, include a concise description, reproduction steps, expected behavior, and relevant system information. The bug-report template asks for a clear description, reproduction steps, expected behavior, and additional information. I would not erase the working application or assume that a standalone installer succeeds. Neither action has a verified result in the cited report.

For Default Folder X, install 6.3.3 if the documented Save-dialog problem applies to your Mac. If the macOS 27 process ID problem remains, use the exact hidden option documented by TidBITS and record whether behavior changes. That workaround costs a settings change and should be reversed if it does not help.

For macOS itself, stay on the public release unless you intentionally test beta software. Check Software Update when Golden Gate 27.2 becomes public. Read its release notes before treating it as the missing fix. I still do not know whether Apple or Cursor will name the installer failure in those notes.