Skip to main content
Known Participant
April 18, 2026

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

  • April 18, 2026
  • 74 replies
  • 905 views

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.

    74 replies

    Participant
    August 19, 2026

    I am running 26.3.2 (Build 2) on Windows 11 and have the same problem. Whenever I press on any names in the menu panel (file, edit, clip, sequence, etc), the Premiere completely freezes the whole system including other running software for about 15-30 seconds!

    Participant
    August 19, 2026

    I am running 26.3.2 (Build 2) on Windows 11 and have the same problem. Whenever I press on any names in the menu panel (file, edit, clip, sequence, etc), the Premiere completely freezes the whole system including other running software for about 15-30 seconds!

    And I do not have Windows Magnifier enabled.
     

    System specs:

    • OS: Windows 11 Pro, build 26200.9168
    • Motherboard: Supermicro X11DAi-N, Intel C621 chipset, BIOS 4.7
    • CPU: 2× Intel Xeon Gold 5218 @ 2.30 GHz — 32 cores / 64 threads total
    • RAM: 128 GB DDR4 ECC Registered, 2400 MT/s
    • GPU: NVIDIA GeForce RTX 5080 16 GB
    • Storage: NVMe SSD + multiple SATA SSDs
    • Display: AOC Q3279WG5B, 31.5"
    MarvinHeston
    Inspiring
    July 30, 2026

    deleted, due to double posting

    MarvinHeston
    Inspiring
    July 30, 2026

    I’m running PP 26.3 and I have this problem.  I can edit find, import files, create proxies, work with a sequence, but as soon as I touch a Top Menu, the app freezes for 2 minutes.  

    In my case Windows Magnifier has never been enabled or active.

     

    Computer specs

    OS Name    Microsoft Windows 11 Pro
    Version    10.0.26200 Build 26200
    Other OS Description     Not Available
    OS Manufacturer    Microsoft Corporation
    System Name    PS-2025
    System Manufacturer    ASUS
    System Model    System Product Name
    System Type    x64-based PC
    System SKU    SKU
    Processor    Intel(R) Core(TM) Ultra 9 285K, 3700 Mhz, 24 Core(s), 24 Logical Processor(s)
    BIOS Version/Date    American Megatrends Inc. 2006, 7/18/2025
    SMBIOS Version    3.8
    Embedded Controller Version    255.255
    BIOS Mode    UEFI
    BaseBoard Manufacturer    ASUSTeK COMPUTER INC.
    BaseBoard Product    ProArt Z890-CREATOR WIFI
    BaseBoard Version    Rev 1.xx
    Platform Role    Desktop
    Secure Boot State    On
    PCR7 Configuration    Elevation Required to View
    Windows Directory    C:\WINDOWS
    System Directory    C:\WINDOWS\system32
    Boot Device    \Device\HarddiskVolume1
    Locale    United States
    Hardware Abstraction Layer    Version = "10.0.26100.1"
    User Name    PS-2025\Marv
    Time Zone    Pacific Daylight Time
    Installed Physical Memory (RAM)    128 GB
    Total Physical Memory    127 GB
    Available Physical Memory    107 GB
    Total Virtual Memory    137 GB
    Available Virtual Memory    114 GB
    Page File Space    10.0 GB
    Page File    C:\pagefile.sys
    Kernel DMA Protection    On
    Virtualization-based security    Not enabled
    App Control for Business policy    Enforced
    App Control for Business user mode policy    Off
    Automatic Device Encryption Support    Elevation Required to View
    Hyper-V - VM Monitor Mode Extensions    Yes
    Hyper-V - Second Level Address Translation Extensions    Yes
    Hyper-V - Virtualization Enabled in Firmware    Yes
    Hyper-V - Data Execution Protection    Yes
     

    Here is a video of it happening along with Task Manager - 

     

     

    Camilo gonzalez
    Participating Frequently
    July 30, 2026

    The only solution is to revert to version 26.0.2

    MarvinHeston
    Inspiring
    July 30, 2026

    I’ll give that a try.  
    you might phrase this “The only work-around”… cause sadly that’s not a solution.
    Thank you for your time and comment.

    Marv

     

    Legend
    July 14, 2026

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

    Legend
    July 6, 2026

    .

    Legend
    July 6, 2026

    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!

    mkrigsman2
    Participant
    July 6, 2026

    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. 

    Legend
    July 6, 2026

    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.

    mkrigsman2
    Participant
    July 6, 2026

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

    Legend
    July 6, 2026

    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!

    mkrigsman2
    Participant
    July 6, 2026

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

    mkrigsman2
    Participant
    July 1, 2026

    Solution is downgrade to 26.02.

    Participating Frequently
    June 25, 2026

    The latest Windows update seems to have resolved the issue; I’ve been working all day without any UI lag in 26.3.0 , and everything is smooth and stable.

    Windows June 23, 2026—KB5095093

    FocusPulling.com
    Known Participant
    August 17, 2026

    This is simply not true.