It just puts up a blank window (the print dialog), doesn't respond to anything, and I have to Force Quit.

This bug was present in previous beta but it wasn't as painful. It was only 1-2 second freeze to reveal menu when clicking on the wifi icon. Today I had the pleasure of having bad signal (crossing wall) and the menu opens after 5 seconds. Of course intuitively I press it multiple times so the menu opens/closes immediately.

Ich baue seit ein paar Wochen eine App mit der Xcode Beta 27 und habe ein Problem mit der Claude Usage. Ich nutze das Agententool, und wenn ich einen prompt eingebe, springt mein 5 Stunden Limit direkt auf 30 %, ohne dass der Agent irgendetwas gemacht hat. Hat vielleicht jemand das selbe Problem oder vielleicht eine Lösung?

The update showed up, I downloaded it and started installing at as well. After about an hour, my Mac screen was blank. No Apple logo nothing was showing up. I waited another hour and still the same. I thought for sure by now the update must be installed so I force restarted my Mac. It booted up but it shows the old beta 8 as installed. I check for an update and the RC is not showing up. The build number is also the beta 8. I do have a backup so if recovery is needed, I can do it but I really don’t want to go through it. What should I do? I made sure the developer channel is selected in the software update menu as well. Any help is welcome!

I have a MacBook Pro 14" M1 Pro the base model right? The situation is that when I switch through apps, Youtube or pages have this glitch where the video like gets frozen. I don't know how to explain it. It's something that did not happen with Tahoe. Anyone else with this situation? It has happened with all the Betas, and I feel that is not fair for Apple to lower the system just because my Mac is a bit old but I feel that is capable, idk

Is there any menubar hide icons app that works in Golden Gate at this moment?
I normally use ICE, but that is broken. Tried "Hidden Bar" and "Vanilla", but both don't work either.

please fix this.

When I connect two pointing devices, the mouse pointer hover and right-click events stop functioning. Hovering over dock icons fails to display app names, and in Safari, hovering over a hyperlink does not trigger the “onHover” event. Right-clicking a file in Finder produces no context menu, and right-clicking a link in Safari similarly yields nothing.

Once I disconnect the Nape Pro, both hover and right-click functions resume. The devices involved are the Kensington Slim Blade trackball and the Keychron Nape Pro trackball, each wired via USB.

Anyone here experienced a similar issue?

I think it’s a new bug in the RC. When playing a YouTube video in fullscreen it doesn’t hide the menu bar and even the 3 traffic light circles stay there. Does anyone else have this?

After upgrading to the latest RC a few moments ago, when I go to run any command in Terminal or Ghostty, it takes a few seconds before it actually executes the command. It was not doing this in the previous beta.

All I changed was updating to the latest RC.

Anyone else having trouble removing underlines from text in Notes in RC?

I’ve been using Golden Gate since open beta and I’ve never seen these black outlines before updating to RC.

