(Make sure this is latest DRV visible from MIDI KBD Manufacturer and not any alternate or old drv by default)* MS Win 10 is working well and there is no possible turning back to Win 7 for me now but unless bloody MS System Updates are pushed to our Musical workstations, i must admit it is fast and stable in my case MS Win10 Pro V1903 + ABL V10.1. See the release notes for whats new or fixed, known issues, and supported hardware. Note: Windows 11 is only supported in 64-bit. Maybe it could help you too?Ģ/ in Device Manager remove your device and driver for Acorn Masterkey 61 MIDI keyboard (Make sure you have somewhere the very latest version of this specific driver but should be reinstalled by Krosoft if DRV not corrupted!),Ĥ/ Check your device manager your KBD / DRV do not appear yetĥ/ Use Driver Easy or equivalent and update your system (it is free and working well but could be slow depending on the size of your DRV so could check DRV REF with tool and go to manufacturer site to download full speed!?)ħ/ Switch on your KBD to plug and pray. Install M-Audio Oxygen Pro 61 FWv2.1.2 - Windows.zip: Applies To: Oxygen Pro 61: Operating Systems: Windows 8.1 (32-bit) Windows 8.1 (64-bit) Windows 10 (32-bit) Windows 10 (64-bit) Windows 11: Version: 2.1.2: Release Date : : Release Notes: Update your firmware to version 2.1.2. WiFi-23.30.0-Driver64-Win10-Win11.exe for 64-bit of Windows® 10 and Windows 11 for 32-bit of Windows® 10 Check if your Windows 10 is 32-bit or 64-bit. Native support for both Power PC and improved support for Intel-based Macintosh computers. I had similar issue with Novation KBD 49SL MkIII on windows 10 after update 1903. Librarian Editor with support For: Axiom 25 Axiom 49 Axiom 61 Oxygen 8v2 Oxygen 49 Oxygen 61, MK-425c, MK-449c, MK-461c, UC-33e, Keystation Pro 88, O2, Ozonic, Trigger Finger and X-Session. I believe your Windows fucks up power management, so perhaps this is what you might wanna try as well:ĮDIT: my idea of how I understand the issue is, plugging a class-compliant device requires 2-way "initialization" which if by any means fails (perhaps some fancy eco-friendly bullsh!t stuff or any other cause for insufficient voltage in usb bus chain, which sadly nowadays is software/kernel dependant) can simply "cutoff" your keyboard due to being considered nonexistent for system to look at let me explain my "troll-post" above actually IS the easy solution - I was experiencing very similar issue, where certain usb external drives randomly failed to show up in Windows, as soon as I installed MacOS on the very same computer (same motherboard, same BIOS settings, same usb ports.), I have never ever experienced the issue again (and also I was able to "remove" drive from MacOS and "add" it again without physically replugging it), so apparently there IS something done different in terms of initializing and accessing devices on Windows vs MacOS