macOS 27 Golden Gate RC 26A428 fixes a false Disk Utility corruption report (September 9, 2026)
Chapters
What Apple disclosed
Apple Developer's macOS 27 release notes list this under APFS resolved issues: "Fixed: High-RAM Macs running macOS 27 Golden Gate Beta might erroneously report filesystem metadata corruption that doesn't actually exist when running First Aid in Disk Utility or an equivalent operation. (182156751)"
That single line is an acknowledgement and a fix at once, and it is also the entire public record. MacRumors covered the release candidate the same day and documented features only, naming no bug, known issue or regression: its news was that "Liquid Glass opacity has been improved to increase readability", with "A slider for controlling the level of transparency, and changes to shadowing".
So the bug reached the public in the notes that closed it. Anyone who hit it during the beta had no vendor documentation to consult at the time.
| Component | Resolved issue in the release candidate | Radar |
|---|---|---|
| APFS | High-RAM Macs on the betas erroneously report filesystem metadata corruption in First Aid | 182156751 |
| Dock | Applications such as Device Hub shown as running in the background when they are not | 179502922 |
| Dock | Dock might persist when entering and exiting Mission Control from a full-screen app | 174992242 |
| AppKit | Selectable, non-editable NSTextField draws text outside the field's bounds when truncation is enabled | 118196071 |
TL;DR
Macs with large amounts of RAM running the macOS 27 Golden Gate betas could report filesystem metadata corruption that does not exist when running First Aid in Disk Utility, according to the release notes on Apple Developer's undated macOS 27 page, published with the release candidate that MacRumors reported seeded on September 9, 2026. The notes mark it fixed in that release candidate, build 26A428, under radar 182156751. Disclosure and fix arrived on the same day, so the only people who ever met this bug were beta testers on high-RAM machines.
- Apple's wording: high-RAM Macs on the betas "might erroneously report filesystem metadata corruption that doesn't actually exist".
- Fixed in the macOS 27 Golden Gate release candidate, build 26A428, seeded September 9, 2026.
- A false corruption report is the expensive kind, because the right answer to a real one is to stop and restore from backup.
- The same notes fix two Dock bugs and warn that Rosetta is not restored automatically after upgrading to macOS 27.0.
- Apple also seeded a fourth release candidate for macOS Tahoe 26.7 and macOS Sequoia 15.8 that day, with no reason given.
Why a false corruption report costs more than it looks
First Aid in Disk Utility is the tool people reach for when a Mac feels wrong, and metadata corruption is the one result that changes what a careful person does next. The correct response to genuine filesystem metadata corruption is to stop writing to the volume and restore from a backup.
A report of corruption where there is none therefore pushes people toward erasing and restoring a healthy disk, or toward replacing a healthy drive. Apple's own phrasing is that the corruption "doesn't actually exist", and nothing in the notes suggests there was any way to tell a false result from a real one from the outside.
If you ran the Golden Gate betas on a Mac with a lot of memory and acted on a First Aid result in the past weeks, that is the piece of context you were missing at the time.
What else the release candidate's notes fix
Two Dock bugs are resolved. The Dock "might incorrectly indicate that some applications (such as Device Hub) are running in the background when they are not" (179502922), and "While using an app in full screen, the Dock might persist when entering and exiting Mission Control" (174992242). The Finder gets one: suggested names for a file or folder "might be more generic than its contents".
AppKit carries fifteen or more resolved entries, among them a selectable but non-editable NSTextField drawing its text outside the field's bounds when truncation is enabled (118196071, FB13354582).
One line in the same notes is a warning rather than a fix, and it is the one to read before upgrading: "If Rosetta was previously installed, it is not automatically restored after upgrading to macOS 27.0. (163213094)"
Who is affected, and the other candidates seeded that day
The bug was beta-only, and narrower than that: Apple scopes it to high-RAM Macs running the Golden Gate betas, which run only on Apple silicon. If you are on macOS Tahoe, this one never touched you, and the fix is in an operating system you do not have yet.
9to5Mac reported on September 9, 2026 that Apple also seeded macOS Tahoe 26.7 release candidate 4, build 25G229, and macOS Sequoia 15.8 release candidate 4, build 24H23, and that "macOS 26.7 is light on new user-facing features and focuses instead on bug fixes and performance improvements". No reason was given anywhere for a fourth release candidate, which is worth noticing and not enough to explain.
In a separate report the same day, 9to5Mac said Apple had confirmed macOS 27 Golden Gate ships to all users with a compatible Mac on Monday, September 14, 2026, alongside iOS 27, iPadOS 27, watchOS 27, tvOS 27 and visionOS 27. So this fix landed five days before the release it belongs to.
What to do today
If you run the Golden Gate betas on a Mac with a lot of memory, in order: 1. Install the release candidate, build 26A428, because the fix is in it. 2. Re-run First Aid in Disk Utility afterwards and treat that result as the real one. 3. If you erased, restored or replaced a drive in the last few weeks on the strength of a First Aid corruption report on a beta, stop looking for a hardware cause. 4. If Rosetta matters to your work, plan to reinstall it after you upgrade to macOS 27.0: Apple's notes say it is not restored for you.
If you are on macOS Tahoe, do nothing about this one. The useful step for you on September 9, 2026 is separate: macOS Tahoe 26.7 is at a fourth release candidate, so a point release is close, and a Mac that is behind on updates is worth bringing current before a major version arrives.
And if a First Aid run ever does report metadata corruption on a non-beta Mac, act on it. The bug in these notes was specific to beta builds on high-RAM machines. A corruption report outside that set has no published reason to be false.
Frequently asked questions
How much RAM counts as a high-RAM Mac here?
Apple does not say, and neither will I. The release note names "High-RAM Macs" with no threshold, no model list and no memory figure, so the only safe reading is that some beta machines with large memory configurations were affected and Apple has not defined the boundary.
Did any real disk damage come from this?
Nothing in Apple's notes or in the coverage describes damage caused by the bug itself. The risk was the response: a person acting on a false corruption report may have erased or restored a volume that was fine.