Skip to main content
Known Participant
Apr 18, 2026 4:36 PM UTC
Acknowledged

P: Adobe Premiere Pro v26.2.0 (Build 65) Severe System Hang when Accessing Menus and Panels

Bug Report: Severe System Hang when Accessing Menus and Panels
App Version: Adobe Premiere Pro v26.2.0 (Build 65)

Issue Category: Performance / UI Responsiveness

Status: Recurring / Degrades over time

System Specifications
Processor: AMD Ryzen 9 5900XT 16-Core Processor (3.30 GHz)

RAM: 64.0 GB DDR4 3600 MHz

Storage: WD_BLACK SN770 NVMe SSD (Firmware: Latest/Current)

Operating System: Windows 11 Pro

OS Version: 25H2

OS Build: 26220.7872

Issue Summary
Opening any top-level menu or interacting with specific utility panels (Properties, Project Manager, Subtitles) causes Premiere Pro and the entire operating system to freeze for 5 to 7 minutes. The issue is cumulative; the application becomes increasingly sluggish the longer it stays open, eventually requiring a full restart to regain functionality.

Steps to Reproduce
Launch Premiere Pro v26.2.0 (Build 65) on Windows 11.

Perform standard editing tasks for a period of time.

Attempt to open any top-level menu (e.g., File, Edit, Clip) or the Project Manager.

Alternatively, use the Properties menu to adjust subtitle parameters, frame positioning, or zoom levels.

Expected Result
The UI should remain responsive, and menus/panels should open instantly without impacting system-wide stability.

Actual Result
The application stops responding immediately upon clicking a menu.

System-Wide Lockup: The entire OS freezes for 5–7 minutes. During this time, no other programs can be interacted with.

Performance Degradation: The "slug-like" behavior worsens over time during a single session.

Normal operation is only restored after a full application restart.

Additional Observations
Workaround Limitation: While keyboard shortcuts work initially, they do not prevent the freeze once a mouse-driven menu is accessed.

Hardware Note: Given the high-end specs (Ryzen 9 5900XT, 64GB RAM, NVMe SSD), this is clearly a software/UI conflict rather than a hardware bottleneck.

