Code 37 — When a Driver Loads but Cannot Initialise
A walkthrough of the difference between loading and initialising, and the safe order of recovery steps.
Load Versus Initialise
A driver loading means its file is in memory and the operating system has called its entry point. Initialising means the driver has set up its internal state and registered with the system as ready. Code 37 sits in between — the file loaded fine, but the entry point returned an error.
The most common reason is a mismatch between the driver build and the operating system release line. A driver built for one major version may load on another but refuse to initialise.
Where to Check First
Open the driver entry in Device Manager, switch to the Driver tab, and note the version. Then visit your device maker's download page and confirm the listed driver covers your operating system release. If your release is newer than the latest published driver, that is the issue.
Sometimes the maker offers a beta or preview build for the newer release. These are usually safe to try and clear code 37 in one install.
When the Device Itself Has Changed
Hardware revisions sometimes change the device ID slightly. The current driver does not recognise the new ID and refuses to initialise. The fix is the same: a newer driver from the maker or, in some cases, a different driver branch covering the new revision.
If you are running pre-release operating system builds, expect a higher rate of code 37 messages. Drivers catch up with each release; the message usually clears with the next maker update.
Keep Reading
Related Overviews on PrintSoftDriver
Hand-picked articles that pair well with this one.
Browse More PrintSoftDriver Reads
Plain-English explainers, fix walkthroughs, and concept articles for every part of your system.