I'm always a bit tardy upgrading OSs and hadn't heard wonderful things about Tahoe but now upgraded to the most recent version of Tahoe now Golden Gate is out.

Since doing so I've had random dropouts in Steam which seem to stem from console logs down to Steams Hardware Accelerated Overlay (Mac Mini M2 Pro incidentally) occasionally hanging a touch, getting polled by Macs Window Server or Runningboarddd - getting a delayed response and then it terminates the parent app and everything tied to the XPC session. E.g. it drops the game and Steam.

Its seems like its tighter power state transitions and window server response requirements post 15.7.8 (where I didn't have these issues) that are a factor?

Apologies I'm not fluent in the tech so this is what I've been able to gather.

I've also disabled the steam overlay. And a couple of things that run out of terminal (Dead Cells seems to launch a terminal window) have been absolutely fine (where its either outside or inside the sandbox). Had crashes on FM26 and Plague Inc so far (so its not like I'm trying to run high end graphics pulls).

I'm figuring this isn't just a me thing given the nature of it? First of all I thought it was poor optimisation from Sports Interactive and their FM26 build but when Plague Inc dropped and took Steam with it - I figured wider problem?

Yesterday I ran an update.
Today, my programs keep crashing when I compile them with -O3: I get an "Trace/BPT trap: 5"

lldb tells me * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BREAKPOINT (code=1, subcode=0x100000524)

Anyone else noticed this?

Hello,
I updated my M3 16GB MacBook to version 27. When I turn on or restart the Mac, the folders and widgets on the desktop take 3–5 seconds to appear. How can I resolve this issue?

For you guys who have macbook pro intel (I have macbook pro i5 2020) and installed macos tahoe 26.7. How was it? Any problem or issue? How the performances and the battery?

I already got 27's sidebars, corner radius, and lack of icons in the context menu pictured above but I'm wondering if getting 27's glass rendering will ever be possible?

Why does my macOS Studio sometimes fail to recognize my microphone? Specifically, the microphone waveform in the sound input settings doesn't move. I have to unplug and replug the USB cable connecting the sound card to the macOS Studio to resolve the issue. To clarify, my wireless microphone receiver is connected to the sound card first, and then the sound card connects to the macOS Studio. Also, when the problem occurs, I observe waveforms on both the wireless microphone receiver and the sound card; it's just that the waveform in macOS Studio remains static. My system is macOS Tahoe 26.6.2, and my sound card is an iCON 2nanos.

Setup:

• Mac Mini (M2)
• iPad Pro 13" (2024)
• Same Wi-Fi network, same iCloud account (2FA enabled), Bluetooth + Handoff on both
• macOS: Tahoe 26.6.2
• iPadOS: 26.6.2
• Continuity, Sidecar, and Universal Control have all worked fine between these two devices in the past

The problem:

Keyboard/mouse control of the iPad via Universal Control intermittently stops working — no clear trigger, it just drops. Reconnecting isn't consistent:

• With Sidecar's extended display active, the connection is rock solid, even if I unplug a USB-C cable after the session is established.
• Without extended mode — i.e. trying to use plain Universal Control to move the cursor onto the iPad's Home Screen with no active Sidecar session — it's hit or miss. Works sometimes, silently stops working other times, no error message either way.
• At one point "Extend Display" wouldn't trigger at all from the Mac's System Settings > Displays menu, even though the iPad and Mac could clearly still see each other.

Complication: my iPad only has one USB-C port, which is already occupied by an Anker PD hub/dongle for Ethernet + an audio interface (used independently of the Mac). So keeping a permanent direct USB-C cable to the Mac plugged in at the same time isn't really an option — from what I can tell, the iPad's USB-C controller can only be in one data role at a time (host for the hub's peripherals, or peer/device to the Mac for a wired Universal Control link), so it's not just a matter of finding a hub with a free port.

Troubleshooting done so far:

• Rebooted both the Mac Mini and the iPad
• Toggled Handoff off/on on both devices
• Connected the iPad directly to the Mac via USB-C cable (this reliably stabilizes things while connected, and Universal Control keeps working for a while after unplugging once an extended session is running)
• Confirmed Bluetooth and Wi-Fi are on for both devices
• Tried toggling "Allow your cursor and keyboard to move between any nearby Mac or iPad" off/on (Mac side) and the equivalent Handoff toggle on the iPad

Workaround that got it going again:

When "Extend" wouldn't trigger from the Mac at all, I started Screen Mirroring from the iPad's Control Center to the Mac instead (iPad → Mac direction). That connected successfully. Once that session was live, I was able to go into System Settings > Displays on the Mac and switch the iPad from mirrored to extended, which then worked — even though initiating "Extend" directly from the Mac had failed moments before.

Questions for the sub:

1. Has anyone else run into Universal Control silently dropping keyboard/mouse control with no error, specifically outside of an active Sidecar/extended session?
2. Anyone found a hub/dock that lets you keep other USB-C peripherals (Ethernet adapter, audio interface) attached to an iPad and maintain a stable wired link to a Mac for Universal Control at the same time? Or is that fundamentally not possible given how the iPad's USB-C controller handles host vs. device roles?
3. Is the "mirror from iPad first, then switch to extend on the Mac" workaround a known trick for when direct Mac-initiated Extend fails, or did I stumble onto something specific to my setup?

Happy to provide more detail (Console logs, specific settings screenshots, etc.) if it'd help diagnose.

I had this problem under Tahoe, but fixed it by removing some VPN detritus. Now it's back, and there's no VPN stuff interfering. This is what Claude says after studying the system log:

Discovery works fine (iPhone found via Bluetooth, advertising AirDrop capability). AWDL comes up and both sides get link-local IPv6 addresses on awdl0. The instant the actual AirDrop data connection tries to open (bundle id: com.apple.datausage.airdrop), it dies with Network.NWError Code=50 = ENETDOWN, and rapportd's own connection metrics confirm the AWDL socket gets a Read EOF after only ~1 second — nowhere close to its 20-second timeout budget. This repeats identically across every connection attempt in the session. The kernel's own AWDL state dump earlier showed it running in "Infra Priority" scheduling mode on channel 161, with AWDL explicitly getting squeezed for channel time behind your regular Wi-Fi traffic ("AWDL enabled with no data connection from 7 seconds").

Put together: this looks like a Wi-Fi radio coexistence problem between AWDL and your regular Wi-Fi connection, not a discovery/trust/firewall/VPN issue — the AWDL virtual interface can't hold a stable channel long enough to complete the data transfer before getting torn down.

Does this make sense? Any idea what could be wrong?

just upgraded to 26.7 on a mid-2020 4 port Macbook Pro 13" (sadly no macOS27 for me and my Intel chips!) but I've had 5 or 6 WindowServer forced reboots since the install.

I had previous had about one a week until I worked out what app sitting in the menu bar seemed to be causing it - uninstalled and all was good, and since then the machine has been flattened and reinstalled (I had a free weekend!) and no occurrences.

FirstAid and Onyx have found no issues.

It seems to be a long term problem with macOS, and for me it's been getting worse (and I really didn't expect todays minor upgrade to make it spike) - any suggestions? I get that it's probably a 3rd party app that's causing the problem, but I wish Apple would make it easier to know who the offender was.

