Patched: M Audio Mtrack Plus Driver Full
Important Note: The original M-Track Plus (silver/blue chassis with two combo jacks) is a legacy device. It is not officially supported on Windows 11, macOS Catalina (10.15) or newer. Workarounds exist, but success is not guaranteed.
Part 4: Troubleshooting & Fixes
You’ve downloaded the "full" driver, but it still isn't working. Here are the most common hardware/software collisions.
For Windows Users (The Critical Step)
If you are on Windows 10 or Windows 11, you must install the dedicated driver. Windows will not automatically recognize the M-Track Plus with the performance settings required for music production. m audio mtrack plus driver full
- The Risk: If you skip this, you will experience "lag" where your vocals come through your headphones milliseconds after you sing them, making tracking impossible.
How to Find and Install the "Full" Driver Package
Many users search for a "full" driver because they are tired of partial functionality. To ensure you get the complete package—including the control panel software and firmware—you must avoid third-party "driver updater" sites. These often host malware or outdated files.
The Official Method:
- Navigate to the official M-Audio Support Page.
- Search for "M-Track Plus" (Note: Do not confuse this with the "M-Track" original or the "M-Track II" or "M-Track 2X2"—the drivers are distinct for each specific model).
- Select your Operating System (Windows 10, Windows 11, etc.).
- Download the latest version (often labeled v1.0.x or newer).
Installation Tip:
Do not plug the interface in before running the installer.
- Download the driver package.
- Run the installer as Administrator.
- Follow the prompts and restart your computer.
- Then, plug the M-Track Plus into a USB port.
4. Installation Protocol: The Full Package
To successfully install the "full" driver for the M-Track Plus (Original), the following technical protocol is recommended to avoid corruption or installation loops: Part 4: Troubleshooting & Fixes You’ve downloaded the
- Extraction: The driver usually downloads as a compressed
.zip or .dmg file. It must be extracted to a local directory rather than run directly from the archive.
- Device Isolation: The physical USB connection must remain disconnected until the driver installation wizard explicitly prompts the user to connect the device. Premature connection can cause the OS to map the device to a generic USB audio driver (such as the Microsoft USB Audio 2.0 driver), which conflicts with the proprietary M-Audio driver.
- Security Privileges: On Windows, the installation must be executed with Administrative privileges. On macOS, the user must approve the M-Audio system extension in the "Security & Privacy" settings in System Preferences before the device can be initialized.
- Verification: Upon installation, the device should appear in the Device Manager (Windows) or Audio MIDI Setup (macOS) as "M-Audio M-Track Plus," not as a "Generic USB Audio Device."
3.1. Legacy Support (Windows 7 / macOS 10.8)
The original M-Track Plus was developed during the Windows 7 and OS X Mountain Lion eras. The "full" driver packages from this period often contained proprietary control panels allowing users to toggle hardware routing directly from the desktop.
5.2. Common Failure Points
- Driver Conflict: If the device was plugged in before installation, the user must navigate to Device Manager, locate the device under "Sound, video and game controllers," right-click, select "Uninstall device," check the box for "Attempt to remove the driver for this device," and reboot before attempting a clean install.
- USB Bus Power: The M-Track Plus is bus-powered. Connecting it to an unpowered USB hub can cause driver instability and audio dropouts. It must be connected directly to a host USB port.
🔧 Pro tip for Windows 10/11:
After installing the full driver:
- Reboot
- Open “M-Audio M-Track Plus Control Panel” (found in Start Menu)
- Set buffer size to 256 samples for stable recording
- In your DAW, select ASIO → M-Track Plus ASIO driver
If Windows doesn’t recognize it, try a different USB port (not 3.0, use 2.0 if possible) and a known-good USB cable.