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 MP3service 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?
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.
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 from Microsoft has written 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).
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.
1. I've called the French phone hotline and the clerk opened a Sharepoint space where I could upload a complete reports and full logs
2. I'm discussing with Mr. Pete Brown on his Discord and he is very commited to help me (us) to solve that issue. Indeed, I have difficulties to uninstall thos KB. Mr Brown may have some questions regarding the MIDI driver of the Hercules DJ Console MK2 so feel free to join and exchange with him if useful or necessary.
3. I have a 2006 unit named "DJ Console MK2" on its back label ref 4780393. Since I falsely believed it was our of order after almost 20 years of loyal functional, I've found, on the most famous second hand trade Website "Le Bon Coin" a brand new unit named "DJ Console MK2 Traktor" ref 4780431, never opened, never used (collector ! It's also noticeable that the rubber on the job wheels is as much sticky as its 20 years older brother).
I do have a 2003 PC running under Windows 7 32 bits, so I may update its firmware next time I visit my mum, where it's stocked. So I'll use the older unit, whose firmware is up to date.
Pete Brown, Microsoft Senior Developer has written: "The problem appears to be that the new MIDI stack is much faster than the old one, so we're hitting conditions in apps that were not hit before. We'll get it sorted out.". So let's wait for the next KB5074105 release, let's create a restore point, then install it and let's see if averything's OK.
Hello DJ Le Chiffre,
1) I have tested a DJ Console Mk2 with KB5074105 update with no problem, it works in MIDI.
Tested on https://www.midimonitor.com/ in Chrome, with firmware 1.3.7.16 in DJ Console Mk2.
So maybe your problem with KB5074105 update for Windows 11 is related to VirtualDJ.
2) If your second DJ Console Mk2 works in audio on your computer, it needs no firmware update.
The last firmware for DJ Console Mk2 is the one ending with 16 in DJ Console Mk2 control panel.
3) Regarding DJ Console Mk2 jog-wheels sticky layer (rubber coating becomes sticky when aging), you may clean it in putting isopropyl alcohol / alcohol-based cleaning sanitizer on a washcloth and rubbing this washcloth on the jog wheels (if you value it for using it rather than as a collector).
Thank you very much for the time you spent on my issue.
1. Pete Brown is actually working directly with Virtual DJ developer and you may be right about an issue affecting specifcally that software; but this issue affected also DJay and DJuced. In addition I've installed Pocket MIDI app and it has never detected any MIDI signal while KB5074105. And Pete Brown has announced a new release version of KB5074105 planned on the 10th of Frebruary, that is to say today. So if you have performed your test today, perhaps you have enjoyed the correction made by him. Tomorrow I'll create a restoration point, then I'll install this KB again, and I'll see if the device works again or if I need to restore the previous point.
2. Both firmwares of my two MK2 are 1.3.6.15 ; thanks to your explanations, I know why they are out to date and next month I'll update you thanks to my prehistoric Compaq laptop running Win7 and DJ Console drivers v2020.HDJS.1 to reach the most recent version you're mentioning.
3. Thank you for the tip, which may be useful with many similar surfaces of other rubber devices. I value my second MK2 as a spare if, one day, my historic one decays, because of a beer pouring on it (it has survived more than one fail of this nature in the past 20 years...)
I'll let you know about the results here, let's stay connected.
Hey all.
Not sure when I said that Feb 10 would be a fix for this, as that is not in any plans. The next set of MIDI fixes goes out at the end of the month (last week: "2D" for February, 4th week) and the next set of fixes after that will be 3D.
The fix VirtualDJ put out today does fix the issue for their customers.
I'm not aware of issues with djay or djuced. Are these reported online anywhere? The Algoriddim folks haven't reported anything to us either. Also, I know that PocketMIDI works fine. Perhaps the issue uncovered by VirtualDJ hung the service and required a reboot before testing the other apps?
Pete
Microsoft
Hello Pete and thank you for posting here. The lack of other testimonies than mine here says all I guess.
Count on me to test the KB5074105 when my Win11 copy will offer it to be installed, with Pocket MIDI and the fixed version of VDJ with my legacy but so cool controller.
Regarding DJay and DJuced I hadn't digged any testimony/report out while I was struggling with my set a few hours before a 6-hour-long DJ set.
Count on me to let you know about the coming tests here, on VDJ community forum and on Discord.
Once again, thank you very much for feeling and acting very concerned, it is very much appreciated.
Hello Pete,
Thanks for your message.
I have tested Windows 11 update KB5074105 in DJUCED 6.4.1 and I have met no issue with 3 DJ different controllers (DJControl Starlight / DJControl Inpulse 500 / DJControl Inpulse T7: these 3 controllers are native MIDI compliant, they need no driver to be enumerated as USB MIDI).
