Premiere Pro CC crashes when I try to change the file name before export

[#1]

Hello,

This issue recently started happening - Premiere Pro CC crashes when I try to change the file name before an export. Premiere runs smoothly at every part of the edit until I come to exporting a file either directly or through media encoder. I can get as far as changing all export settings but as soon as I click the filename to change it, I get an error message (attached).

Never had this before, not installed anything new on my system, running windows 10, decent specs etc.

All adobe software is up to date also.

Any ideas on this? This is my first posting so sorry if I have missed anything off that will help you guys!

Cheers in advance,

Joe

[#2]

Hello,

This issue recently started happening - Premiere Pro CC crashes when I try to change the file name before an export. Premiere runs smoothly at every part of the edit until I come to exporting a file either directly or through media encoder. I can get as far as changing all export settings but as soon as I click the filename to change it, I get an error message (attached).

Never had this before, not installed anything new on my system, running windows 10, decent specs etc.

All adobe software is up to date also.

Any ideas on this? This is my first posting so sorry if I have missed anything off that will help you guys!

Cheers in advance,

Joe

[#3]

Hi Joes,

Never seen this kind of issue.

Do you have enough room in the target location?

Did you try exporting to a different location?

Please test this in a new project and let me know if that makes any difference.

Thanks,

Kulpreet Singh

[#4]

Hi Kulpreet,

Thanks for replying to me. There is enough room in the target location and I have changed the location a couple of times to check this. I have also tested this in a new project and I am still having the same issues!

Anymore suggestions,

Thanks,

Joe

[#5]

Please close all the Adobe applications.

Go to the following locations:

• C:\Users\<Username>\Documents\Adobe
• C:\Users\<Username>\AppData\Roaming\Adobe

In all the locations, rename the 'Adobe' folder to 'OldAdobe'

Launch Premiere, accept the License Agreement and see if it works.

Note: You will lose your customized workspaces and keyboard shortcuts.

You might need to kill some Adobe processes from the Task manager.

Thanks,

Kulpreet Singh

[#6]

Thanks Kulpreet,

I will try these and get back to you - thanks again for your help!

Joe

[#7]

Did you ever get a resolution to this? I have the exact same problem.

CC 2015

[#8]

Hey Neils,

I have the exact same problem.

Sorry to hear that, did you try all of the above mentioned steps?

Please click on the "I have the same question" tab at the top.

Thanks,

Kulpreet Singh

[#9 · Accepted solution]

Hi,

Thanks for your quick response.

I just found a suggestion that worked. Changing the render settings to "Mercury Engine Playback Software Only" solves the problem. I'm not sure of the impact this will have, but I'm not making many big projects, so that's okay.

I also don't know the cause - maybe I don't have the correct graphics drivers or something, but for now, this fixes my issue

Neil

[#10]

https://forums.adobe.com/people/kulpreet+singh  wrote

Hey Neils,

I have the exact same problem.

Sorry to hear that, did you try all of the above mentioned steps?

Please click on the "I have the same question" tab at the top.

Thanks,

Kulpreet Singh

This thread should not have been marked as "answered."  Not even close.  That Adobe has a severe bug crashing Premiere upon simply initiating the prompt to enter a new filename/location, is not resolved by the suggestion to severely downgrade the Premiere application's functionality, to software-only rendering.  That has nothing to do with Adobe's bug (obviously).  And yes, I've cleared my preferences, which did nothing to solve this ongoing problem.

Just because you don't see it in frequently in these forums, doesn't mean the problem isn't a huge nuisance.  We have to force-close Premiere and start over, but sometimes it causes loss of the most recent version since auto-save.

This problem ​needs to be fixed.

[#11]

I am having the same issue as reported.  Some days I am able to work on exports with no issues. Other days I have to change the filename and/or location inside of Media Encoder instead of in the export dialog box.  Please give us a fix!

[#12]

Not a fix by any means, but a workaround, if you need to get stuff done and since they amazingly haven't fixed this yet as of 2020- 

I just let it save under whatever filename it wants and wherever. I pay attention to what name and where it saved it, then I just go to that folder and rename it and move the file where I want. Stupid, but it beats wasting hours dealing with this foolishness. Get it fixed already! The "Mercury Engine Playback Software Only" fix is bogus, it takes away all your hardware acceleration! Suddenly a 20 minute render is 7 hours! Ridiculous!

[#13]

This how I have been "solving" it as well.

[#14]

I'm having this same problem as well. This problem seems to come and go. The last time I had the issue was a few months ago, and I cleared off some HD space and it went away. No such luck this time around. This problem is really persistent.

I'm on Windows 10 (latest version as of 1/20/18), i7 laptop, 16 GB RAM, GTX 880M (latest drivers). This happens on multiple different projects, multiple sequences, etc. No idea how to make this very frustrating problem go away.

[#15]

I've just started having the same issues. Very bizzare. Any update? Its a huge problem as i export multiple edits for clients to sign off on and obviously need to change file names etc...

[#16]

Adding my voice here, same problem. Doesn't always happen but still consistently about once a day. After a program crash and end task, it typically works fine until the next computer restart. After that it could go either way.

Followed the same troubleshooting steps, not working, and disabling Mercury for rendering is not an option for me.

CC 12.1.1, tons of hard drive space, on multiple drives, fully updated drivers etc. i7 4930k, 32 GB RAM, GTX 1080. Bug report submiiiiittedddd.

[#17]

Same issue here. Win10.

[#18]

same issue here