Andy3252 October 19, 2016 14:56

New M-Track 2X2M Windows 10 driver installation issue

Okay so here goes my 5th attempt to get a resolution on the inability of M-Audio to fully understand the M-Track 2X2M driver installation issue that had me completely clean re-install Windows 10 three times and stop my product from being an expensive paperweight just sitting by my DAW work desk being non-functional.

In late September 2016 I purchased the M-Track after seeing it being demonstrated on the youtube channel. I thought it would be great for my needs having a nice sleek audio interface with a small footprint. I duly plugged it in and loaded the software and driver with no issue on my Windows 10 Pro set-up. However I had to alter some hardware a couple of weeks later and this meant I had to do a clean install of Win 10. Everything was fine until I went to install the M-Audio driver for the M-Track and I received an error in Device Manager stating:

" Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52) "

I tried and tried getting it installed, after all it work before (though not sure if that was an earlier version of the driver??), but no luck. Re-installed Windows again, making sure I loaded all updates, chipset drivers etc. but still no luck.

So I rang M-Audio support in the UK and was told I didn't need the driver as the M-Track is fully MIDI compliant, rather dumbstruck by this but decided I must remove the driver. Okay done, now its not seen as any hardware, has no ASIO driver and is not recognised aas a device in my DAW software. Just as I thought it wouldn't but I assumed M-Audio support must know what they are talking about.

So second call to M-Audio support UK and after explaining my problem again, the person said he would have to check with someone else, so put on hold for a few minutes and then on return he repeated that its fully MIDI compliant and I don't need drivers in Windows 10.

So here I am at stalemate still with a glorified paperweight, listening to support staff that obviously have no idea what they are talking about, as being MIDI compliant has nothing to do with the M-Tracks functionality as an audio interface, which is what I bought it for.

No other piece of hardware I have plugged into my PC has had its drivers refused, so this must be an issue that is M-Audio's responsibility to sort out. I have a product that does not do as it is purported to do and I am over £100 out of pocket, so come on M-Audio sort it !

I am not saying M-Audio equipment is poor as I have several other great items by them, I am just frustrated that I cannot get this issue resolved like many others with the same issue.

