Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m frustrated

M-Audio M-Track Plus MK2 NOT compatible with Windows 10 (more inside)

This is a long post and my aim is to get M-Audio to aknowledge that their drivers for Windows 10 NEED fixing and updating...

So I've had my M-Track Plus Mk2 now for around 6 months and have 'put up' with having to reset the sample rate every few hours when it stops working and the occasional BSODs due to the awful drivers. I have tried to work with M-Audio on the issue and so far I've been told...

* It's my RAM (it wasn't, I ran memtest86 over night and tried different RAM)
* It's Microsoft's fault due to their bad audio drivers and to contact Microsoft to get fixed drivers - As you can guess they don't have 'fixed' drivers and assured me that it's M-Audio's responsibility to make drivers that work with Windows.
* It's my USB port(s). I've tried the ones in the front, the ones on my screen, my USB hub, all 16 of the ones on my motherboard and a well known PCI-E USB hub. I also have a friend with a different motherboard and an M-Track and he has the same problems.
* It's my motherboard (see above).
* It's my friends motherboard (when I told them I tried a different computer).
* It's the speakers, then quickly changed to 'it's the USB cable' when I told them I'm using a pair of M-Audio BX8 D2's. I've tried 6 different cables of varying length and quality - It's not the cable.
* It's your audio software - Spotify, Chome (Youtube), various games and ProTools all exhibit the same issues.

Then finally, someone got it right and said "It's the audio backend windows uses and our drivers don't always play nice." and that "they'll look into getting them updated" - This was last year!

What has happened since then is almost all of the major UK resellers (Scan, Overclockers are the ones I know but I know others have followed suite) have either stopped selling this completely due to the high volume of returns or are marking this as not compatible with Windows.