Note for Support: This issue significantly impacts professional workflows as it forces a complete system halt multiple times per hour. Please investigate potential memory leaks or UI rendering conflicts in Build 65.

    78 replies

    Joe_wpi
    Inspiring
    Nov 12, 2026 10:14 PM UTC

    I’m attempting to use 2027 and still this bug persists! it makes editing near impossible with how much it freezes. After i hit post on this comment, and return to premiere, i will have to wait 90 seconds for it to recover for its freeze. 

    Translate
    Participating Frequently
    Nov 5, 2026 10:54 AM UTC

    Still happening in 26.5.2 (Build 5) on Windows 11 26300.9818 (i9-14900KS, 64 GB, RTX 5070 Ti, Studio 621.14). I have isolated the exact code path of the accessibility-related hang - it reproduces 100%.

    When a UI Automation client reads the Premiere window, the main UI thread runs at 100% of one core for minutes inside Premiere's own WM_GETOBJECT handler ("Not Responding" + "Media Pending"). 24 of 24 identical stack samples:
      Adobe Premiere Pro.exe (deep recursion, same frame repeated) <- 100% CPU
      ... window procedure
      USER32!SendMessageTimeoutW (WM_GETOBJECT)
      OLEACC!AccessibleObjectFromWindowTimeout
      UIAutomationCore (incoming UIA request)
      USER32!PeekMessageW (main message loop)

    A/B test, same project and machine: with a UIA client attached the project open never completed (more than 2 minutes, UI thread 99-100%). With no UIA client it opened in 2-10 s and played, scrubbed, saved and reopened normally. UIAutomationCore.dll is loaded in Premiere in every hung session and absent in every good one.

    So it is not only Magnifier: any UI Automation client triggers it (Magnifier, Text Cursor Indicator, Power Automate, AI computer-use agents).

    @KatieToo @Amy the Stuv - I have a minidump captured during the hang and the full stack captures. How can I send them to engineering privately? Please also share the bug ID and whether a 26.5.x hotfix is planned. Waiting for v27 is not acceptable for paying professional users.

     

    Translate
    KatieToo
    Community Manager
    Community Manager
    Sep 30, 2026 2:35 PM UTC

    Hi all, 
    Just updating with another find from ​@take26504906kj40 regarding Accessibility related freezing with Text Cursor Indicator. 

    "Turning off Windows Settings → Accessibility → Text Cursor → Text Cursor Indicator eliminated the wait time for menu operations. Restoring the original Premiere settings continued to improve performance, and it remained smooth after updating to 26.5.1.

    During the troubleshooting, I ended IME Copilot and also uninstalled Typeless. After removing Typeless, there was partial improvement, but the stop persisted, and it was resolved once the text cursor indicator was turned off. Therefore, this is not a strictly one-factor comparison test."

    Link to the Questions post -


    Appreciate your patience as the engineering team continues investigating this!
    Katie​​​​​​​

    Translate
    Participating Frequently
    Sep 2, 2026 5:25 PM UTC

    Intel i7 mobile
    Nvidia ADA 500 mobile(yeah it sucks but what they gave me)
    64GB RAM

    I had to roll back, as well as another peer at work...BUT!!! IT is saying they are going to force an update to be “secure” even though we are saying it removes our ability to work. Adobe, for real you need to fix this.

    Translate
    MarvinHeston
    Inspiring
    Jul 30, 2026 6:22 PM UTC

    deleted, due to double posting

    Translate
    Legend
    Jul 14, 2026 3:30 PM UTC

    I found that if I turn off the Windows UI zoom feature (Windows++ and Windows+-) the problem goes away 

    Translate
    ImageshopUK
    Participant
    Aug 25, 2026 6:59 PM UTC

    x

    Translate
    Legend
    Jul 6, 2026 9:23 PM UTC

    .

    Translate
    Legend
    Jul 6, 2026 9:21 PM UTC

    I think I figured out the issue with the freezing when clicking menus!


    When I do training, I always have the Windows Magnifier feature turned on (Win + '+', or Settings > Accessibility > Magnifier).

    Once I disable that feature, Premiere stops hanging. Yay!

    Please make sure Premiere and this feature can coexist, since my work depends on both!

    Translate
    Inspiring
    Nov 12, 2026 2:08 AM UTC

    I've never had Magnifier turned on on my Windows 11 PC and it still constantly freezes and shows "Not Responding". Mainly when I try and click on the colour Picker in the Properties panel. This has been happening way before this update and it's at least been good so far since upgrading to 26.5.2 when going into Project Settings and such (though I have not tested it extensively). Previous updates really struggled to even open those settings sometimes, let alone the simple colour picker.

    Translate
    Legend
    Nov 12, 2026 7:29 AM UTC

    The magnifier is just one of the accessibility features that may cause this.  There’s also a screen reader, high-contrast themes, color filters, text & cursor scaling - and more. 

    Translate
    mkrigsman2
    Participant
    Jul 6, 2026 5:45 PM UTC

    Looks like I found solution. Detailed report attached. 

    In summary, a good place to start is simply close the Claude app. Be sure there are no Claude processes running.

    Then, run the latest version of Premiere and see if it works. 

    Translate
    Legend
    Jul 6, 2026 6:15 PM UTC

    I don’t have Claude running while I do training, so for me, that was not the culprit. I found that the Windows Zoom utility was what made it hang.

    Translate
    mkrigsman2
    Participant
    Jul 6, 2026 6:26 PM UTC

    See the report. Windows accessibility functions have the same issues. 

    Translate
    Legend
    Jul 6, 2026 2:05 PM UTC

    I think I figured out the issue with the freezing when clicking menus!


    When I do training, I always have the Windows Magnifier feature turned on (Win + '+', or Settings > Accessibility > Magnifier).

    Once I disable that feature, Premiere stops hanging. Yay!

    Please make sure Premiere and this feature can coexist, since my work depends on both!

    Translate
    mkrigsman2
    Participant
    Jul 6, 2026 5:46 PM UTC

    Yes this makes sense. See my post today with the attached report. Adobe needs to fix the bug.

    Translate