Premiere Pro 26.5: Home blocks all interaction for ~5 seconds on every launch (M5 / macOS 26.6.2)

Issue

On a MacBook Pro M5 running macOS 26.6.2, Premiere Pro 26.5 displays its Home screen after the splash screen, but all application interaction remains unavailable for approximately five seconds. Recent-project links, buttons and menus cannot be used during this interval. The interface becomes interactive around the time the Adobe account avatar appears in the upper-right corner.

This happens on every launch into Home. Configuring Premiere to open the last project directly bypasses the issue completely. The five seconds describes the unresponsive interval after Home becomes visible, not total launch time.

Environment

• MacBook Pro, Apple M5.
• macOS 26.6.2 (25G83), also confirmed in the supplied process sample.
• Adobe Premiere Pro 26.5, updated September 10, 2026. Exact application build not recorded.
• ARM64 architecture, confirmed in the process sample.
• Creative Cloud Desktop installed; exact version not recorded.
• Clean installation reported; also reproduces in a newly created macOS user account.
• No media or sequence is required: occurs before opening a project and with an empty recent-project list.

Steps to reproduce

1. Configure Premiere to launch to Home rather than open the last project.
2. Quit Premiere completely.
3. Launch Premiere normally.
4. Wait for the splash screen to disappear and the Home/recent-project screen to become visible.
5. Immediately attempt to click a recent project (if present), a Home button, or an application menu.
6. Observe that interaction is unavailable for approximately five seconds, then becomes available without restarting.
7. Quit and repeat: this occurs on every launch into Home on this machine.

Control comparison: configure launch to open the last project directly, quit and relaunch. The reported delay disappears completely. Restore launch-to-Home to reproduce it again.

Expected result

Once Home is displayed, project-opening controls and application menus should accept input. Loading account imagery or other Home content should not prevent basic interaction.

Actual result and impact

Home is visible but all interaction is blocked for approximately five seconds. Responsiveness returns around the time the account avatar appears. This creates a repeatable delay on every normal launch. No crash is reported with this symptom. Opening the last project directly is an effective workaround.

Troubleshooting already performed

• New macOS user: exactly the same issue reproduces.
• Clean installation: issue persists. Exact procedure was not recorded; use of Creative Cloud Cleaner Tool is not claimed.
• Disable plugins: same behavior. Earlier process listings still contained CEP extensions, so complete removal of all system-wide extensions is not independently established.
• Change DNS: no improvement.
• Network/offline comparison: without Internet, there is a longer delay before the recent-project list appears, but the list is interactive once visible. This differs from the online post-display delay.
• Creative Cloud sign-out, Mac shutdown/restart, sign-in: no improvement.
• Keychain: keychain list and Adobe-related entries examined; no specific corrupt credential or causal fault established. A fresh macOS user also reproduces.
• Media cache: same issue with cache cleared/empty.
• Recent projects: same issue with an empty list.
• External disks: same behavior connected or disconnected.
• Diagnostics: startup samples, system log stream, filesystem/network fs_usage traces and Adobe process listings collected and analyzed. No definitive causal stack or timeout isolated.
• Open last project directly: completely bypasses the delay.

DNS, network, Keychain, plugins, caches, recent projects and disks were investigated and summarized as ruled out during troubleshooting. More precisely, the tests did not yield a fix or establish them as the cause; they do not categorically exclude all Adobe service dependencies, system-wide extensions or security-framework interactions.

History and scope

This has persisted for several months and across multiple updates on this M5 Mac. It was not observed on my previous M1 Mac, but that is a historical comparison, not a controlled test with matching software versions. The issue predates 26.5 and should not be assumed to be a new regression specifically introduced by that release.

Diagnostic evidence and interpretation

The collected premiere_startup_30s.txt records an ARM64 process launched at 11:28:50.071 on September 10, 2026, with sampling beginning at 11:28:50.183 on macOS 26.6.2 (25G83). Its application version field is ???, so it does not independently establish the Premiere build.

The sample includes FE::HomeScreenSupport, UXPClientHostAPI::LaunchNewDocDialog and CachedIMSTokenAuthProcessor::POST. A collected system log contains repeated Apple Security runtime diagnostics around 11:33:32: “This method should not be called on the main thread as it may lead to UI unresponsiveness.” These are investigation leads, not proof of which operation caused the interval.

The startup sample aggregates startup and subsequent activity, including normal event-loop waits and new-project dialog activity. It is not precisely aligned to the visibly unresponsive interval; aggregate call counts should not be interpreted as measurements of the freeze. Earlier filesystem/network trace analysis did not isolate a single multi-second blocking operation.

The strongest evidence is the difference between launch-to-Home and opening the last project directly, plus reproduction in a fresh macOS user. A Home initialization or readiness dependency is a hypothesis. The responsible component—Home, UXP/CCX, authentication/licensing, a shared service or another startup dependency—remains unconfirmed. CEP extension processes alone do not establish Home's implementation technology.

Request to Adobe engineering

Please reproduce online launch-to-Home on this configuration and compare it with direct project launch and the offline behavior above. Please investigate whether Home initialization or an account/profile readiness event gates application input. A trace aligned to Home becoming visible and then interactive would help distinguish main-thread blocking from controls disabled while waiting for asynchronous initialization.

Please specify the preferred diagnostic capture if the existing samples are insufficient. Collected materials include premiere_startup_30s.txt, premiere_startup_sample.txt, Sample of Adobe Premiere.txt, and system-log, fs_usage and process-list output. Raw diagnostics are not attached to this public post; they may contain local paths and account-related metadata.

Information not yet established

• Exact Premiere build and Creative Cloud Desktop version.
• A screen recording with visible timing.
• A controlled Premiere 25.x comparison or Safe Mode result.
• A confirmed result for the suggested CCX Welcome folder rename.
• Full system-wide CEP-extension removal; a fresh macOS user alone does not remove shared extensions.