Participating Frequently

P: Properties panel freezes on any interaction — text, captions, masks, shapes, fill, shadow, border.

Forum|Forum|4 months ago
May 29, 2026
35 replies
566 views

Properties panel causes severe freezing on any interaction — 40+ second hangs, complete unresponsiveness

Premiere Pro 26.2.2 (latest stable release as of May 2026) freezes severely whenever the Properties panel is used. The issue was also reproduced on the latest Premiere Pro 26 Beta — confirming this is not version-specific within the 26.x branch. Specific examples:

Adding a simple text element and attempting to change color, border, or shadow: 40+ second freeze before any response
Editing background color or text color: application becomes completely unresponsive, requires force-close
Applying a simple mask to any element: full hang
Editing an existing caption: application freezes for 30–60 seconds or indefinitely

This is not occasional lag — every single interaction with the Properties panel triggers a freeze. The issue is consistent across all projects (new and existing), all sequence types, all source file formats (H.264, MP4, ProRes), and all timeline operations involving Properties.

System specifications:

OS: Windows 10 64-bit, build 26100
RAM: 48GB total — 36GB allocated to Premiere Pro, 12GB to other applications
Storage: Working directories and media cache relocated to SSD with ample free space — no disk errors, no bad sectors reported
GPU: NVIDIA GeForce GTX 1660 SUPER
GPU Driver: Studio Driver 610.47 (latest as of May 27, 2026), installed clean via DDU (Display Driver Uninstaller) — full wipe of previous driver before reinstall
No viruses, malware, or system integrity issues detected

Critical technical finding: Plugin logs (Film Impact) reveal Premiere is reporting

gpu": "Unknown GPU device [m/used]"

— the GPU is not being correctly identified. As a direct consequence, the CUDA renderer dropdown is completely grayed out in Project Settings (Mercury Playback Engine CUDA shows as the only option but is non-interactive). This GPU misidentification appears to be the root cause of the Properties panel rendering failures, as panel rendering relies heavily on GPU acceleration.

Note:

the cuda_supported_cards.txt
orkaround is no longer available in Premiere Pro 26 — the file does not exist in the installation directory, removing a previously viable fix for GPU recognition issues.

Troubleshooting already performed — none resolved the issue:

Full uninstall and reinstall of Premiere Pro 26, including manual deletion of all AppData, cache, and temp directories
Tested on Premiere Pro 26 Beta (latest) — issue persists identically
Updated GPU driver from 596.49 to 610.47 Studio — no improvement
Full DDU wipe and clean driver reinstall — no improvement
Disabled NVIDIA In-Game Overlay
Disabled GPU-accelerated interface rendering (Preferences > General) — marginal improvement only
Disabled hardware acceleration for video decoding (Preferences > Media)
Disabled and relocated all Film Impact plugin folders (partial improvement confirmed — plugin was the largest single contributor, but issue persists without it)
Changed sequence preview codec from Apple ProRes 422 LT to GoPro CineForm
Disabled Linear Color composition in sequence settings
Cleared media cache and relocated working directories to SSD
Tested with antivirus (Norton) disabled
Tested with tablet drivers (Huion) disabled
Tested on a fresh Windows user profile

Adobe support response to date: downgrade to Premiere Pro 25.

The system is clean, the hardware is capable, and the issue is fully reproducible on both the latest stable and latest beta versions of Premiere Pro 26. This appears to be a bug in how Premiere Pro 26 identifies and interfaces with the GPU for Properties panel rendering, rather than a hardware or environment issue.
😮
HEEEEELLLPPPPP

Show previous replies

masato_2172

Participant

It looks a problem for the version.

I downgraded the version into 26.0 and everything moves smooth as before.

PulseBriefs

Participating Frequently

@masato_2172 Yes, the text rendering engine delay is tied directly to the same unified memory allocation bug in v26.2/26.3. The NLE loses the hardware pointer for the font cache during direct UI inputs. Temporary fix while we wait for Adobe's patch: create a blank Adjustment Layer over your text block, or downgrade to the v26.0 point-release. We are logging the hardware profiles for this bug over at thepulsebriefs . com if you want to drop your Mac configuration metrics.

igorcaiedoamaral

Participating Frequently

I have the same here! It happens also on text and search panel. Suddenly both stopped work.

masato_2172

Participant

Do you have delay for typing texts also? I have the same problem now!!

PulseBriefs

Participating Frequently

@Amy the Stuv
I am tracking this identical Properties panel freeze on an M1 Mac running macOS 15. The UI locks up completely for 30+ seconds when interacting with text borders and masks. I am pulling a native macOS Activity Monitor 'Sample Process' dump during the next hang to send over to the team. Temporary workaround for anyone stuck: bypassing GPU acceleration to Software Only or running a non-destructive Binary Search on text layers restores stability.
Tracking full logs over at thepulsebriefs . com.

KatieToo

Community Manager

@PulseBriefs quick question! I’m curious if you happen to have any kind of bluetooth headphones while experiencing this lag on your Mac? Another user reported about this issue, and they were able to clear it. Anything external or bluetooth mouse or something like this could be worth double checking on.

Thanks!
Katie

Amy the Stuv

Community Manager

Hello @DRD_POA

Welcome back. I’ve been digging into this issue and the team said it could be helpful to get a “dump” during the hang.

