Some Windows users are reporting that they see the ‘ MME Internal Device ‘ error in Premiere Rush and Adobe Premiere PRO and no audio output is available when editing a video. This problem is mainly reported to occur on Windows 10.

[Fix] MME Internal Device Error in Premiere - 1

MME Device Internal Error

When troubleshooting for this particular issue, you should start by seeing if your operating system is not capable of fixing the problem automatically. Do this by running the Recording Audio Troubleshooter and applying the recommended fix.

If this doesn’t work and you don’t really require microphone input when editing your videos in Adobe Premiere PRO or Adobe Premiere Rush, you can fix the problem swiftly by accessing the Audio Hardware settings and changing the Default Input to None. But doing this will restrict Adobe from tuning in to the audio your connected microphone picks up.

Another possibility that might end up causing the ‘ MME Internal Device ‘ error is a restriction imposed by Windows 10. It’s possible that microphone access is turned off for the device where you’re using Adobe Premiere on. In this case, you should be able to fix the issue by navigating to the Privacy tab of the Settings app and allowing Microphone access for this device .

However, if you’re encountering the problem on Windows 10, you can also expect to see this problem due to an Audio Capture bug that was introduced along with the Creator’s update and affects UB audio capture on various video editing apps. In this case, you can either install the hotfix released by Microsoft via Windows Update or you can install the 3rd party WDM Audio driver ASIO4ALL.

If everything else fails, you need to seriously consider that you are actually facing some kind of system file corruption that is effecting the recording infrastructure of your OS. In this case, you can either perform a clean install or a repair install in order to refresh every relevant OS component that might be responsible for this problem.

Method 1: Running the Recording Audio Troubleshooter (Windows 10 Only)

In the event that you’re experiencing microphone issues with other applications than Adobe Premiere Pro, it’s very likely that you’re dealing with a generic inconsistency that your Windows 10 OS might be capable of resolving automatically.

You can expect to see the ‘ MME Internal Device ‘ error due to an incorrect recording configuration – In this case, running the Recording Audio troubleshooter might fix the issue for you (if the problem you’re encountering is already covered by a repair strategy).

This utility was build to scan your computer for common audio recording problems and automatically applied verified fixes if a compatible scenario is found. Several users that were previously dealing with the ‘ MME Internal Device ‘ error have confirmed that this method worked for them.

If you’re encountering this issue on Windows 10, follow the instructions below to run the Recording Audio troubleshooter and apply the recommended fix:

  1. Press Windows key + R to open up a Run dialog box. Next, type “ms-settings:troubleshoot” inside the text box and press Enter to open up the Troubleshooting tab of the Settings app. Accessing the Troubleshooting tab
  2. Once you’re inside the Troubleshooting tab, move over to the right-hand menu and click on the Recording Audio entry. Next, click on Run the troubleshooter from the newly appeared context menu to launch the troubleshooter. Running the Recording Audio troubleshooter
  3. When you’re prompted by the UAC (User Account Control) , click Yes to grant admin access to this troubleshooting utility.
  4. Wait patiently until the initial analysis is complete, then take a look at the results. If the utility ends up recommending a fix, apply it swiftly by clicking on Apply this fix . Apply this fix Note: Keep in mind that depending on the fix that gets recommended, you might need to follow an additional set of instructions in order to apply the fix.
  5. After the recommended fix is successfully deployed, reboot your computer and see if you are able to edit videos in Adobe premiere without encountering the ‘ MME Internal Device ‘ error.

In the event that the same problem is persisting, move down to the next potential fix below.

Method 2: Set Default Input to None

If you don’t really care about microphone input, then there’s a really simple fix that will allow you to work around the ‘ MME Internal Device ‘ error – You can simply go into your Adobe Premiere settings and change Input from Audio Hardware to None.

This small but important modification will ensure that Premiere is no longer listening from microphone sounds, so the error message will stop appearing even in situations where Windows is preventing the Premiere app (and other 3rd party apps) from using the built-in microphone.

This is more of a workaround rather than a fix, but a lot of affected users have confirmed that this operation was successful in allowing Premiere Pro and Premiere Rush users to top encountering the ‘ MME Internal Device ‘ error.

If you want to give this workaround a try, follow the instructions below:

  1. Open your Premiere application and use the ribbon at the top to select Edit, then navigate to Preferences > Audio Hardware .
  2. Once you’re inside the Audio Hardware menu, move over to the right-hand side menu, and expand the drop-down menu associated with Default Input . Modifying the Default Input Menu
  3. From the Default Input drop-down menu, select None, then save the changes by clicking on Ok .
  4. Restart your Adobe Premiere application and see if the issue is now resolved.

