Yes, the latest versions of the driver (especially those with valid digital signatures) are reported to work on Windows 11 24H2, provided that Driver Signature Enforcement is either disabled or satisfied by the signature.
The most common culprit for Code 39 on Windows 11 is Memory Integrity. Disabling it allows legacy virtual drivers to load.
This security feature prevents unsigned or old drivers from loading to protect the system.
Windows 11 blocks unsigned kernel drivers by default. Multikey drivers are unsigned. Virtual Usb Multikey Code 39 Windows 11
Reboot. You will see “Test Mode” watermark on desktop.
Right-click your .reg configuration file and select to update your system registry.
If disabling signature enforcement works but resets after a reboot, you can put Windows 11 into a permanent testing state. Yes, the latest versions of the driver (especially
The root certificates used to sign older MultiKey releases (such as the Comodo AddTrust External CA root) expired and were untrusted by Microsoft. Windows 11 strictly rejects drivers lacking a valid cryptographic chain.
Windows 11 strictly blocks drivers that lack a digital signature from a verified certificate authority. Step-by-Step Fixes for MultiKey Code 39
Legacy automation software (CNC machines, medical analyzers, CAD/CAM from the early 2000s) often relies on physical parallel or USB dongles. When the original dongle fails (e.g., dead EEPROM) or is lost, and the vendor no longer exists, users turn to virtual emulation to keep critical systems running. The “Virtual USB” approach also allows running such software on modern laptops without physical dongles (e.g., for remote diagnostics). This security feature prevents unsigned or old drivers
with Code 39 dongle emulation on a CAD/CAM application showed:
If disabling Memory Integrity doesn't work, Windows might still be blocking the driver because it lacks a digital signature recognized by Microsoft. Hold the key and click Restart from the Power menu.