Properties panel freezes on any interaction — text, captions, masks, shapes, fill, shadow, border.
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
AdChoices