Fix: Windows Code 32 error message

If you have received a Windows ‘ode 32 Error with the following line as description while running your system – A driver (service) for this device has been disabled. An alternate driver may be providing this functionality, then this post may interest you. This error is associated with corrupt drivers, services or registry keys.

Some of the commonly known causes of Code 32 error are:

1. The driver is corrupted
2. The device is not up-to-date
3. The device is not configured as default
4. A previous attempt to update the driver failed unexpectedly or was interrupted
5. A required service associated with the device driver is disabled
6. A different device is providing default functionality.

Windows Code 32 error

Identifying the exact cause may require extensive troubleshooting of all software components if, caused by the erroneous drivers. The widely recommended solution for this error message is to reinstall the driver for the device – the first level of repair that you should attempt. Also, always keep your device drivers up-to-date.

Uninstalling and Re-installing the driver

• In Device Manager choose the device and pick the option to uninstall or remove the device.

• Click on Action and then scan for new hardware.

• If the new hardware scan did not work, go to the Control Panel.
• Choose Add/Remove Hardware and add a new device.
• Windows should auto-detect the device and begin the reinstall.
• Follow all prompts for the reinstall process

If prompted for the driver location and you can’t recall, go to the vendor’s website & download the latest version of the driver from there.

If the problem still persists, there may be a registry problem that needs to be addressed then. You may have to change driver start values. Fixing a registry error is a job of a computer veteran; serious problems can occur if you modify the registry incorrectly. Therefore, make sure that you back up the registry first and create a system restore point and then  follow the steps carefully.

Changing Driver Start Values via Registry Editor

Open Registry editor and navigate manually to the following registry path-

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

Once there, look for the drivers giving the problem. If found, change the start value from 3 to 1.  for example, If your USB mass storage is not working and displaying the code 32 error every time, open the USBSTOR and change the start value from 3(0×00000003) to 1(0×00000001).

That’s It!

Hope something helps!