In case you really need Microphone input and you can’t really afford to disable it from the Audio Hardware menu, move down to the next potential fix below.

Method 3: Allowing Microphone access (Windows 10 Only)

If you’re encountering this problem on Windows 10, and a trip to Preferences > Audio Hardware (in Adobe Premiere) is pointing out that your audio devices aren’t working properly, you’re likely seeing the ‘ MME Internal Device ‘ error because the microphone access for this device is turned Off.

Several affected users that encountered a similar issue have confirmed that they managed to fix the issue by accessing the privacy settings on Windows 10 and modifying the default behavior for the active microphone so that it’s able to access the device it’s on.

If the scenario described looks like it could be applicable to your current situation, follow the instructions below to allow Microphone access and resolve the ‘ MME Internal Device ‘ Error on Windows 10:

  1. Open up a Run dialog box and press Windows key + R . Next, type ‘ ‘ms-settings:privacy-microphone” and press Enter to open up the Microphone Privacy window for the Windows Settings app. Running the ‘ms-settingsprivacy-microphone’ in Run command
  2. Once you’re inside the Settings app, move over to the right-hand section and click the Change button associated with Allow access to the microphone on this device.
  3. Next, from the newly appeared context menu, enable the toggle so that the Microphone has access to this device. Enabling Microphone access to this device
  4. After you manage to do this modification, close the Settings menu, restart Adobe Premiere and see if the problem has been fixed.

In case you still end up seeing the ‘ MME Internal Device ‘ error, move down to the next potential fix below.

Method 4: Resolving the Audio Capture bug on Windows 10

If you’re encountering the issue on Windows 10 that’s not updated to the latest build and none of the potential fixes above have worked for you, it’s very likely that you’re dealing with a bug with the Creators Update on Windows 10.

This is a well-known problem that affects USB audio capture with various video editing apps including Adobe Premiere Pro and Adobe Premiere Rush.

If this scenario is applicable, you have two ways forward:

Option A – Installing every pending update along with the fix that resolves this inconsistency (Microsoft has already patched this problem via a hotfix that gets installed via Windows Update)

Option B – Installing the ASIO4ALL Universal ASIO Driver for WDM Audio in order to circumvent the generic Audi driver bug.

Regardless of your preferred way of fixing the problem , we have created two separate guides that will walk you through both Option A and Option B.

