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

[joes47599238]

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

[JustinWoo]

@Focuspulling

Oh totally. This is Adobe's fault - no question. I'm just explaining how pernicious and persistent this problem is. The only way I was able to get past it was by literally buying a new PC. That's BONKERS. That's LUDICROUS. That's the kind of thing that makes people migrate to Da Vinci.

[jermainesky]

I have been experiencing the problem many times a day, really frustrating. Something two things that I have found that have worked for me:

1) Run the app as an administrator. Right click the desktop shortcut then "Run as administrator" this greatly reduces the problem but doesnt actually eliminate it. I am able to work this way.

Note: When I run as administrator, I cannot seem to drag and drop from explorer to premiere pro, i have to import footage from within premiere pro

2) Reduce premiere pro from full screen to a window. This seems to work well for me, haven't had a crash since.

Note: When I select this method, I cannot view full screen preview on the second monitor.

If anyone can try this and verify if it works on their side?

[TheSqueakerArmy]

Same exact issue, and I agree that it isn't solved.

[Kens10]

I have experienced this problem with Premiere Pro 2018 and now 2019. Did anyone figure out a legit fix?

[_earthtojens]

I am also having this issue. Running latest version via cloud update. Turning off Mercury GPU acceleration does solve my problem but severely impacts performance. This is a major issue as I am having to toggle the Project Settings > General > Video Rendering and Playback > Renderer every time I export my files!

Premiere 13.0.1 (Build 13)

Windows 10 Version 1803 , OS build 17134.1

[JustinWoo]

If you're on Windows, uninstall OneDrive and set it on fire. Premiere runs 10x more stable without it in my system.

[_earthtojens]

I appreciate the tip and yes I would love to set it on fire but I need it to transfer files in and out of my companies enterprise cloud. Also Premieres stability should not be dependent on external software like OneDrive. I would hope Adobe could work with Microsoft to remediate any stability issues with OneDrive if they do exist.

[JustinWoo]

You'd hope, but you'd be wrong. This is a 2 year old problem and neither software company is taking responsibility, so users are left holding the bag.

[R3C0N54]

This just started to happen to me at work but not at home. Two things that are different from both that allow it to work.

My PC at home uses Nvidia card but none of the drivers are installed and it works.

But at work, my PC got the issue. However, I grabbing the latest Driver for Nvidia (Version 417.01 at the time) and the issue was resolved.

Hopefully this helps a bit with those who have this issue. I don't run AMD, so unfortunately I do not have answers for that.

[_earthtojens]

Thanks for the suggestion. Updating video drivers didn't not fix my issue unfortunately.

Geforce GTX 1080

417.01

was 397.31

[JustinWoo]

Did you try doing a clean install of the drivers? If you DL the drivers from the NVIDIA site, and run the executable (rather than trusting the GeForce Experience to do it for you), and then select the custom install option, it lets you do a clean install, which seems more reliable in my experience.

[_yuwara]

i resolved this issue by changing my renderer to "software only" and then back to "GPU acceleration/CUDA" and then also restarting Premiere

[_earthtojens]

Thanks for the tip @ _yuwara. Unfortunately this did not work for me and now Premiere is also crashing when my project is set to 'Mercury Playback Engine Software Only'. My export directory is essentially stuck in the 'C:\Users\Public\Documents\Adobe\Premiere Pro\13.0\Tutorial\Going Home project' folder.

[_earthtojens]

Updating to the latest version of Premiere Pro CC has fixed my problem. I no longer crash when changing the output name in the export settings. Thank you to all who attempted to help me with this issue.

Premiere Pro CC Version 13.0.02 (Build 38)

[Tim_Tyler]

It happens to me too. I actually EXPECT it to happen so often that I save my project before clicking the link to rename the file.

Windows 10 / GTX1070 / SSD's

If I restart Premiere the problem goes away, but then returns after a while of using Premiere.

[tarvot23397778]

yeah i do the same

yet it still manages to surprise me sometimes...

[nicklear]

Just to add another me too - this bug has plagued me over the last year. I am still on v12 as I am on a big project and I don't trust upgrading it. I hope v13 fixes this for others. I certainly don't want to have to have software only render on. I don't want to stop using OneDrive.

[johnlunceford]

Same issue.

[daily doseo49630288]

I have same problem

[wcn_dave]

I also have the same problem, caused me to quite often lose work.  Very annoying.  All it's doing is browsing the file system!!

[FocusPulling.com]

  wrote

I also have the same problem, caused me to quite often lose work.  Very annoying.  All it's doing is browsing the file system!!

It's incredible that Adobe has totally ignored this issue for many years.

[wcn_dave]

And it's still happening....

[Rich_S_UK]

I have exactly the same problem, and downgrading to software rendering isn't acceptable.  Come on Adobe.  This needs sorting.

[Kevin-Monahan]

Rich,

Try checking permissions for the folder where you are trying to save. Make sure they are set to Read/Write. Did that help? Need help with that? Let us know.

Thanks,
Kevin

[FocusPulling.com]

That has absolutely nothing to do with it, Adobe Employee (but sure, I just checked).

Instead of sending questions back to us, perhaps finally do something?