P.S. Don't tell me to look to Microsoft as no other drivers throw up this issue and don't tell me to disable code signing check every time I want to use my M-Track. Its a good job I have a Focusrite Interface to fall back on.
7 people have
this problem +1
This topic is no longer open for comments or replies.
  • EMPLOYEE
    Corey S (Official Rep) October 19, 2016 18:31
    Andy,

    Sorry for the experience with support. I can verify that the M-Track 2x2 and 2x2M both require drivers. Please use the guide below to verify that you're downloading the right one:

    Finding the Right Driver for Your M-Track

    Now, I've pointed this out several times already: The drivers are fully signed. Please see my post over here if you're still unsure.

    These have been fully tested and confirmed supported for the latest version of Windows 10, but it's important that you have all your updates in order. The driver signature process has changed recently and the M-track 2x2 will require the appropriate Windows updates in order to be recognized properly. If your other devices don't use this new process, than obviously they will be unaffected.

    I do not recommend simply booting into a different mode to work around this, but in order to dig deeper you will need to touch base with Microsoft. The fact that this was working and only stopped after you reinstalled the OS is very telling.

    Let me know if you have any questions.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Andy3252 October 19, 2016 19:52
    Thanks for your response and apologies if I sounded a little angry, it was through pure frustration. You have confirmed what I think I have just discovered. I have disabled secure boot within my bios and the driver now works fine, though I am unsure how I get the new driver signature into the secure boot database. I assume this is done during a windows update. I will trawl through all the updates and check I have everything, though I assumed I have as I have run windows update several times to ensure I am up to date.

    Again thanks for your help and guidance, I hope to have everything back to normal soon.

    Cheers

    Andy
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • I’m frustrated
    Patrick Lafferty November 19, 2016 03:19
    I'd like to chime in here, as I'm having the same exact issue. I just spent a few hours with Windows Devices/Driver support and they had me try everything in their book to get this driver working. I agree and acknowledge 100% that the driver I've downloaded from M-Audio (v1.0.4) is appropriately signed, but when I install it and open Device Manager, I still receive the following error:

    "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"

    I see that M Track 2x2 Control Panel is installed, but when I run it, it reads "Hardware Not Connected" across the top, despite the cable being clearly connected and the power light being illuminated on the M-Track.

    Microsoft had me uninstall the driver, open MSConfig and disable all non-Microsoft services, reboot my machine, and reinstall the driver, but the problem persists.

    To give some background information on my system: I have a brand new Dell XPS 15 running Windows 10 Pro Anniversary (version 1607), and I've run Windows Update multiple times today to make sure I have the most current build. I have a brand new M-Audio M-Track 2x2 (NOT 2x2M) that I have connected via my USB-C port.

    Any assistance here would be greatly appreciated. I would really love to start using this product, and do not want to put my machine at risk by using the above boot workaround.

    Thanks,
    Pat
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • I’m sad
    OLEG KACHANKO November 20, 2016 17:55
    Hi, all! I'm have the same exact issue too!
    M-Audio M-Track 2x2M and code 52
    Windows 10 64bit, 1607
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • I’m Frustrated
    Danny Rock November 22, 2016 23:01
    I also have this problem. Ive reset my entire system as a last resort thinking that this must work now. Not a chance. I dont get it. A brand new HP i7 Envy Desktop back to factory settings and windows updates installed. Still no joy. What can I do before I send this back and get a Focusrite?
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • OLEG KACHANKO November 23, 2016 07:40
    The only decision now is
    Disable-Secure-Boot in BIOS
    http://support.hp.com/us-en/document/...
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • I’m frustrated
    Alex Gray November 23, 2016 12:25
    With this and the buggy drivers for the M-Track Eight in other threads, it's very clear that M-Audio really needs to get its act together and hire driver experts to resolve the niggles before what should be trivial issues drag the company's reputation down the pan.

    The 'tech support' staff really don't have a clue, as in my own experience and as shown by Andy's experience. They just try to point the finger at anything else they can think of other than an obvious problem with M-Audio drivers.

    Whatever the root cause, if drivers installed on otherwise smooth running machines from a wide range of users and situations cause them to fall over repeatedly and frequently, then the drivers are not fit for purpose.

    Writing reliable drivers is perhaps one of the toughest software jobs to do, but that is what we are paying good money for, not a pile of bundled software tat that we could get as a cheap add-on if we really wanted it. Good software drivers cope with real situations on real machines, day-in day-out. M-Audio's current drivers for the M-Track Eight do not do this.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Danny Rock November 23, 2016 18:39
    I've disabled secure boot in the bios and this appears to have rectified the problem. I suppose I'm left with an unsecure boot now. Funnily enough, I was reinstalling Pro Tools 12.6 and I received the same message about unsigned digital signatures which has got me thinking. I originally restored my system following a problem with right clicking and creating a new folder in windows explorer. Windows explorer would be unresponsive for a couple of minutes every time. It was doing my head in so I hit reset in windows recovery. The digital signature problem occurred after the windows reset. I solved the original problem but then the M Track was causing problems when I was reinstalling everything again. I'm thinking that when I reset the system it may have been better to have taken out the additional hard drive that I had installed and an Avermedia capture card in a pci express slot when reinstalling windows and keep the hardware as it was when it was bought from HP, then do a factory setting reset. That's all I can think it is unless Microsoft have screwed something up in a recent update.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • OLEG KACHANKO November 26, 2016 10:39
    today: I tested on my system novation x-station and rme babyface - ALL without ANY problems with driver installation.
    good solution! good solution! (undo)
    • Ильдар Каримов November 26, 2016 12:05
      Олег, ты решил проблему со звучкой или нет, если да, то как?????я тоже тыкаю, переустанавливаю и ничего.....
    • Cancel
    • Alex Gray November 26, 2016 13:48
      The drivers install without problem for me too. The problem is that the system is from then onwards unstable - it will crash unpredictably, sometimes one in a few days, sometimes several times in a day.
      No-on is saying that the drivers fail on all systems, but it is clear that they fail on too many systems. Just because a driver works on some systems and not on others it does not mean it is the fault of those systems - a properly written driver should work on a wide range of systems and subsystems, and should not cause a crash by attempting to address non-existent code.
    • Cancel
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Ильдар Каримов November 26, 2016 11:58
    Олег, ты решил проблему со звучкой или нет, если да, то как?????я тоже тыкаю, переустанавливаю и ничего.....
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • OLEG KACHANKO November 26, 2016 12:08
    Я выключил в BIOS защищенную загрузку.
    Насколько я понял - проблема в чем: майкрософт с июля этого года объявила о спецзащищенности системы через UEFI Security Boot - на деле получается, что производители материнских плат (!!!) должны вписывать сигнатуру драйвера на мать. Для "старых" драйверов (до июля 2015) проблем нет, а для "новых" (M-Audio - апрель 2016) - система не дает запускать такие драйверы, если их не подписала сама Майкрософт, это как антивирус, короче работает, только на уровне материнской платы.
    Если отключить security boot - ничего страшного нет, в общем, но если подцепить хитрый вирус, то он обойдет и систему и антивирус, т.к. драйвер "реального режима" запускается с правами, такими же, как у системы.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • OLEG KACHANKO November 26, 2016 12:10
    Ищи ка отключить Security Boot in Bios
    например http://remontka.pro/secure-boot-disable/
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Patrick Lafferty November 29, 2016 04:02
    @Corey S - Any weigh in here would be greatly appreciated. Even if it's a general timeline of when we can expect updated drivers. I am currently ready to return my M-Track 2x2, but would rather keep it if you can give me some good news.

    Thanks,
    Pat
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Alex Gray November 29, 2016 12:57
    @Corey S - I second Patrick's question. My M-Track Eight is currently useless as it's drivers make the system unstable - they cause Windows to stop when they try to reference paged out memory causing a BSOD.

    Sometimes they will go a day or two without trouble, but rarely longer than that, and sometimes they crash twice or three times in a day.

    The memory dump points to a driver software fault rather than any hardware issue, and no other software on my system has any problem when the M-Audio drivers are removed.

    If this can't be fixed, I think M-Audio should offer to buy back all affected units at original purchase price.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • EMPLOYEE
    Corey S (Official Rep) November 29, 2016 13:53
    Hey guys,

    As I've pointed out, the drivers have been properly signed and qualified for use with Windows. Issues with Code 52 or problems with the system recognizing the signature have been linked to missing updates in the Windows system. If you continue to have trouble with this, contact your local Windows support and make sure that your system has been updated properly.

    Alex, your issue is very different and not at all common with the M-Track Eight. While I have encountered issues with BSOD's flagging the M-Track as a problem, it's rare that the driver is ever the cause. More often this is caused by unstable and mismatched components from user's building their own computers.

    I have to insist that issues with the M-Track Eight driver are extremely rare. I could only find one inquiry regarding a BSOD for that device. When this is the case it often boils down to something specific on the user's system, which becomes very difficult to pin-down on a community forum. It's often far too complicated and time-sensitive to handle through simple text. If you require further support with this, contact our team or your local Windows support for assistance. Here are a couple of options that you could choose from:

    • Submit a Warranty or Service Inquiry with our Technical Support team by logging onto the M-Audio Support Page. Select Warranty or Service Inquiry from the drop down menu. This will not require a support code.

    or

    • For faster support, call or email your nearest Support Office or International Distributor. Select your country to find the nearest office.

    I hope this clarifies! Let me know if you have any additional questions.

    p.s. I have notified the M-Audio team about the recent trouble with driver signatures. I will be sure to notify this thread and all other relevant threads if there is anything that can be changed from our end.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Alex Gray November 29, 2016 14:45
    @Corey S - I did try the support last year when i had the same problem on another computer, with no resolution at all, just more finger pointing in any direction other than M-Audio. I have replaced that computer with a brand new one, and Windows 7 with Windows 10, and get the same issues. But I will try support again.

    As for the number of people with similar problems, there may be only a few that have come to these pages, but there are more out on the Internet with very much the same experience. Eg
    Windows 7: BSOD when using M-Audio M-Track Eight
    http://www.sevenforums.com/bsod-help-...
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • rainer beck December 09, 2016 20:42
    I just bought an M-Track 2x2 today and I cannot for the sake of it install that thing in windows 10. Yes, I can boot up and disable digital driver signature enforcement but this will only work until I reboot. As soon as I reboot manually the yellow exlamation mark is displayed in the device manager and I get the error about the driver signature missing.

    and yes, my win 10 drivers are up to date.

    I will send that thing back on Monday what a waste of time
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Alex Gray December 09, 2016 21:19
    As of Friday I've abandoned attempts to use the M-Track 8, and gone to a 'cheapo' Behringer interface that needs no drivers and works just fine. I've also tested an old Edirol interface, and that is working perfectly as well. I shall see if I can get any money back on the M-Track.

    Alex
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Danny Rock December 10, 2016 06:34
    This is the message I get most days from this awfully written driver. M-Audio should be ashamed of themselves. Nothing but trouble!
    good solution! good solution! (undo)
    • view 1 more comment
    • Cancel
    • Alex Gray December 10, 2016 13:44
      Just so. That message is Windows trying to put a brave face on the fact that the M-Audio driver has wrongly attempted to access memory that is outside of its allocated areas. That causes the machine to stop because it could cause untold havoc to other software running on the computer.
    • Cancel
    • Corey S (Official Rep) December 12, 2016 22:14
      Hi Alex,

      I'd like to point out again that a BSOD with an M-Track Eight is rare and system specific. I'm disappointed to see that you haven't responded to my post on your other thread about the problem, though I understand if you've given up on it at this point:

      http://community.m-audio.com/m-audio/...

      Danny, I'd urge you to check out the link above for more info. But, as far as I know, you weren't having this problem before you "reset the system" and disabled secure boot in an earlier post. This, in all, does not sound like a very stable system. Granted, you were attempting to re-route around another issue, but booting into different modes was something I adamantly opposed in my first post.

      Changing settings in BIOS and straying from manufacturer defaults are a large contributor to BSOD's and very likely the cause of your problem. I will gladly go out on a limb here and say that a BSOD with the M-Track 2x2 is far more rare than one with the M-Track Eight, and I've even connected several cases to having the incorrect M-Track driver installed.

      In the end, it would be in your best interest to factory reset your system and start over.
    • Cancel
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • I’m sad that the M-Audio unit has proved such a problem for us.
    Alex Gray December 12, 2016 23:42

    Corey wrote: I'd like to point out again that a BSOD with an M-Track Eight is rare and system specific. I'm disappointed to see that you haven't responded to my post on your other thread about the problem, though I understand if you've given up on it at this point:


    I simply couldn't afford the time to continue following it up Corey. It has already cost me more than the cost of the product itself in downtime and trying to sort it out, not to mention the inconvenience caused to other staff with repeated crashes or freezing of sound output.

    Since I removed the M-Audio driver last week the machine has run 24x7 without a single problem, including 24 hours of solid unattended audio playback. The Behringer audio interface is working fine, but doesn't have a balanced audio connections, which I would prefer. I have also tried an older Edirol interface today, which although also needing its own drivers appears so far to run without a hitch, so I may try that as a means of getting back to balanced audio connections.

    Alex
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Donovan Burgess December 13, 2016 02:19
    This would honestly make more sense if Corey would do his job as a support technician, and instead of following up every single response to an inquiry with links to
    "Finding the Right Driver For Your M-Track"
    "M-AUDIO support page"
    or whatever crap we're getting...

    Link us to a specific Windows page for Windows 7 64 and 10 64 bit, with the EXACT single update required to resolve this issue.
    Clearly, he doesn't realize that most of us really do not want to enable automatic updates and render our machines inoperable for eight hours while it configures crappy updates.

    Corey, do your job.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Alex Gray December 13, 2016 12:09
    I don't mind being directed to a new driver, but Corey's lazy link takes me eventually to just the same driver I've been using from the start. I have twice uninstalled it and reinstalled it, with the same result each time. When the driver is uninstalled the machine is reliable, when the driver is installed the machine becomes unreliable.

    I do understand that there can be quirky driver interactions, but these generally happen only on systems with poorly written third-party drivers or an unfortunate combination of non-standard hardware and drivers. I am doing this on a pretty clean system. It has absolutely no other peripherals or expansion cards installed, no strange disk drives or quirky configuration. It is a standard Windows 10 64-bit installation on a commercial Intel i5 motherboard. The only other peripherals are just standard HID devices, mouse and keyboard, and I'm not aware of any third-party drivers having been installed, just those that come with the base Windows setup.

    If M-Audio's driver does not work reliably under these circumstances, and the machine works perfectly without the driver, I feel it is reasonable to point the finger at the driver, not just to dismiss it with an "all sorts of things can cause a BSOD".

    The specific error causing the system to stop is a safety measure that is designed to trap badly behaved drivers that attempt to write to an area of memory not 'belonging' to the driver. A well written driver would make these checks for itself and report a problem or take evasive action rather than leaving it to the system to stop altogether.

    Edit: I should perhaps add that if I was the sort of user who does a studio session or gig that means I switch the machine on, work for a few hours and shut down, I might never notice anything wrong. But my machine is in professional radio station use 24x7, and does not normally get more than a routine weekly reboot as good practice. And an unexpected reboot can have an immediate and very unwelcome impact on our broadcast output.

    The M-Audio driver crash mostly happens after it has been in use for at least a few hours, if not a day or two. It tends to happen when playback software switches from playing an MP3 file to a WAV file or vice versa. If I were a home studio or hobbyist user and got a crash or hang after several hours I would probably think 'oh well, just one of those things', and reboot without ever reporting the problem to M-Audio. So they may have a wildly inaccurate idea of how common this issue is.

    I guess we just have to regard this as a 'hobbyist-only' product, and rule it out for frontline professional use.

    Alex
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • 1
    James May December 26, 2016 11:08
    I also have the problem. This problem has wasted so much time for me and for others. It has been going on for too long now.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • EMPLOYEE
    1
    Corey S (Official Rep) December 30, 2016 20:26
    Hi everyone,

    Heads up! We just posted a new driver for the M-Track 2x2 and M-Track 2x2M that will work around this problem with the Driver Signature enforcement.

    If you are having trouble with this, please uninstall the current driver, then download/install the latest driver for your M-Track model from the guide below:

    Finding the Right Driver for Your M-Track

    Hope this helps!
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Donovan Burgess December 31, 2016 04:10
    Just installed the new driver after removing the old one (the one that was giving us Code 52)

    Now the audio interface isn't even recognized by the system.
    "USB Device has malfunctioned"

    Yeah, great job M-Audio.
    You're keeping up your reputation of not being able to code drivers that are worth a damn.

    I mean, seriously.
    Focusrite doesn't have this much trouble.
    Behringer doesn't have this much trouble.

    I'm seeing a pattern.

    Corey, if you could please just redirect us to the version just before 1.0.6, that would be great. At least I can actually use my audio interface via disabling driver signature enforcement with the old version.
    good solution! good solution! (undo)
    • James May December 31, 2016 11:56
      I have installed the new driver and it works perfectly. if you're computer cant recognize it. its nothing to do with the driver.
    • Cancel
    • Corey S (Official Rep) January 04, 2017 21:55
      Hi Donovan,

      James is right, this isn't necessarily the driver anymore, though possibly a conflict. The older driver is no longer available from our website, though you may still have it in your downloads folder.

      If you continue having trouble, I'd recommend contacting our support team directly or creating your own thread. Here are a couple of options that you could choose from:

      • Submit a Warranty or Service Inquiry with our Technical Support team by logging onto the M-Audio Support Page. Select Warranty or Service Inquiry from the drop down menu. This will not require a support code.

      or

      • For faster support, call or email your nearest Support Office or International Distributor. Select your country to find the nearest office.

      Make sure to reference or link to this thread to help out the support team.

      Let me know if you have any additional questions.
    • Cancel
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • James May December 31, 2016 10:12
    I was about to send it back but I'll give it another go with the new driver.
    Comment
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel
  • Roman Hanák Jr. January 02, 2017 16:37
    Today I bought this device, but I've got some troubles with driver. Even with the latest driver 28.12.2016, windows says, that it is not signed, as you can see in the picture.
    good solution! good solution! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

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

    Cancel