Code 31 with the message "the requested operation was unsuccessful" means Windows recognizes the device but cannot start the driver that binds to it, and the most common cause is a mismatch between the driver's digital signature or installation state and what Windows expects. It is not the same as Code 10 or Code 43, and treating all three as one error is why so many fixes fail. The number in the message is what matters: 31 points at the load stage, where the driver package or its registry entry is broken, blocked, or duplicated.
What Operation Failed Code 31 Specifically Reports Inside Device Manager
Device Manager assigns Code 31 when the driver's installation state cannot be validated at start time, so the device hardware can be perfectly healthy and still show the yellow warning triangle. Code 31 is categorized as a driver load failure, which separates it from Code 10 ("device cannot start") and Code 43 ("Windows has stopped this device"). Microsoft documents the Code 31 message set across supported Windows versions, and the wording "the requested operation was unsuccessful" is the standard string attached to it. What the reader needs to hold onto is this: the device is present in the hardware tree, the driver entry exists, and the handoff between them failed. That gap is where every repair lives.
The failure surfaces in Device Manager under the device's Properties dialog, on the General tab, in the Device status box. The exact text reads "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)" followed by the operation-failed phrase. On Windows 11 the same message appears, sometimes with the additional line "The specified request is not a valid operation for the target device." That second line is the useful clue β it usually means a filter driver, a stale upper or lower filter registry value, or a ghosted duplicate device is intercepting the load.
A working example: an Intel Wi-Fi adapter that functioned for months starts showing Code 31 after a Windows cumulative update. The hardware is fine, the network is fine, and reinstalling the app does nothing. What changed is the driver's signature validation path, and the fix lives in the driver package, not in the app or the network settings. Recognizing that pattern saves hours.
Windows version matters less than most guides suggest. The Code 31 vocabulary is consistent from Windows 7 through Windows 11 because the underlying Plug and Play manager has handled driver load failures the same way for years. What changes is the recovery tooling β Windows 11's Settings app offers fewer driver rollback paths than the old Control Panel, and the "Update driver" automated search now prefers Windows Update over manufacturer catalogs. That single shift causes a large share of unresolved Code 31 cases, because Windows Update often returns a generic driver that does not match the specific hardware revision.
The Four Real Causes Behind the Operation-Failed Message, Ranked by How Often They Occur
The largest share of Code 31 cases come from a corrupted or partial driver installation, usually after an interrupted update, a failed rollback, or a forced shutdown during installation. The device entry registers, but the binary files or their registry configuration never finished writing. Cyclic redundancy errors during a Windows Update install produce this exact profile. If the failure appeared right after an update, treat corruption as the leading candidate before anything else.
The second most common cause is a duplicate or ghosted device entry. Windows keeps hidden entries for hardware that has been physically disconnected, and when the device returns on a different port or slot, the old entry can conflict with the new one. This shows up frequently on USB devices moved between ports and on laptops whose docking station was swapped. The "specified request is not a valid operation" line in the error is a strong tell here.
Third is the digital signature problem. Windows requires kernel-mode drivers to carry a valid signature from a trusted publisher, and Windows 10 and 11 in default configuration will refuse to load a driver whose certificate has been revoked, expired, or was issued by a test-signing channel. According to Microsoft's driver signing documentation, the kernel-mode code signing policy has been enforced since Windows Vista x64 and tightened in later releases. An unsigned or cross-signed legacy driver that worked on an older build will produce Code 31 on a current one.
Fourth, and least often, is a genuine hardware or firmware fault. A device that fails its own power-on self-check or reports malformed descriptors to the bus can trigger a load failure before the driver is even consulted. This is the case where no amount of driver swapping helps, and it is why the diagnostic order matters: rule out software before you replace hardware.
Run the Five-Step Repair Sequence Before You Reinstall Windows
Work through these in order. Each step targets a different layer, and stopping at the first success avoids unnecessary changes. Expect the whole sequence to take 20 to 40 minutes on a typical machine, with the restart steps consuming most of that time.
1: Open Device Manager (Win+X, then Device Manager), expand the affected category, right-click the device, and choose Uninstall device. If a "Delete the driver software for this device" checkbox appears, tick it. Restart the PC and let Windows re-enumerate the hardware. 2: Open an elevated Command Prompt (search "cmd", right-click, Run as administrator) and run sfc /scannow. When it finishes, run DISM /Online /Cleanup-Image /RestoreHealth. Both commands repair the system image and component store that driver packages depend on. 3: In Device Manager, click View, then Show hidden devices. Look for greyed-out duplicates of the affected device and uninstall every one of them. Restart. 4: Return to the device's Properties, open the Driver tab, and use Roll Back Driver if the button is active. If it is greyed out, proceed to step 5. 5: Download the current driver directly from the hardware manufacturer's support page β Intel, AMD, NVIDIA, Realtek, Broadcom, or the laptop maker β and install it manually rather than accepting Windows Update's suggested package.
If the device still fails after step 5, open the device's Properties, go to the Details tab, select "Hardware Ids" from the dropdown, and note the VEN and DEV codes. Search those codes on the manufacturer's site to confirm you have the right driver for that exact revision. A driver matching the model name but not the hardware ID is the single most common reason a manual install produces another Code 31.
Driver Signature Enforcement Is the Cause Most Guides Skip
Microsoft's kernel-mode code signing requirements mean a driver without a valid, trusted signature will not load on a 64-bit Windows system in its default configuration. The enforcement isn't new β it dates to the Vista x64 era β but it bites hardest on older peripherals and on hardware pulled from industrial or point-of-sale environments where cross-signed drivers were standard practice. If the device is a serial adapter, a label printer, a barcode scanner, or a legacy capture card, signature rejection should be your first hypothesis, not your last.
You can confirm it by checking the device's driver details. In Device Manager, open Properties, go to the Driver tab, and click Driver Details. A signed driver lists a digital signer. A rejected one may show an error in Event Viewer under Windows Logs, System, filtered to source "CodeIntegrity." Those events name the file that failed validation, which turns a guessing game into a targeted fix.
The remedy is a current signed driver from the manufacturer. If none exists, some vendors publish a signed update for their legacy line precisely because of this enforcement, and it's worth checking the vendor's support page before concluding the hardware is unsupported. The alternative β disabling driver signature enforcement through the advanced startup menu β is a temporary diagnostic measure only. It resets on reboot, weakens the machine's security posture, and does not fix the underlying problem. Use it to confirm the diagnosis, then go get the signed driver.
For anyone maintaining fleets, the practical rule is to inventory any device older than roughly 2015 before a Windows feature update, because that's where signature-related Code 31 failures cluster.
Filter Drivers in the Registry Explain the "Specified Request Is Not a Valid Operation" Line
Upper and lower filter drivers sit between the device stack and the function driver, and a stale filter entry will cause a load failure that no amount of driver reinstalling resolves. This is the specific scenario behind the "specified request is not a valid operation for the target device" message. Common culprits are leftover entries from uninstalled backup software, antivirus suites, disk encryption tools, and virtual drive mappers.
The repair happens in the registry, so back it up first (File, Export in Registry Editor). Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class and locate the class GUID for the affected device type β for example, {4d36e972-e325-11ce-bfc1-08002be10318} covers network adapters. Inside, find the subkey matching your device's instance and inspect the UpperFilters and LowerFilters values. A multi-string value naming software you no longer have installed is your problem.
Remove the orphaned entry, restart, and check Device Manager. If the device starts, reinstall the current version of the software that owned the filter, or leave it out entirely if you no longer need it. Be conservative: only remove values you can tie to uninstalled software, because deleting a filter that a currently installed security product depends on can leave the machine unbootable. If you're unsure, create a System Restore point before touching the registry β Windows creates one automatically during driver installs, but an extra manual point costs nothing and takes about a minute.
Comparing the Actual Fix Methods on Risk, Time, and Success Rate
Four approaches cover nearly every Code 31 case, and they differ sharply in how much time they take and how much they can break. The table below reflects the sequence above and the trade-offs behind it.
| Method | Typical time | Risk level | Best for | Main limitation |
|---|---|---|---|---|
| Uninstall and re-enumerate | 5β10 min | Low | Recently corrupted driver | Fails on ghosted duplicates |
| SFC and DISM repair | 15β30 min | Low | Post-update corruption | Does not touch third-party drivers |
| Manual OEM driver install | 10β20 min | Medium | Signature and version mismatch | Wrong package if hardware ID not matched |
| Registry filter cleanup | 10β15 min plus restart | High | "Invalid operation" message | Editing wrong key can break boot |
The ordering is deliberate. The low-risk steps come first because they resolve the majority of cases, and the registry work sits last because it carries the only real chance of making things worse. A user with a Code 31 network adapter after a Windows update will usually be finished by row two. A user with a Code 31 on a ten-year-old label printer will usually need row three. A user seeing the "invalid operation" line with no other symptoms needs row four.
The one method this table deliberately excludes is a full Windows reinstall. It's the most expensive option in both time and data risk, and it's almost never necessary for Code 31 specifically, because the failure is isolated to one device's driver stack rather than the operating system as a whole. Save it for the case where multiple unrelated devices fail simultaneously, which points at a deeper system problem.
Checking Hardware IDs and Compatibility Before You Install Anything
The Details tab in Device Manager is the most underused diagnostic in Windows. Under the Property dropdown, "Hardware Ids" returns strings like PCI\VEN_8086&DEV_24FD&SUBSYS_00108086&REV_78. The VEN value is the vendor, the DEV value is the device, and the SUBSYS value identifies the exact board revision. Matching all three against the manufacturer's driver download page eliminates the guesswork that produces repeat Code 31 failures.
Do this before downloading, not after. Manufacturers publish driver packages for product families, and a package for the right family can still be the wrong revision if the SUBSYS differs. On laptops, the OEM driver is usually the correct one even when the chip maker publishes a newer generic version, because laptop vendors modify power management and thermal profiles inside their driver packages. Going straight to Intel or AMD for a laptop's graphics driver is a frequent source of trouble, and it's worth checking the laptop maker's support page first.
For USB devices, check the device's power requirements as well. A device that draws more current than the port can supply may fail enumeration intermittently, and the resulting error can present as Code 31 on reconnect. Testing on a powered hub or a rear-panel port resolves this. It's a fast check and it rules out a cause that driver work will never fix.
When the Device Itself Is Failing and No Driver Will Help
Some Code 31 cases are hardware. A device that reports malformed descriptors, fails its power-on self-check, or behaves differently across two machines has a fault the operating system cannot repair. The decisive test is to move the device to a different computer and see whether the same error follows it. If it does, stop working on drivers.
The second decisive test is safe mode. Boot into safe mode (hold Shift while selecting Restart, then Troubleshoot, Advanced options, Startup Settings) and check whether the device starts there. If it does, a third-party driver or service is interfering in normal mode, and the filter-driver section above is your path. If it fails in safe mode too, the fault is at the hardware or firmware layer.
Laptops with soldered components complicate this, because "moving the device" isn't possible. For an integrated Wi-Fi card or an onboard audio chip, the substitute test is a live Linux boot from a USB stick. If the device works there, the hardware is fine and Windows is the problem. If it doesn't, you're looking at a board-level issue and a warranty or repair decision.
Firmware updates from the manufacturer sometimes resolve these cases, particularly on docking stations and USB-C hubs, where the firmware handles enumeration before Windows sees the device. Check the manufacturer's support page for a firmware utility, and apply it only from a stable power source.
Stopping Code 31 From Coming Back After Updates
Prevention focuses on three behaviors. First, pause driver updates through Windows Update when a machine is stable, using Settings, Windows Update, Advanced options, and the pause control β this stops the automatic substitution of a generic driver for a working OEM one. Second, keep a copy of the current working driver for any device that has failed before, so a repeat incident takes minutes instead of hours.
Third, avoid third-party "driver updater" utilities. They frequently install unsigned or mismatched packages, and the resulting Code 31 is harder to diagnose than the original problem because the utility has changed several drivers at once. If a machine arrives with one of these tools installed, removing it and restoring the OEM drivers is worth the time.
For managed environments, Microsoft's documentation on driver package management and the Windows Hardware Compatibility Program provide the supported path for validating drivers before deployment. The compatibility program listing tells you whether a specific driver has been tested against a given Windows release, which is more reliable than a vendor's marketing page.
FAQ
Is Code 31 the same as Code 10 or Code 43?
No, and the distinction changes the fix. Code 31 means the driver failed to load; Code 10 means the device could not start; Code 43 means Windows stopped the device after a reported failure. Code 31 lives in the driver installation layer, which is why reinstalling or re-signing the driver resolves it, while Code 43 often points at hardware.
Can a Code 31 device damage my computer if I keep using it?
Not directly. The device isn't running, so it can't fail mid-operation. The risk is indirect: an unresolved driver failure leaves a partially installed package behind, and repeated failed installs can accumulate conflicting entries. Clearing the device entry and starting fresh is cleaner than repeatedly retrying the same install.
Why does my device work in safe mode but show Code 31 in normal mode?
That pattern means a third-party driver or service is interfering with the load. Check the UpperFilters and LowerFilters registry values for the device class, and look at CodeIntegrity events in Event Viewer. The conflicting software is usually a security suite, backup tool, or virtual drive utility, and updating or removing it resolves the conflict.
Does disabling driver signature enforcement permanently fix Code 31?
No. The setting reverts on the next restart, and leaving it permanently disabled weakens the machine's protection against malicious kernel drivers. Use it only to confirm that signature validation is the cause, then obtain a signed driver from the manufacturer. A test-signed driver is a diagnostic result, not a solution.
How long should a driver reinstall take before I give up?
Allow 10 to 20 minutes for a manual OEM install including the restart, and up to 40 minutes for the full sequence with system file repair. If two clean installs of the correct hardware-ID-matched driver both fail, stop reinstalling and test the device on another machine. Repeating the same install rarely changes the outcome.
Will a Windows reset fix Code 31?
A reset keeps or removes files depending on the option chosen, and it removes installed applications and drivers. It resolves Code 31 only when the cause was system-wide corruption, which is the minority of cases. Try the five-step sequence first; a reset is a last resort behind hardware testing, not ahead of it.
Can a docking station cause Code 31 on a laptop?
Yes. Docking stations and USB-C hubs run their own firmware for enumeration, and outdated firmware can present devices to Windows in a state the driver rejects. Updating the dock's firmware from the manufacturer's support page, then reconnecting, resolves this scenario more often than driver changes on the laptop.
What if the manufacturer no longer publishes a driver for my device?
Check the Windows Update Catalog, which retains older signed packages for many devices, and verify the package matches your hardware ID before installing. If no signed driver exists, the device has reached end of support for current Windows versions. Replacing it is usually cheaper than maintaining workarounds.