Skip to main content
Chris1905
Participant
Oct 27, 2026 11:13 AM UTC
Acknowledged

Regression in 26.5 / 26.5.1 / 26.5.2: stuck Media pending, repeated frame-substitution errors and AppHangB1 with OBS MKV; 26.3.2 was stable

Our existing editing workflow was usable in Premiere 26.3.2. We tried upgrading to 26.5, 26.5.1 and 26.5.2, and encountered the same class of problems with each. Previous rollbacks restored usability according to our experience. The current detailed evidence was collected on 26.5.2 Build 5 (executable version 26.5.2.5).

The Program Monitor repeatedly freezes on the yellow multilingual "Media pending" screen. In one occurrence, the same image remained visible even after switching to an empty sequence. Premiere also reports repeated frame-retrieval and frame-substitution recursion errors for multiple OBS MKV recordings, involving both our CAM and RawCapture files.

The application repeatedly becomes unresponsive ("Keine Rückmeldung" / Not Responding). Some hangs recover temporarily; others led to closing and reopening Premiere. Restarting can restore the picture briefly, but the errors and hangs return. This has also happened after leaving Premiere open and idle, without editing.

We initially also reported a failure when starting Premiere without a project. The latest startup test stayed stable, while errors and unusable performance persisted in the project workflow. We therefore do not claim a consistently reproduced no-project startup crash.

Version comparison
- 26.3.2: last version known to work in our workflow, based on user experience.
- 26.5: problems after upgrading.
- 26.5.1: problems persisted.
- 26.5.2 Build 5: detailed current case, screenshots and three Windows AppHangB1 reports.
- Rollback: 26.3.2 Build 2 / executable 26.3.2.2 is now installed again. A fresh sustained editing test after this rollback has not yet been confirmed.
- A separate 25.6.6 installation exists but is NOT the baseline version for this report.

Steps in the affected production workflow
1. Launch Premiere 26.5.2 Build 5 on the system described below.
2. Open a copy of the affected project with its original OBS MKV recordings linked.
3. Play the sequence, switch sequences and allow background media/audio processing to run.
4. Also leave the project open without interacting for a while.
5. Observe the Program Monitor, Events panel and UI responsiveness.

Actual result
Repeated frame errors, a stuck Program Monitor and recurring application hangs make productive editing impossible. A restart only provides temporary relief.

Expected result
The same project/media workflow should remain responsive and reliable as it was in 26.3.2. Background analysis should not leave playback or the UI persistently blocked.

This is a real-project reproduction description, not yet a deterministic minimal one-clip reproduction. Time to failure was not measured consistently.

Error examples
Normalized from the German screenshots:
- Error retrieving frame 60240 at 0:16:44:00 in CAM-2026-10-14 19-30-40.mkv; substituting frame 60239.
- Error retrieving frame 76939 at 0:21:22:19 in RawCapture/2026-10-14 19-30-43.mkv; substituting frame 76938.
- Frame-substitution recursion attempt aborted after multiple attempts for the specified file.
- Other captured errors refer to a black replacement frame.
- The Program Monitor remains on "Media pending / Ausstehende Medien".

Affected filenames include:
CAM-2026-10-14 19-30-40.mkv
CAM-2026-10-14 20-00-49.mkv
CAM-2026-10-14 20-52-09.mkv
RawCapture/2026-10-14 19-30-43.mkv
RawCapture/2026-10-14 20-00-46.mkv

Background processing
Intelligent Media Analysis was visible at 0%, with audio preparation and automatic audio tagging also present. The timing suggests a possible interaction to investigate, but causation has not been established. We did not complete a verified analysis-disabled comparison run.

Troubleshooting already attempted
- Completely cleared media cache: no lasting improvement.
- Updated graphics driver: no lasting improvement.
- Closed/reopened the project and restarted Premiere repeatedly: temporary recovery only.
- Disabled H.264/HEVC hardware-accelerated decoding and restarted Premiere: the preview initially returned, then hangs recurred. This was not a fix.
- Latest startup test following a suggested reset procedure: startup stayed stable; errors and poor responsiveness continued in the project workflow. Individual reset checkboxes and third-party-plugin-disabled state were not separately recorded, so this should not be treated as a fully documented plug-in-isolation test.

Personal settings, workspaces, effect presets and three keyboard profiles were backed up before the suggested reset.

Not yet tested: lossless MKV-to-MP4 remuxing, transcoding, a new project with only one clip, controlled audio-device isolation, full plug-in A/B testing or hang-dump analysis.