If you want to fix the ‘ MME Internal Device ‘ error by installing every pending Windows Update, follow Option A (Recommended. On the other hand, if you have no desire to update and install the Microsoft provided hotfix, follow Option B.

Option A: Installing the hotfix via Windows Update

  1. Open up a Run dialog box by pressing Windows key + R. Next, inside the text box, type ” ms-settings:windowsupdate’ and press Enter to open up the Windows Update tab of the Settings app. Opening the Windows Update screen
  2. Once you’re inside the Windows Update screen, move down to the left-hand section and click on Check for Updates button. Check for Updates
  3. Next, wait for the initial scan to complete. If the scan reveals that there are pending Windows Updates that are waiting to be installed, follow the on-screen instructions to Download & Install the pending updates. Note: In the event that you have a lot of pending updates that are waiting to be installed, you might be prompted to restart your computer before you get the chance to install them all. If this happens, restart as instructed, but make sure to return to the same screen once the next startup is complete.
  4. Once you made sure that every pending update is installed, reboot your machine one final time and see if the ‘ MME Internal Device ‘ error has been fixed by trying to edit a video in Adobe Premiere PRO or Adobe Premiere Rush.

Option B: Installing ASIO4All WDM Audio Driver

  1. Visit this link ( here ) and download the latest version of the Asio4all driver by downloading the latest version associated with your language. Downloading the latest version of ASIO4All
  2. Once the download is complete, open the installer executable, and click Yes at the User Account Control prompt to grant administrative access.
  3. Next, follow the installation prompts to complete the installation of the ASIO4All driver. Installing the ASIO4ALL driver
  4. After the operation is complete, perform a system restart and see if the issue is now resolved.

In case the same problem is still persisting, move down to the final fix below.

Method 5: Performing an in-place repair

In the event that none of the potential fixes above have allowed you to fix the issue, it’s very likely that the ‘ MME Internal Device ‘ error is somehow being facilitated by some type of system file corruption that’s affecting your OS files.

If this scenario is applicable, the only way to fix the issue is to perform a procedure that ends up refreshing every Windows component and ensures that there’s no corrupted data that might end up causing this problem.

Of course, the most popular option is a clean install , but this is not the most efficient solution. Sure, it will refresh every OS component, but unless you backup your data in advance, you can expect total data loss on your OS drive. This includes personal media, installed applications, games, and user preferences.

If you want the most efficient approach, go for a repair install (in-place reinstall) – While this operation will require you to insert a compatible installation media, the main advantage is that the procedure will only reinstall system files (Windows components), without touching your applications, games and user preferences.

How to Fix “Printer is in an error state” Issue?

The error “ WinRAR Error: Next Volume Is Required ” usually appears when you’re extracting a multi-part RAR archive and WinRAR can’t find (or can’t correctly identify) the next file in the sequence . This often happens when a volume is missing , stored in a different folder , or renamed in a way that breaks the archive’s expected order .

[Fix] MME Internal Device Error in Premiere - 2

In this guide, we’ll go over the most reliable fixes confirmed by affected users, along with what each method is doing behind the scenes so you can choose the right one for your situation.

Important: To extract multi-volume archives, you should always start extraction from the first file in the set. This is usually file.part1.rar , or (in older sets) the main .rar file that comes before .r01 , .r02 , and so on.

1. Download and Place the Missing RAR File

WinRAR needs all parts of a multi-volume archive to complete extraction. This error usually appears when one of the volumes in a set like .part2.rar , .r01 , .r02 , .001 , and similar naming formats is missing . Downloading the missing volume and placing it in the same folder as the other parts allows WinRAR to continue extracting normally .

  1. Look at the error message or review the list of archive parts in the folder.
  2. Identify which volume is missing (for example, part2.rar , .r02 , .001 , etc.).
  3. Go back to the website or source where you downloaded the archive.
  4. Locate and download the exact missing file using the same naming format as the others.
  5. Make sure the new file name matches the pattern of the rest. Example: If you have file.part1.rar and file.part3.rar , the missing one must be file.part2.rar .
  6. Move the downloaded missing volume into the same folder as the other archive parts.
  7. Confirm that all parts are in a single folder before extracting.
  8. Right-click the first file in the series (usually part1 or the main .rar file) and select Extract Here or Extract to Folder .
  9. WinRAR should now detect all volumes and continue extraction normally .

2. Manually Browse & Select the Next Volume

Use this method only if the next volume already exists , but WinRAR is failing to detect it automatically. This can happen due to incorrect naming , the file being in a different location , or a temporary file access issue. Manually browsing helps WinRAR locate the correct volume and resume extraction without interruption .

  1. Right-click the first file in the series (usually .rar or part1.rar ) and select Extract Here or Extract to Folder .
  2. When WinRAR cannot find the next volume, it will show the “ Next Volume Is Required ” message.
  3. A small window will appear, allowing you to manually select the next volume .
  4. Use the file explorer window to locate the folder where the other archive parts are saved.
  5. Select the next part based on the naming order (example: select file.part2.rar after file.part1.rar ).
  6. Make sure the selected file matches the naming format of the archive (no extra characters like (1) and no mismatched numbering).
  7. WinRAR will resume extraction using the selected volume .
  8. If additional volumes are missing or stored separately, WinRAR may prompt you again. Repeat the same process until extraction completes.

3. Rename the RAR files in Order

WinRAR relies on a proper naming sequence (such as file.part1.rar , file.part2.rar , file.part3.rar ) to extract multi-volume archives. If a file is named incorrectly, contains extra characters, or is out of order, WinRAR may fail to locate the next volume and show this error. Renaming the files correctly helps WinRAR follow the sequence and extract the archive without interruptions .

Note: Renaming only changes the file name , not the file contents. The goal is to restore the correct sequence so WinRAR can detect the next volume.

  1. Go to the folder where all the RAR files are saved.
  2. Make sure all parts of the archive are present and stored in the same folder .
  3. Check how the parts are currently named . Common patterns include:
file.part1.rar, file.part2.rar, file.part3.rar
file.rar, file.r01, file.r02, file.r03
  1. Look for files that don’t match the expected numbering pattern (for example, file.part01.rar , file.part1(1).rar , or unrelated names).
  2. Rename each file so it follows the same order without extra characters or mismatched numbering. Example:
Incorrect: file.part1.rar, file.part3.rar, file.part2(1).rar
Correct: file.part1.rar, file.part2.rar, file.part3.rar
  1. Make sure the text before the number is exactly the same for all files.
  2. Only the last part number should change.
  3. Right-click the first file in the series (usually part1.rar or the main .rar file) and select Extract Here .
  4. WinRAR should now recognize the sequence and continue extraction normally .

If you still get the same prompt: the archive set is likely incomplete (a part was never downloaded or was removed), or one of the volumes is corrupt and must be re-downloaded from the original source.