Skip to main content
Participating Frequently
December 10, 2022
Question

Adobe Premiere Pro 2023 (Version 23.1) hangs while loading files

  • December 10, 2022
  • 18 replies
  • 3150 views

The latest version of Premiere Pro 2023 (23.1) is stalling while loading saved Premiere files. The indicator shows 'loading file' to about 75% and then stalls. I had to downgrade to the previous version (23.0) which seemingly works fine. I have tried to fix it by clearing the Adobe media cache and even uninstalling plugins. With no results.  I just hope Adobe will address this issue asap. Otherwise, all future updates will become useless. Meanwhile, I have disabled automatic updates, which seems to be the only workable solution at the moment.

This topic has been closed for replies.

18 replies

horeseru
Participant
April 18, 2023

It worked on the latest version (23.3) and the latest NVIDIA Studio Driver! Thank you so much @Kevin-Monahan !

Kevin-Monahan
Community Manager
Community Manager
March 29, 2023

Hi horeseru,

Have you tried v.23.2 yet? You can also update to the latest studio drivers. The latest ones are pretty stable from what I hear.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
horeseru
Participant
March 29, 2023

Hi @Kevin-Monahan 

I've tried clean installing NVIDIA driver 517.40 but I'm still stuck on 75% when opening projects that were saved with Premiere Pro 23.1 or 23.0. It was fine when opening Premiere Pro v 22. projects.

I tried downgrading my projects and opening them in Premiere Pro v 22.6.4 but they were still stuck at 75%.

Please help, there are important works in my project files.

 

Thank you.

Participating Frequently
January 4, 2023

Hi FocusPulling

The status has not changed. My advice; keep ignoring the "Premiere Pro Update is available" as long as it is version 23.1. I am hoping that Adobe will address the issue in a later update. Until then I am running Version 23.0.

FocusPulling.com
Known Participant
January 3, 2023

What is the status of this gigantic, affects-nearly-everyone, cripples-Premiere bug?  I am not updating to the "latest" version despite the nags from the Creative Cloud app, until Adobe finally acknowledges and addresses this (instead of blaming Nvidia even though their latest drivers worked with the immediately preceding Premiere version).

Kevin-Monahan
Community Manager
Community Manager
December 15, 2022

You can reinstall it from the Creative Cloud application.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Trebor21
Participant
December 11, 2022

I installed Nvidia driver 517.48 and i still can't open my project in Premiere. How to roll back the defect Premiere version to the last stable one?

 

thx

Participating Frequently
December 11, 2022

Hi Kevin,

thanks for your reply.

Yes, my NVIDIA driver version is 522.30

To your suggestion to downgrade my NVIDIA driver makes little sense though. This driver works perfectly in Adobe Premiere Pro (32.0). Downgrading it because of a problem in version 32.1 would be counterproductive. Instead of going backward, moving forward, Adobe should fix the issue asap as the error is apparently found in the Adobe upgrade. 

Kevin-Monahan
Community Manager
Community Manager
December 10, 2022

Thank you for the added details. I upvoted the bug report.

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
FocusPulling.com
Known Participant
December 10, 2022

The triggering action that caused Premiere to melt down, was entirely Adobe's fault.  This is an easy logical deduction because of the fact that all prior and current Nvidia drivers work perfectly fine with the very recent 2023 update of Premiere.  When Adobe compiled the 23.1 update, it was Adobe itself who committed this failure that didn't exist in 23.0, regardless of current/prior GPU drivers installed.

 

Instead of taking ten seconds or so to boot up Premiere on an Nvidia system to see if it works, Adobe just sorta went "meh" as usual and published the broken update.