HELP!! MME device internal error...

Report · May 23, 2018

...suddenly popping after system update last night. I have checked settings, everything appears normal, but showing 'not working' for no apparent reason. Everything has been re-set, re-booted, etc, so now what for a "non techy" gal!!!??? Any very specific guidance will be greatly appreciated!! Alas, no phone support for Audition...REALLY?? Wow! Thanks guys/gals!! 05/24/18

Kelli

Report · May 23, 2018

I honestly don't know if there's going to be a simple answer to this. Yesterday's 'upgrade' was something of a disaster for a lot of people - including me. I don't know quite what they did, but it appeared to screw up a lot of things that were working fine previously, and it took me about five hours (and an OS reload...) to get it all back working again.

First thing though - does the sound on your system work at all, for anything? Or is it just Audition that's failing to connect to it? Device internal errors often point at drivers that need updating...

Report · May 23, 2018

Oh wow, so it's not just me!!? So unfortunate! Yes, I have sound everywhere except Audition & was just able to finally get it to record, but only in ASIO mode. Now, I can't get it to edit, so simply no MME function at all...I had to uninstall my Lexicon/Lambda/re-install, etc & all of the other re-fresh, re-boot's that go along with it. Now, I'm stuck with no editing capability damn it! I wasn't having any issues until I allowed the update. I'm not sure of what other drivers I would need to update quite honestly. This is where I get very lost!! I appreciate it!!

Report · May 23, 2018

At least it's working somewhere - that's not so bad. There are a couple of other options you can try, though. Firstly, see if WASAPI is available as a drive class - that might well work. The other option is to download (free) ASIO4ALL and try using that as a driver - that has often been known to solve all sorts of problems, and also gives good diagnostics.

ASIO4ALL - Universal ASIO Driver For WDM Audio

Report · May 23, 2018

eehh, well, I've now lost all sound so back to zero. Ugh. I have downloaded the program, now to get it to do what it needs to do! I'll do another re-boot & see if that helps!! Frustration builds. Why do these guys think these updates are helpful...at all? lol, trying not to lose my mind

Report · May 23, 2018

The air was somewhat blue around here last night, too!

Report · May 23, 2018

Could you tell us please what update this was that caused all this wailing and gnashing of teeth so that we can try and avoid it?

If you have decent external audio interfaces then surely using the manufacturers ASIO should be the answer since these should bypass all OS audio driver problems? Unless of course something was changed in USB port support.

Report · May 23, 2018

All I can tell you is that it was the latest Microsoft 10 update forced down our throats within the last 24 hours. Everything worked fine & I woke up to disaster. I was able to record, but now I'm back to no sound at all anywhere on the computer. MME error just won't clear. I've downloaded the suggested ASIO 4 All program & ran it, so I'm about to go in & see if that helped. Other than that, I'm out of options.

Report · May 24, 2018

ryclark wrote
Could you tell us please what update this was that caused all this wailing and gnashing of teeth so that we can try and avoid it?

Knowing the build number doesn't help - and I can't tell you what the actual failed build number was because it's now not the current version. Microsoft never tell you anything useful about their updates anyway. The version I've got on this laptop now is 10.0.17134 but that's later than the one that screwed up. What happened was that the update failed to recognise the existing desktop layout files at all, and for a while this resulted in nothing visible on the screen, except some error messages which didn't provide much of a clue, quite frankly. After a lot of provocation using Task Manager I got it to the point where I could repair the OS from a downloaded version. You have to do this with Windows running, though, otherwise everything gets wiped if you use it from a cold start.

I think that the most annoying thing about M$ updates is that before they start, they appear to destroy all of your restore points...

Fortunately this isn't the DAW that's suffered - I won't let them update that until I know that whatever they're trying to do at least works fine on this laptop. From the investigating I've done, it would appear that quite a lot of people have had an identical experience with this 'upgrade'...

Report · May 24, 2018

OK. Thank goodness this was only a Windows 10 update. I still run my DAW on Win 7. However my laptop which runs Win 10 has failed all updates in the last few months, so isn't yet even on 1709 Creators Fall edition or whatever it was called.

Report · Jun 07, 2025

Same here. Many of my settrings in Adobe programs do not work, and Audition has slowed to a crawl. Mail has begun to show blank pages when the header is clicked. I am completely updated, and often try Adobe's "Beta" programs, but have found they conflict with the original, so I stopped. I don't know if theser are Adobe or Apple problems, but I suspect Apple has been hacked (half joking).

Report · Jun 09, 2025

@unauthorizedrob

The most recent post to this thread, prior to yours, was from 2020 and was a problem created by a Win 10 update.

It would seem from your post that you run a Mac so I think your post is, regrettably, irrelevant to this thread, sorry! Perhpas you need to create a new thread, with details of your system and of the problems you are experiencing?

Report

Where does it say this a Windows only thread?

Report

In the title, where it refers to an MME (Microsoft Multimedia Environment) error.

Report · May 24, 2018

Try turning off audio input in premiere. Worked for me.

Report · May 24, 2018

Oh really? Good for you!!! I have tried powering off everything & just did a restore that wasn't successful. It says it couldn't access a file probably bc of my anti virus software & to disable it & try again. This is just a crazy waste of time, not to mention money. My tech skills have been stretched, & the stress doesn't help .

Report · Jun 08, 2018

That worked for me too,,,, yesterday. Created a new project this morning, and no sound again. So went to preferences > Audio Hardware, and selected 'none' for input, and it didn't work at all. Beyond Frustrating and makes me wonder why on earth I pay Adobe all this money for CC.

Please, SOMEONE, a fix for this issue!

Report · Jun 08, 2018

Unfortunately if you are reliant on built in soundcards then you are always at the mercy of OS updates and the provided audio drivers. This is nothing to do with Audition. It is all down to Microsoft and the audio drivers it supplies in it's Windows updates. Unless you have a decent external USB audio interface with it's own ASIO drivers, which bypass the OS completely, then you may end up with problems when things change.

Report · Jun 11, 2018

First-time post!

The Windows update changed some microphone settings with certain apps. You have to turn the app access back on for your Adobe CC apps - here's the fix...

To enable app access to microphone In Windows 10, do the following...

Open the Settings app.
Go to Privacy - Microphone on the left menu
On the right, enable the toggle switch under "Allows apps to access your microphone". ...
In the apps list below, you can control microphone access for certain apps individually.

Report · Jun 15, 2018

THANK YOU SO MUCH, this worked for me

Report · Jul 04, 2018

This worked for me as well!! Thanks!!! Was going to hurl the computer through my office window!!!

Report · Jul 20, 2018

markn95269639 wrote
This worked for me as well!! Thanks!!! Was going to hurl the computer through my office window!!!

Why not throw it through Microsoft's Office Windows instead.

Report · Jul 20, 2018

Yep that fixed it. Thanks

Report · Sep 21, 2018

Thank you for the reminder about the changes to privacy and security. I first ran across this a couple months back with my USB camera and Skype. The error message is basically useless, since it doesn't indicate a security issue, just that there was an "internal error." Interstingly, the same issue is not happening on my W10 laptop, just my workstation.

So, thanks again. Once I "allowed" access to the mic, I can once again record...

Report · Jun 07, 2018

Hi.

I had the same problem. This solution from Adobe worked for me.

In Preferences > Audio Hardware > Change the default Input to "No Input" > Click OK & test.

Hope it helps you, too.

HELP!! MME device internal error...

1 Correct answer