Premiere CC 2015 - "No Valid audio output channels for playback found. Please check the audio hardware preferences."

[Kunz]

I just updated from CC 2014v2 to 2015.

When I open any project or create a new one and import any type of media - I get a yellow warning window at the bottom of screen stating "No valid audio output channels for playback found. Please check the audio hardware preferences." When pressing Play, no sound plays and the playhead does not move.

Here are my audio hardware preferences - Realtek is my only option. Everything was fine in CC 2014 this afternoon and I have CS6 installed, which opens and plays clips and audio with no problems while listing Realtek as the output device.

HP Z820 - Windows 7 64-bit - 128GB ram. Adobe apps and system all up to date.

[joomclub]

I have the same problem since I upgraded to latest Premiere Pro.

Why there is no support from Adobe , but they are very happily charging the credit card every time.

Now I know the reason, why people laugh at me, when I say, I bought adobe CC.

They said, dont waste money!

[Kevin-Monahan]

Why there is no support from Adobe , but they are very happily charging the credit card every time.

Now I know the reason, why people laugh at me, when I say, I bought adobe CC.

They said, dont waste money!

If you have a complaint, please file a bug report. Adobe engineering will not hear you until you do that.

Thanks,
Kevin

[Kunz]

I have gone to the HP Z820 support site and updated all of my audio drivers, as well as others.  Still the same issue in Premiere CC 2015. I can not do my work and it is becoming a problem.

If I open CS6, everything is as it should be and no audio issues. Here is a shot of my Audio Preferences from Premiere CS6.  Can anyone from Adobe chime in with some advice?

[Kunz · Accepted solution]

I was able to resolve this issue by removing all of Plug-ins from the "C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore" directory, which fixed the problem, then replacing them in batches until the error returned.  In this case, it was an outdated version of a Bluefish444 addon.