Notifications
Clear all

MIDI Control Surface Failure - Hercules DJ Console MK2 - Windows 11 Compatibility Issue (KB5074105)

2 Posts
3 Users
0 Reactions
17 Views
0
Topic starter

I am writing to report a critical issue with my Hercules DJ Console MK2 on Windows 11. I also wanted to inform you that your French support website currently appears to be down/out of service.

Issue Summary: Following the recent Windows 11 KB5074105 update, the MIDI control surface of my console has become completely unresponsive. While the audio interface (ASIO) continues to function perfectly, allowing for playback and headphone monitoring, no MIDI signals are being transmitted or received by the system.

Environment Details:

  • Computer: Lenovo Ideapad 3 14ITL6.

  • OS: Windows 11 (Post-KB5074105 update).

  • Software: Virtual DJ 2026 (v2026 b9004).

  • Drivers: Package 2.HDJS.2023 (Driver v6.3.0.0, Firmware v1.3.6.15).

  • Hardware: Tested with two different MK2 units (one of which is brand new/NOS) across multiple USB cables and ports.

Technical Breakdown (as <a href=" removed link " target="_blank" rel="noopener">identified via Virtual DJ community and system logs):

  • Driver Blocking: The KB5074105 update has significantly reinforced Windows 11 security policies regarding legacy drivers. Even with Core Isolation (HVCI), Memory Integrity, and the Vulnerable Driver Blocklist manually disabled, the MIDI/Bulk layer of the 2.HDJS.2023 driver is being filtered or ignored by the OS.

  • MidiIn Silent: System logs (HDJInfo.txt) show that while the Hercules® DJ Control MP3 service is running, the "MidiIn" counter remains at zero.

  • USB Controller Conflict: There is a failure in the data handshake between the Intel USB 3.1 Controller and the console’s legacy protocol. I have already attempted to disable all USB power management settings (Selective Suspend) for the Root Hubs without success.

Request: Virtual DJ support has confirmed that this is a software/driver conflict caused by Microsoft's new security architecture in Windows 11. Since the hardware is functional, does Hercules/Guillemot plan to release a driver update to restore MIDI compatibility with these newer Windows 11 security layers?

2 Answers
0

Hello DJ Le Chiffre,

 

Thanks for your message.

 

1) I just logged & connected on the French supporrt website with no problem

https://support.hercules.com/fr/portal-login-fr/

When did you try and find it was offline?

 

2) KB5074105 update seems to be a pre-version, not a final version.

https://support.microsoft.com/en-us/topic/january-29-2026-kb5074105-os-builds-26200-7705-and-26100-7705-preview-85bd25de-894a-43eb-a19b-9a59d10f194b

VirtualDJ blog describes KB5074105 as a preliminary version, and suggests to uninstall it according to the process they describe if you meet an issue.

https://www.virtualdj.com/wiki/Win11-KB5074105.html

In Reddit, Pete Brown form Microsoft says the final release should arrive in March.

 

3) I am surprised you tested "with two different MK2 units (one of which is brand new/NOS)" as DJ Console Mk2 was phased out before 2010, so having a brand new one is unusual.

  • Please confirm your DJ controller is DJ Console Mk2 (there are other MK2 in Hercules, the latest ones are DJControl Inpulse 200 Mk2 and DJControl Inpulse 300 MK2)
  • If your brand new DJ Controller is DJ Console MK2, make sure you update its built-in firmware (with a USB hub which has a power adapter connected) in a PC with Windows 7 or 8.0, as, DJ Console Mk2 cannot boot with the factory firmware on computers with Windows 8.1/10/11(the reason is that DJ Console Mk2 was released before USB 3, and in Windows 8.1, Microsoft USB layer changed the way to enumerate USB devices in a way which does not work with the original firmware).
0

I would uninstall the KB5074105 update, as it caused problems for several users. However, Microsoft is likely to release a new patch on February 10, so I would wait for that. There are several cases where cameras and other devices also had problems with the January update. My recommendation is to suspend the update until February 10 and uninstall update KB5074105. Restart and wait for the update in February.