System
- Intel Core i9-9900KF @ 3.60 GHz.
- NVIDIA GeForce RTX 4070 Ti SUPER, 16376 MiB reported by nvidia-smi.
- NVIDIA driver 617.42 at collection time; driver branch not verified.
- 32 GB RAM according to the existing hardware configuration.
- Windows build 26300.9711; registry DisplayVersion 26H2. Windows marketing name/edition not separately verified.
- Samsung Odyssey Neo G9 display and Elgato Wave XLR audio interface.
- Media on local F: drive; current media cache on C:.
- Approximately 158.5 GB free on C: and 481.0 GB on F: during collection.

Media and OBS recording details
The five checked MKV headers contain H.264/AVC and AAC codec identifiers. These headers were inspected; no complete bitstream validation or variable-frame-rate analysis was performed.

We found original OBS 32.2.2 recording logs from 14 October that explicitly name the affected RawCapture files. They document:
- NVIDIA NVENC H.264, High profile.
- 2560x1440 and 60/1 fps in the OBS video configuration.
- NV12, Rec.709 Full.
- VBR 50000 kbps target / 70000 kbps maximum.
- Keyframe interval 120, preset p5, tuning hq, multipass qres.
- 3 B-frames, lookahead off, adaptive quantization on.
- Three stereo AAC tracks at 320 kbps each.

These RawCapture settings should not be assumed to apply identically to every separate CAM recording.

Windows evidence
Three original WER reports identify:
EventType: AppHangB1
Application: Adobe Premiere Pro.exe
Executable version: 26.5.2.5
Hang Type: 134217728
Hang signatures: 7f6d, 737d, c7c2
WER directory modification times on 27 October 2026: 10:06:07, 11:08:03 and 11:09:16 local time.
Windows description: "Stopped responding and was closed".

These reports establish hangs, but do not identify a faulting module or provide an analysed thread stack. We are not claiming a proven hardware failure or a specific decoder/GPU defect.

Request to Adobe
Please investigate the regression between 26.3.2 and the 26.5 series, including MKV/H.264/AAC handling, multi-audio-track recordings, repeated frame substitution, background analysis and playback interaction. Please confirm whether this exact case is known and provide a verified workaround or fix.

Please also specify the preferred method for capturing a useful hang dump and a private upload route for an original failing recording.

Evidence package
Available privately: detailed German report, two project snapshots, three original WER reports, ten UXP logs from the Premiere logs directory, two OBS recording logs, media/system/version inventories and SHA-256 checksums.

Screenshots are documented in an index with transcribed evidence. Original PNG files could not be copied into this ZIP and need to be attached separately to the Adobe report. Original source media total about 44.4 GB and are also not included. The projects therefore require relinking to the original media to reproduce the issue.

