Mikro MK3 won't install in my new computer.

OldSchool

I looked around and did not find my exact issue or anything that worked for me. I apologize if I have placed this in the wrong area. I tried the auto-chat and could not get an email to Native Instruments support. The AI asked me some tech questions and may have sent that in. I don't know, it never acknowledged that it did. I don't often have installation issues, I repair computers but am a bit of a novice about USB audio although I am a pro from the analog days. This is just to let you know about me.

When installing Native Access in my Windows 11 Pro 32GB DDR4 using a 4TB NVmE NE (Native Access from here on out) causes an old-fashioned bluescreen!

When rebooted the NE app is working but the Controller Editor (CE) is partially installed. It opens but when looking at it the link is a blank white icon and Windows uninstall tries to install it and when it tries to find it, it asks me to navigate there, when I do it refuses to see the folder or the exe in that folder and totally fails.

I then use Revo to surgically uninstall and then the version of CE successfully installs and offers an update. I am sure if I could sidestep NA and just install the pieces this would all work. But n matter what I do, CE, after selecting my Mikro MK3 from the list, does not 'see' my device, (the connect button is grayed out).

When plugging in the device the quick all lights boot procedure occurs and then it settles on just the select window in white with the words 'Maschine Mikro'. It was fine days ago on my old computer. I have tried USB ports on the motherboard, on a PCiE card, and even on a hub.

I am using the original USB cable that came with my then brand-new Mikro MK3. That cable has never been stressed and looks new. All of my other USB audio devices operate perfectly, SSL 2+, Elgato Wave XLR, Streamdeck XL, and my Launchpad X.

LostInFoundation

Is the problem solved as per your Profile page?

Otherwise I would suggest to check if NI Agents are running in the background or not

OldSchool

I am not sure what that means? I did try to manually install the NTKDaemon as some suggested, but that did not help. What 'Profile page'? On the NI website? or in Windows 11 Pro? It is possible to install all the elements manually? The failure occurs when Native Access runs the show. I get the feeling that it is sensing something I don't have as it does install an MK2 app, (Native Instruments Komplete Kontrol MK2 driver).

Could that help find what went wrong? I have a Mikro MK3 (not MK2). Again, I am a nube on this and wildly shooting in the dark, here.

OldSchool

At one-point, Native Access did install what I know to be known bad,

Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.40664 and

Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.40664 drivers!

Those remain installed when the newer, fixed drivers,

Microsoft Visual C++ 2015-2022 Redistributable (x64) 14.42.34433

Microsoft Visual C++ 2015-2022 Redistributable (x64) 14.42.34433 drivers.

Could that be part of this issue?

OldSchool

Visual Studio 2013 has a vulnerability1 that allows an attacker to gain elevated permissions on a vulnerable system. Additionally, there is a remote code execution vulnerability in Microsoft Visual Studio 2013 when it incorrectly handles debug information. Also, Microsoft claims the 2013 version 12.xxx is 'no longer supported'.

LostInFoundation

I mean this message in your profile page here on the forum:

But it seems that your problem isn’t solved, so we can continue ☺️

Check in Task Manager if the 2 NI Agents are running (NIHostIntegrationAgent and NIHardwareAgent)

Check point 4 of this support article: (and, while you are there, also the other points ☺️)

https://support.native-instruments.com/hc/en-us/articles/4410096148113-My-Native-Instruments-Hardware-Device-is-Not-Recognized

OldSchool

Thanks. Will follow the procedure in that link. Sorry about the 'profile' confusion. That was on my old motherboard, so none of that happened. This new 'clean' Windows 11 Pro install on a new motherboard has failed. Knowing about that previous fail, I was careful to follow the steps. I first downloaded the Native Access app and installed. I got a Windows error (bluescreen) and forced reboot. Since then, nothing has worked as I explained in the beginning of this thread.

red_nick

Does the Maschine software itself detect the Mikro?

OldSchool

I have done all those before. I researched this for a week before coming here. I even read other's issues on this site. First, am I expecting too much? Shouldn't the Controller Editor 'see' my device?

I tried a totally fresh install on my laptop. I logged into my NI account and downloaded Native Access. Here I go not bluescreen installing it, but I have no other USB audio in this laptop. Next, I logged into Native Access and opened Controller editor and got an error message I will attach, but after running the update for Controller Editor that opened without complaint. But still no acknowledgement to my Mikro MK3 from Controller Editor! Note* On the laptop I used a USB 2.0. I wasn't aware that was necessary until deep support suggested using a USB 2.0 port.

Again, the attachment was running Controller Editor before its needed upgrade, so that may not be too important.

3_27_2025 13_37_41 PM - Controller Editor-mini.nicrash

OldSchool

Is there a 'hard reset' on the Maschine Mikro MK3 itself? I feel like I am missing something simple.

PK The DJ

I'm curious why you're posting so much about Controller Editor when the thread is about installing the Mikro MK3. If your goal is to use the Mikro MK3 with Maschine to record & play back music then you don't need to run Controller Editor. Just install Maschine 3 software, then run it with the Mikro MK3 connected.

OldSchool

I thought Maschine 3 won't open until Controller Editor 'sees' the device. It was not my original issue, but seemed to be a flag to judge whether it is working. The only light on the Mikro MK3 is the white selection window that states "Maschine Mikro". Nothing else responds. When installed correctly the app Maschine 3 would react to buttons and settings I chose in the Maschine 3 app. Is the app not compatible? Is there a better way to install and/or test my Mikro MK3?

OldSchool

In Ref to: Check in Task Manager if the 2 NI Agents are running (NIHostIntegrationAgent and NIHardwareAgent)

The only services I see running are: NIHardwareService and NTKDaemonService

LostInFoundation

Your intuition was not wrong: checking if the controller is seen in Controller Editor is a good way to check if the device is recognized.

Maschine Mikro mk3 is compatible with Maschine 3 software.

About the hosts: also NIHostIntegrationAgent should be there (it’s used by the softwares that can host plugins (therefore Komplete Kontrol but also Maschine…at least that is my understanding)..

If I’m not wrong, those agents are installed when installing the software. Have you tried deleting and reinstalling Maschine software?

OldSchool

WOW! I got Maschine 3 to install without error on the laptop! All the services are running, and the Mikro MK3 lit up like a Christmas tree! I am not sure what I did differently, but all previous times Maschine 3 failed to install. I did a forced 'log in as Administrator' on both the Native Access app and when launching Maschine 3. I did not think since I am an administrator that it would make a difference, but it does now.

I never had to do that on my old computer, both were running Windows 11 Pro and I only upgraded to get more native USB ports (on the motherboard) so my USB audio would integrate better.

So maybe my solution was just manually force 'open as administrator' every time I use a Native Instruments app?

OldSchool

Thank you, LostInFoundation your assistance was what I needed!

It may be a 'chicken and an egg' situation, but after the Maschine 3 app opened, Controller Editor now 'sees' the Mikro MK3! I think Maschine 3 is needed to first install those two key services, NIHostIntegrationAgent and NIHardwareAgent before detection is possible. Thanks for the guidance!

Note to Native Instruments Support: A simple standalone version of Maschine 3 would probably fix many installations gone wrong. I still have to figure out how I am going to get Maschine 3 installed in my desktop computer, but having a working model in my laptop will help big-time!