Latest KB5127690 and KB5127648 updates disabled GPU in Adobe Premiere 23

Question

Latest KB5127690 and KB5127648 updates disabled GPU in Adobe Premiere 23

Riversedge64 0

As in topic, before last update everything worked well. I installed KB5127690 and KB5127648 and Adobe Premiere 23 updated GPU settings for itself after finding some changes in system and stopped to use GPU even if it is selected (no changes in settings were made). Only software encoding works. I updated nvidia drivers, made clean installation. Nothing helps. I tried to uninstall KB5127648 but windows still keeps this update after uninstall. Any ideas?

0 comments

7 answers

Your answer

Answer 1

TaoLi 116.8K Independent Advisor

Thanks, I found an Adobe case with almost the exact same RTX 40-series issue.

https://community.adobe.com/questions-729/cant-export-in-hardware-encoding-1557056

Disclaimer: This link points to a non-Microsoft website. While the content appears to be accurate and safe, the site may contain third-party advertisements. Please take care to distinguish between advertisements and the actual download links to avoid accidentally clicking on content that might promote PUPs/PUAs (Potentially Unwanted Programs/Applications). Before downloading or installing any file, it is recommended to verify its source and filename.

Please check Control Panel >> Programs and Features and uninstall any WebM plugin/application. If you don’t see WebM, search for fnord instead, then restart Premiere.

Adobe confirmed this plugin can block NVENC hardware encoding even when CUDA is working normally.

Riversedge64 0 Reputation points

2026-10-15T16:41:50.23+00:00

Of course I checked it before. No WebM and fnord programs installed. I didn't installed anything except last win11 updates.

Answer 2

TaoLi 116.8K Independent Advisor

Thanks. Build 26300.9457 means KB5127648 is no longer installed.

Since you have an RTX 4070 Super, install the latest NVIDIA Studio Driver, then check:

Premiere >> File >> Project Settings >> General >> Renderer >> Mercury Playback Engine GPU Acceleration (CUDA)

If CUDA is missing or greyed out, try rolling Premiere back one version.

Riversedge64 0 Reputation points

2026-10-15T14:32:52.1366667+00:00

Latest Studio Driver as clean instalation performed. CUDA is active in Premiere settings, but Premiere ignores usage of GPU while exporting or doesn't allow to use it (depends on settings) claiming that "your system's hardware does not support hardware acceleration for the current settings". I remember that after win11 update Premiere displayed a window about GPU settings update (it was performed automatically after system changes). It is shocking because it worked before win11 update.

Answer 3

TaoLi 116.8K Independent Advisor

Thanks for the update.

Please press Win + R >> winver and send the Windows build number. The update history can still show “Successfully installed” even after removal.

Also try Settings >> System >> Display >> Graphics >> Premiere Pro >> Options >> High performance (NVIDIA), then restart Premiere.

If it still ignores the GPU, please also send the exact NVIDIA GPU model.

Riversedge64 0 Reputation points

2026-10-15T13:58:38.52+00:00

W11 26H2 (I upgraded from 25 in hope that it helps but nothing changed). compilation no 26300.9457. I have 4070 Super Nvidia card.

Answer 4

Riversedge64 0

Hello! Thanks for the answer, unfortunately none of your solutions helped. Even after uninstalling latest quality update, both updates keeps on the list of updates history as succesfully installed". Premiere keeps ignoring possibility of usage the GPU.

0 comments

Answer 5

TaoLi 116.8K Independent Advisor

Hi, since reinstalling the NVIDIA driver didn’t help, try resetting Premiere’s preferences:

Close Premiere >> hold Alt while opening it >> Reset app preferences >> Continue. Back up your custom settings first.

If the update still won’t uninstall, try Shift + Restart >> Troubleshoot >> Advanced options >> Uninstall Updates >> Uninstall latest quality update. Have your BitLocker recovery key ready, and treat removing the security update as a temporary test.

0 comments