We are reporting a suspected regression based on repeated version-dependent behavior. We have not established the exact underlying component. Our immediate workaround is returning to 26.3.2 to resume production.
 

      3 replies

      KatieToo
      Community Manager
      KatieTooCommunity Manager
      Community Manager
      Oct 27, 2026 8:01 PM UTC

      ​@Chris1905 Thank you for sending those files and for all the detailed information about these issues. I wanted to let you know we were able to recreate them on our side. For example, in Premiere v26.5.2 we ran into that hang, of which, I noticed it was stuck on Preparing Audio around 50% or so, under Progress panel. The clip in question that time was your 40.mkv. Also ran across the frame substitutions coming up on several clips as well. These same clips/project do work well in v26.2.2 as you noted.

      Temporary workaround: Continue working in v26.2.2 -or- you can try transcoding your clips to say Apple ProRes 422, though I understand transcoding would add more time and space needed but wanted to offer that.

      We’ll be filing a report about all this with your thorough details and logs, thank you again for including all of that. We’ll return to this post to update with a fix once that becomes available, or if any further needs or questions come up.

      Appreciate all your time and efforts reporting on these issues, and for helping others!
      Katie

      Translate
      KatieToo
      Community Manager
      KatieTooCommunity Manager
      Community Manager
      Oct 27, 2026 3:06 PM UTC

      Hi ​@Chris1905 

      Thanks for your two detailed posts including your specs and Premiere versions. It looks like you have a few issues happening including media pending, hang/freezing, and frame substitution errors. In order to better troubleshoot, could we please request a few sample media files to test in the included project? Perhaps from the list you mentioned being affected: 


      Affected filenames include:
      CAM-2026-10-14 19-30-40.mkv
      CAM-2026-10-14 20-00-49.mkv
      CAM-2026-10-14 20-52-09.mkv
      RawCapture/2026-10-14 19-30-43.mkv
      RawCapture/2026-10-14 20-00-46.mkv

       

      We can DM you our private upload link for that. That way we can maybe relink those and use the project you sent, or at least run a quick controlled test with those.

      As for Premiere hang/freezes, we might like to request a Dump file from you for engineers to look over. You can also include the results of that on the same private link we’ll send for the media files. Out of curiosity, when you say closing Premiere, are you force quitting Premiere or having any actual crashes? If you are having any crashes, in the crash report box, please put an email address in, so our engineers can look up that report.
       

      Mini-Dump file:

      •  Process Explorer (from Microsoft) is required for a Mini-Dump.
        •  This website  provides the steps with screenshots.
        • Zip the file before sending.


      Full Dump file:

      1. Open Task Manager go to the Processes tab, and identify the Premiere process (you can use search to filter for only Premiere)
      2. Launch Premiere, work until it reaches that same delayed hang or unresponsive state
      3. Switch back to Task Manager and right click on Premiere then choose > Create dump file
      4. When it's finished, it tells you where it saves the .DMP file.
      5. It'll be large, but it ZIPs down smaller. So right click on the file and choose Compress to .ZIP file.


      Let’s start there, and we hope to help!
      Katie 

      Translate
      Chris1905Author
      Participant
      Oct 27, 2026 12:36 PM UTC

      Update — 27 October 2026: important version correction and further troubleshooting

      I need to correct the baseline in my original post and its title: I misremembered the last stable version. It was 26.2.2, NOT 26.3.2. I have now returned to 26.2.2, and Premiere is working again.

      Corrected results on this Windows system:
      • 26.2.2: last stable version; working again after the latest rollback.
      • 26.3.2: also affected; returning to this version did not resolve the problem.
      • 26.5, 26.5.1 and 26.5.2: also affected by the reported hangs/crashes and unusable editing performance.

      Every version newer than 26.2.2 that I have actually tested has failed in this workflow. This does not mean that I tested every intervening release. The earlier references to 26.3.2 as stable, including the original workaround and attached rollback snapshot, are superseded by this update.

      Latest observation: after returning to 26.2.2, I opened my template project and everything is working normally and very quickly again. In the affected newer versions, Intelligent Media Analysis remained stuck at 0%, with Premiere failing either immediately or later. This makes a version-dependent problem involving media analysis/background processing my main current suspicion. However, disabling analysis did not reliably recover the affected versions, and this is not yet a controlled proof of causation.

      Further tests since the original report:

      1. Clean reinstall and Windows restart. I backed up my keyboard shortcuts and custom workspaces, uninstalled Premiere, cleaned/isolated the remaining Premiere profile and cache data on C: and generated preview/analysis data on F:, restarted Windows and reinstalled. This did not resolve the issue. No manual Adobe registry purge was performed.

      2. Confirmed testing with automatic Intelligent Media Analysis disabled. Automatic transcription was also disabled. The problem persisted. Re-enabling analysis during one test was followed by another failure; disabling it again and reopening did not restore stability. This is an observation, not proof that analysis or its cache is the cause.

      3. After reinstalling, importing a single original OBS MKV produced audio but a black video image. Premiere recognized the clip as 2560 × 1440 at 60 fps, with video present on a visible timeline track. This was a test with the MKV, not a completed MKV-versus-MP4 comparison.

      4. A new, separate media-cache location and a completely new project without my production template did not solve the problem. Importantly, I also experienced a failure with the new project still EMPTY, before importing any media. The issue therefore cannot be explained solely by the original project or a particular MKV file.

      5. I renamed the active user-profile folder to force profile recreation and tested again, without intentionally restoring my custom shortcuts/workspaces for that test. Failures continued. However, legacy shortcut/layout files were found again in the recreated profile, apparently migrated from an older installation. This was therefore not a fully verified migration-free/default-profile test.

      6. RAM usage was around 50% during an observed failure, without an excessive upward trend. Available system memory and commit headroom were also checked. We have not established RAM exhaustion or the large memory growth described in the separate Mac memory-leak report. An internal memory-management problem is not ruled out.

      The earlier cache deletion, graphics-driver update, repeated restarts and hardware-decoding-disabled test also provided no lasting fix. The original AppHangB1 records remain evidence for 26.5.2; they are not newly collected crash dumps for every version listed above. Some incidents recover after “Not Responding,” so I am distinguishing hangs from confirmed process termination.

      Current workaround: remain on 26.2.2 to resume production. The newer tested versions are a production show-stopper on this system. The root cause is still unconfirmed. Please investigate changes after 26.2.2, particularly Intelligent Media Analysis remaining at 0% and its interaction with project opening/background processing, as well as the failures with an empty project. The case should not be limited to MKV decoding or the 26.5 series alone.

      A controlled remux/transcode comparison, complete audio-device and plug-in isolation, and analysed hang dumps have not yet been completed.

      Translate
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices