![Arturia keylab vs nektar impact](https://kumkoniak.com/34.jpg)
![arturia keylab vs nektar impact arturia keylab vs nektar impact](https://info.shimamura.co.jp/digital/img/upload/shimastaff/2016/BeatStep-Black-Edition-1024x447.png)
It finally found the Keylab and is currently working.
![arturia keylab vs nektar impact arturia keylab vs nektar impact](https://www.strumentimusicali.net/images/product/600x450/2021/05/18/10/arturia-arturiakeylab88vcollection7omaggiousato-1.jpg)
I shut down Pro Tools, closed the MCC, then re-opened Pro Tools. After selecting the DAW in the MCC, I opened Pro Tools and it didn't find the device. It connected to the device, so I ran the firmware update. I then installed the MIDI Control Center and turned on the Keylab. I had turned off the Keylab, uninstalled the driver, uninstalled the MIDI Control Center, and rebooted. I read a thread somewhere discussing how Windows MIDI is easily hijacked, so I started disconnecting everything that was non-essential, and shutting down any processes that were audio-related. MCC found the device, but said it couldn't connect because it may be in use by something else. I connected the Keylab to a powered USB 2 hub.
![Arturia keylab vs nektar impact](https://kumkoniak.com/34.jpg)