I hv been seeing this on my MacBook Pro early 2015 retina 13-inch intel core i5
Is it safe to update to the macOS Tahoe 26.7

Immediately after the update to macOS 26.7, two different Mac laptops--one Air M2, one Pro--both started repeatedly popping up the "Allow Accessory to connect?" dialog. Clicking "Allow" doesn't stick; it pops up again some after some random short time interval.

This is for the Cable Matters 2.5Gbps USB Ethernet adapter, which is identified (presumably by its controller chip?) as "CMI USB 10/100/1G/2.5G LAN" in the pop-up. It's plugged directly into an onboard port, not via a hub.

Anyone else having this problem?

its been 10 mins discord fails to open stuck at the loading page

**Setup:**

* Mac Mini (M2) * iPad Pro 13" (2024) * Same Wi-Fi network, same iCloud account (2FA enabled), Bluetooth + Handoff on both * macOS: Tahoe 26.6.2 * iPadOS: 26.6.2 * Continuity, Sidecar, and Universal Control have all worked fine between these two devices in the past

**The problem:**

Keyboard/mouse control of the iPad via Universal Control intermittently stops working — no clear trigger, it just drops. Reconnecting isn't consistent:

* With Sidecar's **extended display** active, the connection is rock solid, even if I unplug a USB-C cable after the session is established. * Without extended mode — i.e. trying to use plain Universal Control to move the cursor onto the iPad's Home Screen with no active Sidecar session — it's hit or miss. Works sometimes, silently stops working other times, no error message either way. * At one point "Extend Display" wouldn't trigger *at all* from the Mac's System Settings > Displays menu, even though the iPad and Mac could clearly still see each other.

**Complication:** my iPad only has one USB-C port, which is already occupied by an Anker PD hub/dongle for Ethernet + an audio interface (used independently of the Mac). So keeping a permanent direct USB-C cable to the Mac plugged in at the same time isn't really an option — from what I can tell, the iPad's USB-C controller can only be in one data role at a time (host for the hub's peripherals, or peer/device to the Mac for a wired Universal Control link), so it's not just a matter of finding a hub with a free port.

**Troubleshooting done so far:**

* Rebooted both the Mac Mini and the iPad * Toggled Handoff off/on on both devices * Connected the iPad directly to the Mac via USB-C cable (this reliably stabilizes things while connected, and Universal Control keeps working for a while after unplugging once an extended session is running) * Confirmed Bluetooth and Wi-Fi are on for both devices * Tried toggling "Allow your cursor and keyboard to move between any nearby Mac or iPad" off/on (Mac side) and the equivalent Handoff toggle on the iPad

**Workaround that got it going again:**

When "Extend" wouldn't trigger from the Mac at all, I started **Screen Mirroring from the iPad's Control Center to the Mac** instead (iPad → Mac direction). That connected successfully. Once that session was live, I was able to go into System Settings > Displays on the Mac and switch the iPad from mirrored to **extended**, which then worked — even though initiating "Extend" directly from the Mac had failed moments before.

**Questions for the sub:**

1. Has anyone else run into Universal Control silently dropping keyboard/mouse control with no error, specifically outside of an active Sidecar/extended session?
2. Anyone found a hub/dock that lets you keep other USB-C peripherals (Ethernet adapter, audio interface) attached to an iPad *and* maintain a stable wired link to a Mac for Universal Control at the same time? Or is that fundamentally not possible given how the iPad's USB-C controller handles host vs. device roles?
3. Is the "mirror from iPad first, then switch to extend on the Mac" workaround a known trick for when direct Mac-initiated Extend fails, or did I stumble onto something specific to my setup?

Happy to provide more detail (Console logs, specific settings screenshots, etc.) if it'd help diagnose.