If you are able to, could you please send me the file produced with the following steps on Windows. On Macs this would be called a Sample and if anyone following this post is having a similar issue on Mac, I can tell you the steps to provide that log.

On Windows

Open Task Manager go to the Processes tab, and identify the Premiere process (you can use search to filter for only Premiere)
In Premiere, get it into the hanging/unresponsive state
Switch back to Task Manager and right click on Premiere then choose > Create dump file
When it's finished, it tells you where it saves the .DMP file.
It'll be large, but it ZIPs down smaller. So right click on the file and choose Compress to..ZIP file.
Have them send us that ZIP file. We can provide a OneDrive upload link if they need to (it still might be >1 GB)

This would be most helpful. We would love to try and solve this problem.

Hoping to help,

Amy Stuvland

R

Rashid_Gooseberry8830

Participant

i have done what you said.
Link : https://drive.google.com/file/d/1f1DYE81RBANT4TILjb1noe3DAXYjILC6/view?usp=sharing

Amy the Stuv

Community Manager

Thank you. I just requested access from my personal gmail. I’ll also DM you an upload link for these files.

cgchang

Participant

Same issue. Rolled back to 26.0.1 and seemed ok.

KatieToo

Community Manager

Hi @0xxz1yz

Welcome to the Premiere Pro forums! We are glad to see you here. Thanks for including all that great information from the bug report details, that’s very helpful. Noting that you are seeing this happening even with a new project, no footage inside.

What kind of disk space we working with where your Premiere is, and I’m curious if you have any other external hard drives plugged in while this happens?

Do you have GPU accelerated UI rendering (restart required) checkmarked under Edit > Preferences > General?

Under the same Edit > Preferences > Memory, how much is given to Premiere / other applications out of curiosity?

Have you been able to check your Task Manager during the crash to see what’s happening with Premiere using CPU/Memory? To do this, press CTRL+SHIFT+ESC at the same time. The Task Manager will pop up. Click the Performance tab and screenshot or relay what of 100% it’s using if possible.

Just thinking also if this would improve anything as well with you being on Windows, in Premiere go to Edit → Preferences → Media → Disable H.264/HEVC hardware accelerated decoding (encoding can stay on).

Let me know what happens with that if you see any improvements. Hope we can help soon!

Thanks for reaching out,
Katie

0xxz1yz

Participant

Issue

Premiere Pro completely freezes and hangs ("Not Responding") whenever any panel (Timeline, Project, Effect Controls, etc.) is clicked. This issue occurs on all versions higher than 26.0.1.

Steps to Reproduce

Install any Premiere Pro version newer than v26.0.1.

Open Premiere Pro and open or create any project.

Click on any interface panel or workspace tab.

Expected Result

The panel should focus immediately, and the interface should remain responsive and operational.

Actual Result

The application immediately freezes, displays the Windows "Program Not Responding" dialog, and hangs. If the window is left alone and repeatedly clicked after a while, it temporarily recovers responsiveness, but clicking on a different panel triggers the exact same freezing loop.

Premiere Version

All versions superior to v26.0.1 (Currently forced to downgrade to 26.0.1 to maintain stability).

Operating System

Windows 11 (Fully updated, clean OS reinstall performed).

GPU Driver (Windows only)

NVIDIA Studio Driver version 610.47 (Released May 26, 2026).

Helpful Context

Does it affect all projects or only some? It affects all projects, regardless of the complexity or assets.

Does it affect new, empty projects? Yes, the issue persists even in completely new, blank projects.

When did the problem first begin? The issue started immediately after updating to any release building upon version 26.0.1.

Additional Troubleshooting Attempted: A full factory reset/clean installation of the Windows OS was performed, and all system drivers are up to date. Downgrading strictly to version 26.0.1 is the only workaround that prevents the freezing, which is unacceptable for a paid active subscription.

PulseBriefs

Participating Frequently

Our lab is cataloguing this exact Mercury Engine GPU acceleration drop. We've archived the non-destructive overrides and setup sheets on our main technical index at: thepulsebriefs . com
(Copy and remove spaces to access). @birdonawi @DRD_POA

PulseBriefs

Participating Frequently

This looks like a classic DirectCompute layer timeout between Premiere 2026's Mercury Playback Engine and your GPU VRAM, especially when the interface tries to render complex vector paths like text, shadows, and masks simultaneously.

If anyone else is stuck in this freeze loop, you can test it safely using a non-destructive "Binary Search" routine:

1. Duplicate your sequence to preserve a clean master rollback state.
2. On the duplicate sequence, clear all text/mask layers on the second half of the project (from the 50% mark to the end).
3. Attempt to interact with the Properties panel on the remaining first half.

- If it works flawlessly: The freeze is being triggered by a corrupt font cache or broken asset on the second half.
- If it still freezes: The hardware-acceleration handshake is broken at the driver level.

I wrote an extensive log detailing this specific hardware conflict. Since I can't post active links here as a new member, you can find the full "Logic Path Matrix" by pasting this into your browser (remove the spaces):

medium . com / @contact_50572 / how-to-fix-premiere-pro-error-compiling-movie-and-render-crashes-cc33a7566e66

Hope this helps isolate the freeze!

birdonawi

Participant

I have the exact same problem. I´m guessing it´s a bug of some sort. I need this fixed asapa. It´s really slowing me down

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.