Please fix the damn drivers as it is a great bit of kit otherwise.
11 people have
this problem
+1
Reply
  • Hi Chaoss,

    Thanks for posting!

    In my personal experience and from what I've found on the forums, driver responses like this are rare and often dependent on the user's system (i.e. the motherboard as you've already pointed out). Please note, I am not blaming your motherboard or system as the culprit, though it likely plays a part. Considering that not every Windows 10 user experiences this problem, it will appear to be dependent at least somewhat on the user's system.

    Before pointing at the M-track driver as the culprit:

    - Make sure that you have the correct driver. A lot of users download the wrong drivers accidentally and experience strange issues. Use the guide below to verify:

    Finding the Right Driver for Your M-Track

    - Follow the guide below for possible BSOD troubleshooting scenarios:

    http://www.howtogeek.com/163452/every...

    Finally, provide your complete system specs and I'll be happy to notify the team of your experience, in case there is anything that can be improved on our end.

    Thanks!
    • view 2 more comments
    • It's M Track. Their drivers are crap and they act like it's not their fault.
    • M-Track Plus MKII works wonderfully on my windows 10 64-bit system.. And it has now for over a year.. currently using the 1.0.3 M-Track driver and I have found that this interface is even capable of 32-bit / 96000 Hz Recording! I love this little interface and I am so confused why everyone is having such trouble with it and blaming M-Audio.. I firmly believe that its an issue with these users ;particular component/driver configurations that are the issue.. Because I use Studio One 3.5, FL Studio 20.1 and many other programs with no issue at all with this interface.. And it sounds great too! Super clean..

      @PHILTHY9FIFTY
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m Sad
    Having the exact same problem here i think, win 10 stops recognizing m-track mkII all the time and when i put my pc in suspension mode with the m-track turned on i get the BSOD . It ́s really frustating, it used to work like a charm on my win 7 old pc, sadly i will have to roll back to win 7 for now. Sorry for my english btw, not a native.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • those supposed windows 10 drivers DO NOT WORK, i can vouch for having the EXACT SAME EXPERIENCE with the original poster......... damn near word for word! and STILL...... they have yet to fix the damn drivers! NEVER BUYING M-AUDIO AGAIN.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • 1
    Hi, I have a M-Audio M-Track Plus which works fine on all windows 8 machines that I have. It does not work however on any windows 10 machine I'm tried it on. The M-Track Plus comes up under other devices in device manager with a caution symbol exclamation mark icon next to it. Windows does not recognise it as an audio device. The current driver is from 2013. I think it's high time M-Audio addresses this issue.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • Do note something. Windows 10 was released July 2015. Their supposedly compatible Windows 10 driver was released January 2015 for this specific device with zero updates. There is obviously an issue if they are releasing drivers before an OS is finalized, as well as the many updates that come after.
    http://www.m-audio.com/support/downlo...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • I’m frustrated
    Same boat. I have tried 1.0.6 drivers, very bad idea. The correct 1.0.3 driver is ancient and until there is an update I am using Asio drivers, more settings and until M-Track sort their ting out I will continue to do so. Works like a dream in Ableton and FL. Terrible Show M-Audio
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I've had intermittent BSOD's over the last couple years, all with Windows 10. Today I switched the USB port I had my m-track plus mk2 plugged into and now device manager is giving me errors for M-Audio DFU.

    Interface "works" with terrible distortion using ASIO4ALL but not all audio programs support ASIO (anything from the windows store, for example).
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • My solution: switching to a USB 3.1 slot. Now everything is working.
    • Did the same with a mobo that has a combined Thunderbolt 3/USB 3.1 slot with USB-C connection, and using USB-C to USB-A adapter with the interface seems to be working for a week. We'll see if it lasts the month. Unfortunately, not everyone will have a USB 3.1 slot even if this ends up working on term. Far cheaper to change an audio interface than to change a computer. The M-Track Plus MKII's 48v phantom power is still terrible either ways.
    • So I held off on upgrading to the older Windows 10 Creators update as long as possible, and now it finally updated. USB-C port now gets the BSODs like the normal USB 2.0/3.0 ones. This leads me to believe that the drivers are definitely the culprit. Looks like this piece of junk is going in storage again.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I’m frustrated
    1
    Same here, BSOD's every day or so under Windows 10.
    >My devices are the M-Audio M-Track.
    >Have tried the 1.0.3 driver for both Plus & Hub and still the
    MAudioMTrack.sys crashes.
    >Was fine under Windows 7.
    >Have tried different USB port types
    >Have tried disabling Secure Boot in bios, which worked for a
    while but fails again under Win10 Creators update.
    Still awaiting updates from M-Audio
    Very poor support.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • I purchased m-track 2x2 installed driver 1.0.6 as administrator on asus n53s intel i7 2630m controller fresco logic (driver 3.8.33709.0 last) windows 10 updated
    connecting interface on usb 3.0 the board only plays noises while in usb 2.0 everything works.
    Is it possible to solve the problem or do I have to return and go to another product?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • 1
    The Windows 10 driver for this hasn't been updated since 01-15-2015. Considering Windows 10 officially released on 29 July 2015 I have no doubt in my mind that the BSOD's are due to lacking drivers (considering the amount of updates that Windows 10 has had since 2015).

    The "custom PC" argument in M-Audio's official response in the 2x2 thread (that they've now locked) is a red herring that might work on technological luddites, but it won't fly with us. Most people in the audio industry are not buying off-the-shelf overpriced Dell PC's (which use the same hardware components & drivers as these mythical "custom PC's" M-Audio keeps mentioning).

    We all know what we are doing here and how to update motherboard and component drivers e.t.c.

    This is elementary level stuff, please do not continue to patronize us and just admit you have messed up with keeping drivers up to date.

    Not one other bit of external hardware I've purchased has ever caused BSOD's like my M-Track Plus II.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • 1
    Not one blue screen since M-audio hardware and driver removed from my pc. Happy days! Working fine and stable now with Roland Rubix .
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • This reply was removed on 2018-06-09.
    see the change log
  • I’m Rolling
    M-Track Plus MKII works wonderfully on my windows 10 64-bit system.. And it has now for over a year.. currently using the 1.0.3 M-Track driver and I have found that this interface is even capable of 32-bit / 96000 Hz Recording! I love this little interface and I am so confused why everyone is having such trouble with it and blaming M-Audio.. I firmly believe that its an issue with these users ;particular component/driver configurations that are the issue.. Because I use Studio One 3.5, FL Studio 20.1 and many other programs with no issue at all with this interface.. And it sounds great too! Super clean..

    @PHILTHY9FIFTY
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited

  • Worked ok first day, dropped a backing track MP3 from my bassist. Recorded 2 completely dry guitar tracks, DL'd and added amp model, cab NAD-IR, and IR's. Rendered to an mp3 track, worked well.

    Came back last night, opened Reaper (DAW) and project was still there. Hit play.. the backing bass track was now this whisper quiet, electronically garbled almost talking backswards type noise. I was like WTF, hoped on youtube and played a vid, some crazy garbled sound, as was any MP3 file I clicked on on my PC.

    Turned off Maudio output, going through my PC sound card all fine, go back to Maudio.. same garbled junk. Figured maybe driver so tried to reinstall newest driver but only gave an option to repair. So I did, then restarted PC and all. After played ok with some pops.

    Started as a new project, dropped the MP3, started recording 2 guitar tracks, this time with amp and cab loaded so good tone from the start. Could never make it through a 4 mins song before it would flip out, drop all sound from the MP3 file, and drop all my tone back to completely dry. Effects showed still active, amp showed "on" but nothing but dry.

    I'd close reaper, or disconnect Maudio and both would be back only to drop/fail again. Then it started stuttering on the recording if it didn't drop out making it impossible to record. Seems completely unusable to me, and support seems to be horrid.

    Fair to say is a 1 year old basic HP laptop with window 10 (which I hate). Today looking around seems many are having this problem with Win 10. Love to have some help or ideas but looking like I'll be returning it. Just ordered a Focusrite Scarlett Solo.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

  • Hey Ray, I have managed to get this stable running fl, cubase and Ableton 10 with a push 2 with some maudio monitors. I have settled on the .03 driver I think it's made for the mk 1 but I use it successfully on the mk 2. No issues after swapping out audio cables previously but now seems stable. My advice would be to remove ALL audio drivers disconnect mtrack, reboot only install .03 driver and test again. Will send pic of my audio settings but I was getting bsod's and weirdness until I did this process a few times
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited