Code 39: The Driver May Be Corrupted or Missing

What causes Code 39

• The driver file links to another file that is not on the PC.
• The driver uses a Windows function that the installed version of Windows does not provide.
• Hypervisor-protected code integrity (shown in Windows Security as Memory integrity) is on and the driver is not compatible with it.
• The driver file or one of the files it needs is corrupted, or could not be read from the disk.

How to fix Code 39, safest step first

The steps follow Microsoft's recommended resolution for this code, in its order, with a reversible step first. Each one says how to put back what it changed.

1. 01

   Before you change anything: note the driver and make a restore point

   Open the device's Properties > Driver tab and write down the driver provider, date and version. Then select Start, type Create a restore point, open it, and on the System Protection tab choose Create. Microsoft notes that System Protection is not turned on by default; if Create is greyed out, choose Configure and turn it on for the system drive first.

   To undo: A restore point changes nothing by itself. To go back later, run System Restore and pick it: Microsoft says it reverts system files, the registry and installed programs, and leaves your personal files alone.

2. 02

   Reinstall the driver (Microsoft's recommended fix)

   In Device Manager, right-click the device and choose Uninstall device, confirm, then choose Action > Scan for hardware changes (or restart). Windows detects the device again and installs a driver for it. Keep the manufacturer's driver package to hand first: Windows may ask for it if it has no driver of its own.

   To undo: If Windows puts back a driver you did not want, use Roll Back Driver when it is offered, or install the driver you kept. The restore point from the first step brings back the whole driver configuration.

3. 03

   Get a driver from the hardware manufacturer

   Download the current driver for your exact model from the manufacturer's support page and install it. If Windows Security says a driver is incompatible with Memory integrity, a newer version from the manufacturer is the way to keep both.

   To undo: Roll Back Driver on the Driver tab returns to the driver you had, or apply the restore point.

Check it yourself

1. 01

   List every device with this code (Command Prompt or PowerShell)

   Available from Windows 10, version 1903. Each device is listed with its instance ID and the problem code with its name, CM_PROB_DRIVER_FAILED_LOAD. No administrator rights needed; nothing is changed.

   pnputil /enum-devices /problem 39

   cmdCopy
2. 02

   Or with PowerShell

   Device Manager shows the same code on the General tab of the device's Properties, in the Device status box.

   Get-PnpDevice | Where-Object { [int]$_.ConfigManagerErrorCode -eq 39 } |
     Format-Table Status, Class, FriendlyName, Problem

   PowerShellCopy