A REAL FIX to - PremierePro Freeze-Crash upon "SaveAs", "importing", "minimizing" etc...

A REAL FIX to - PremierePro Crashes upon "SaveAs", "importing", "minimizing" etc...

Okay, so I may have a REAL answer from tech support to why Premiere Pro crashes for some, but not others.

So, I'm on customer support with my usual complaints that it's crashing indiscriminately upon "Saving as", "importing" and/or when I minimize premiere.

So, Adobe customer support says (and I paraphrase here) that Premiere uses the most CPU & ram resources and thus has a grater chance to generate occasional corruptions including in the program "Preferences".  So the fix is to re-name (or delete) your preferences, when crashing seems to be a problem. The only caveat is that if you have specific UI (User Inter-phase) preferences, like I do, you loose those as well and have to re-make all those preferences.

Any way here's how to delete the preferences file to hopefully fix many crashes.

1. go to...  File Explorer /  Documents / Adobe.

2. re-name (or delete) the folder called "Premiere Pro".

Warning: This will delete all of your preferred Premiere Pro UI Desktop preferences as well as you audio preferences. The next step will explain the audio warning that might open up, upon your next opening of Premiere.

3. Open up a Premiere Pro project.

     - a "MIME Device Internal Error" might open up with options to correct the error.

4. Choose "Yes" to open up your 'Audio Hardware Preferences'

5. Choose your preferred input. (mine is 'No Input')

6. Choose your preferred output. (mine is 'Speakers - Realtek High Definition Audio)

7. Click on "OK"

8. This will bring waveform back into your audio tracks.

9. Now finally, if you have any custom  Premiere UI workspace settings and custom keystrokes, you'll have to remake all of those as well.

I know this isn't fun to do and can take some time to re-address over again, but it's the only viable work-a-round that we have at this point.

Adobe really need to fix the memory leaks or whatever it is that causes corruption(s) within the program. Maybe automate this process somehow with uncorrected preferences memory to re-establish with a single keystroke, or even better yet, automate this whole damned thing in the background, like Final Cut Pro (joke).