Known issues in the April 2018 release of Premiere Pro CC (12.1.x)

A list of known issues in the April 2018 release of Premiere Pro CC (version 12.1.x)


  • After you update to the April 2018 release of Premiere Pro (version 12.1.x) on Mac OS, the application crashes on launch without any error message. For information on resolving this issue, see Application crashes during launch on mac OS.
  • Premiere Pro can crash if you switch between workspaces too quickly.
  • Custom scratch disk settings persist even if you reset the settings to same as project causing Premiere Pro to crash while rendering.
  • Premiere 12.1.x crashes on Windows with the error message: The application was unable to start correctly (0xc0000005). For more information, see Application crashes on launch with the error "The application was unable to start correctly (0xc0000005)".
  • If you use the Save As option to save the file and choose to replace your existing project file with the same name, Premiere Pro closes the project file and shows a blank workspace. Some users end up force quitting Premiere Pro thinking it has crashed. On opening the project again, all sequences are closed from the Timeline panel and users assume that their work is lost on seeing an empty Timeline panel.
    To continue where you left off, open the sequence by double-clicking the name of the sequence from the Project panel. To avoid the entire situation, increment the project name (for example: "project name_001"), save the project file with a different file name, or save it to a different location.


  • Premiere Pro sequences with closed captions show offline media in AME when native rendering is turned off. This error occurs when DLs from Premiere Pro are imported into Adobe Media Encoder, and you have enabled Burn Captions Into Video. When you try to encode, the caption is not burned.  In addition, if you set caption to "none", then the video image is blank. To work around this issue, in Adobe Media Encoder, enable Import sequences natively.
  • There is no audio playback in a project. To work around this issue, solo and unsolo a track to get the audio playing, then save the project and close Premiere Pro. Open Premiere Pro once more to be clear of the issue.
  • Green and purple streaks appear on the clips while editing a Premiere Pro video. This issue occurs if the device drivers on your system are not compatible. For more information, see Green or purple streaks appear in the Source and Program monitors.
  • Imported H264 AV file imports as audio only file on specific machines.
  • Files from some Nikon cameras are imported into Premiere Pro with wrong frame rates.
  • QuickTime files do not import correctly and show up as offline on updated projects. This issue is because QuickTime 7 era formats and codecs are no longer supported. For more information, see Dropped support for QuickTime 7 era formats and codecs.


  • Reveal in Project does not work if Bins are in Thumbnail view.
  • In the Project window, if you add properties using the Metadata Display dialog box (when List view is selected in the Project window), properties are not saved when you close the Bin and save the changes. To retain custom properties, open the bin in place, make changes to the metadata, then save the project.
  • If the Project panel is in Icon mode and bins are closed, clicking Reveal in project on a clip in a sequence causes Premiere Pro to crash.
  • The Search box in the Project panel sometimes becomes disabled.


Some Type 1 PostScript fonts don't appear in the Font menu.


Use any of the following workarounds to resolve this issue:

  • Convert the font to an OpenType or TrueType font using a font conversion utility.
  • Search Typekit for the same or similar font, and then install that.
  • Create the text in Photoshop or Illustrator, and import the PSD or AI layer into Premiere Pro.

Aanmelden bij je account