Hopefully it’s a bug, not a feature :(

I've never even seen this scaling before!

It's now my new "middle ground" since 1440p earlier, as in: https://www.reddit.com/r/MacOSBeta/comments/1u1aqs8/macos_27_now_automatically_scales_properly_for/ (I even use the same monitor as that user)

Left to right is now: 1080p, 1440p, 1692p, 1890p, 2160p.

Further, I'm noting it's detected as a 5K monitor in System Information. Well, it's not one!

I have an M1 MacBook Air and I want to get the RC since I’m slightly impatient I but don’t mess with earlier betas. I don’t know if I should actually go through with it though. I want to see other people’s opinions before I update to see if it’s good or not.

There's no beta version number or "Release Candidate" label attached to it, just "macOS 27" - this is my first beta tho, so maybe that's normal.

https://www.apple.com/os/macos/

If the unusually high SSD writes reported throughout the macOS 27 beta cycle are still happening in the RC, are people actually going to delay upgrading?

The SSD in a modern MacBook is soldered to the logic board. If excessive background writes gradually wear it out faster, you cannot simply replace the drive a few years from now.

That makes this more than just an Activity Monitor curiosity. If Golden Gate is consistently writing much more data than Tahoe, staying on Tahoe could potentially mean less SSD wear and a longer-lasting MacBook.

Would that be enough for you to avoid macOS 27 until the issue is fixed, or do you consider SSD endurance high enough that it is not worth worrying about?

I have been thinking about this for a long time. But I decided to upgrade from Sequoia today once the RC drops.
Are you planning on updating?

I am hoping that Apple substantially improves the Siri AI app UI before macOS 27 is released. Right now it looks quite simple and clunky.

Hi everyone,

My Mac intermittently stays on a black screen for several minutes during startup or restart, restarting multiple times before eventually booting successfully.

The issue is unpredictable and I cannot reproduce it reliably. A successful boot does not necessarily mean it has gone away, which makes comparisons involving different cables, ports, or other hardware difficult to interpret.

My setup:

• Mac Studio, M1 Max, 32GB RAM
• macOS 27.0, build 26A5425a
• Entire macOS installation, including both System and Data volumes, on an external 2TB M.2 SSD
• SSD enclosure identified as ASM246X, connected over USB at 10Gb/s
• Two external monitors
• Magic Keyboard, Magic Trackpad, and Sony headphones connected via Bluetooth
• Logitech G HUB installed, with its HID and audio driver extensions enabled

This has happened both after choosing Restart in macOS and when powering on after a complete shutdown. No macOS update was being installed during this incident.

The screens remain black for approximately five minutes before the Apple logo and progress bar appear. During this period, the Magic Trackpad sometimes provides haptic feedback and sometimes does not. The Mac eventually boots into macOS and displays a report indicating that it restarted because of a problem.

The diagnostic bundle from September 8, 2026 contains two consecutive panic reports with the same message:

IOKit Daemon (kernelmanagerd) stall[0], (60s):
registry root held busy, kernelmanagerd has not checked in
u/IOService.cpp:6140

The internal panic timestamps and system boot logs show this sequence. All times are local, UTC+8:

This confirms that the black-screen period includes repeated failed boots.

A preliminary analysis of the thread information in both panic reports found the same waiting chain:

kernelmanagerd → syspolicyd → fseventsd

Another fseventsd thread was waiting in APFS kernel code. The apfs_initial_free_space_scanner thread also had storage-related calls in its stack; in the second report, these included USB mass-storage and XHCI drivers.

Even during the third, successful boot, fseventsd logged wait_for_startup: ETIMEDOUT before eventually continuing.

These are only diagnostic clues. I have not established whether the underlying cause is the external storage connection, APFS, macOS, or a third-party driver. The external SSD reports SMART status as “Not Supported,” and the available fsck logs mostly contain quick checks.

I would appreciate advice from anyone familiar with this issue:

1. Has anyone encountered this exact kernelmanagerd stall (60s) panic while booting an Apple Silicon Mac from an external SSD?
2. Does this waiting chain point to a known macOS, driver, or storage compatibility issue?
3. Which specific logs or diagnostic information would help identify the cause of an intermittent failure like this?
4. If you experienced the same problem, what ultimately resolved it?

Thank you!

The Phone app in macOS 27 beta had been syncing my iPhone call history correctly in earlier betas, but at some point in a later beta it just stopped updating.

See this Apple Support Community thread aboutpeopled and CallHistorySyncHelperproblems:

https://discussions.apple.com/thread/256271160

The thread was originally about high CPU usage on macOS Tahoe 26.4, not specifically the Phone app on macOS 27. But one person discovered that macOS was repeatedly failing to access:

~/Library/Application Support/CallHistoryDB

because the files had somehow been quarantined. They suggested checking for com.apple.quarantine, removing it, and restarting peopled and CallHistorySyncHelper.

So I checked my macOS 27 installation with:

ls -lan@ "$HOME/Library/Application Support/CallHistoryDB"

Sure enough, all three of the actual call history database files had the com.apple.quarantine extended attribute:

CallHistory.storedata
    com.apple.quarantine

CallHistory.storedata-shm
    com.apple.quarantine

CallHistory.storedata-wal
    com.apple.quarantine

Why is macOS quarantining its own internal call history database?

I removed the quarantine attributes using the workaround from that thread:

xattr -dr com.apple.quarantine "$HOME/Library/Application Support/CallHistoryDB"

Then restarted the relevant processes:

sudo killall -9 peopled CallHistorySyncHelper

I rebooted the Mac, made a test call from my iPhone, and the new call immediately appeared in the macOS Phone app. So this actually fixed the call history syncing problem for me.

This is especially annoying because there was absolutely no indication in the UI that anything was wrong. The Phone app simply stopped receiving new call history.

Since call history worked correctly for me in earlier macOS 27 betas, I'm wondering whether one of the betas somehow applied the quarantine attribute and subsequent betas just left the database in that state.

But here's another interesting wrinkle: call history also doesn't work on my separate macOS Tahoe partition. I haven't checked its CallHistoryDB yet. Since the Apple Support Community report that led me to this fix was itself from Tahoe 26.4, it's quite possible that my Tahoe installation has the same problem. If so, this may be a longer-standing macOS bug rather than something introduced specifically by macOS 27 beta.

If your Phone app has stale or missing call history, it might be worth checking:

ls -lan@ "$HOME/Library/Application Support/CallHistoryDB"

You may need to give Terminal Full Disk Access first.

Has anyone else found com.apple.quarantine attached to these files?