GPU Code 22 in Device Manager: "This Device Is Disabled" — Disabled or Dead Card? How to Re-Enable It

Key Takeaways
Code 22 means Device Manager has marked your graphics card as disabled, not that the card has failed. The card is still detected and its driver files remain installed; Windows simply skips it. Read the full status text, check for the down-arrow icon, then re-enable the device or remove and redetect it.
What Code 22 Actually Means
Open Device Manager, expand Display adapters, double-click the graphics card, and look at the Device status box on the General tab. If it reads "This device is disabled. (Code 22)", the card has been given problem code 22. In Microsoft's documentation this code is listed as CM_PROB_DISABLED, and the device node carries the status flag DNF_DISABLED, defined simply as "Indicates that the device is disabled."
That definition is worth reading literally, because it describes a state, not a fault. When a device is disabled, the Plug and Play manager skips it: it does not load the driver, and the device does not start. The driver files themselves remain on the system, which is what makes this different from uninstalling the device. The device is also still enumerated, which is what makes it different from a card Windows cannot detect at all.
Microsoft Support describes the cause in plain terms: "The device was disabled by the user in Device Manager." Its recommended fix is equally direct: "In Device Manager, click Action, and then click Enable Device. This starts the Enable Device wizard."
Code 22 is therefore not proof that the card is dead, not proof that the driver has a bug, and not proof of a hardware fault. In most situations the card itself is completely fine and has simply been switched off at the Device Manager level. The work of this guide is to find out which kind of Code 22 is on screen, because the three variants look similar and need different handling.
Three Different Code 22 Messages, Three Different Fixes
The same problem code appears with three different status texts in Microsoft's documentation, and treating them as one message is the most common mistake readers make. Copy the full status text from the General tab before doing anything else, then match it against this table.
| Variant | Status text (Microsoft documentation) | What it means | What to do |
|---|---|---|---|
| A. Disabled by the user | "This device is disabled. (Code 22)" and "Click Enable Device to enable this device." An Enable Device button is shown. | Someone with permission manually disabled the device in Device Manager. | Click Enable Device, then restart the computer and read the code again. |
| B. Device not started | "This device is not started. (Code 22)" | The device has not been disabled, but it has not entered a running state either. | Restart the computer, or use Action, then Scan for hardware changes, and read the code again. |
| C. Disabled by a driver | "This device is disabled. (Code 22)" and "You can't enable this device because it has been disabled by a Windows driver." No Enable Device button is shown. | A Windows driver has disabled the device, so there is no enable button to press. | Uninstall the device in Device Manager, then use Action, then Scan for hardware changes, so Windows detects it again. |
Variant C deserves special attention because it is the one that looks the most alarming. A reader who sees no enable button often concludes the card is dead or the system is locked, when in fact the correct path is simply uninstall followed by a hardware scan. The absence of the button is part of the message, not a sign of a deeper failure.
Disabled or Dead? Read the Icon and the Status Text
There are two quick visual checks that separate a disabled card from a faulty one, and both should be done before any fix is attempted.
First, look at the icon. A disabled device in Device Manager carries a small down arrow on its icon. It does not carry a yellow exclamation mark. The yellow exclamation mark belongs to error codes such as Code 10, Code 31, and Code 43. If the icon shows a down arrow, the device is disabled. If it shows a yellow exclamation mark, something else has gone wrong, and the Code 22 steps in this guide are not the right starting point.
Second, look at the device name. A Code 22 device still shows its normal model name, because the driver is installed and the device is enumerated. That is different from Code 28, where the driver is not installed and the device often appears as Microsoft Basic Display Adapter. A disabled card has not become an unknown device; it is a known device that has been switched off.
If the icon shows a down arrow, the name is the normal model, and the status text matches one of the three variants above, the card is disabled rather than dead. The remaining question is only which variant applies and which re-enable path it needs.
Step by Step: Re-Enabling the Card
Work through the steps for the variant identified above, and re-read the device status after every step. Do not stack several changes at once, because then it is impossible to tell which one made the difference.
Variant A: the enable button is available
Right-click the graphics card in Device Manager, or open the Action menu, and choose Enable Device. This starts the Enable Device wizard described in Microsoft's guidance. Follow it, then restart the computer and check the status text again. If Code 22 has disappeared and the card shows as working normally, the problem is solved and nothing further needs to be done. There is no need to reinstall the driver, because Code 22 was never a driver-damage problem.
Variant B: the device is not started
Restart the computer first. If the code remains, open the Action menu in Device Manager and choose Scan for hardware changes, which asks Windows to detect the hardware again. Read the status text after the scan. If the message has changed to a different code, note the new code and follow the guidance for that code instead of repeating the Code 22 steps.
Variant C: no enable button is shown
Right-click the graphics card and choose Uninstall device. When the uninstall is complete, open the Action menu and choose Scan for hardware changes. Windows will detect the card again and assign the driver. Read the status text after detection. This is the correct route for a device disabled by a driver: the uninstall clears the disabled state, and the scan brings the device back.
If the code changes after enabling
Sometimes Code 22 disappears and a different code takes its place, such as Code 31, Code 10, Code 39, or Code 43. That change is diagnostic information in its own right. It means the disabled state was only hiding the next layer of the problem, and the new code is the one that now needs attention. Record the new code and the step that produced it, then follow the guidance written for that code. Do not treat the change as an enabling failure.
If the device disables itself again after a restart
Note exactly which step the re-disabling follows. Check whether a company or school device-installation policy, or software that runs at startup, is disabling the device again. No specific program or driver can be named as the cause without evidence, so the check is directional: look at what changed around the time the code returned, and on a company machine ask the IT team before changing any policy setting. If the pattern cannot be explained from the machine's own history, the next step is a hands-on inspection rather than further guessing.
Cross-testing, where a second machine is available
If a second computer is available, the card can be fitted there and checked for the same code. If the second machine also shows Code 22, the problem follows the system setting rather than the card itself. If no second machine is available, that limitation should be stated plainly: without a second machine, a card-level fault cannot be ruled out from the desk alone, and the diagnosis stays at the level of what Device Manager reports.
Laptop Dual-Graphics Warning
Laptops with two graphics processors need extra care with disabling, because the two processors do not behave the same way when switched off.
Disabling the discrete graphics card usually means games and heavy applications fall back to the integrated graphics processor. The result is slower performance, not a blank screen, because the integrated processor is still producing the picture.
Disabling the integrated graphics processor is riskier. On some laptops the built-in screen is driven through the integrated processor, so disabling it can leave the built-in screen with no picture at all. This is why integrated graphics should not be disabled as a casual experiment. The general recovery route if the screen goes blank is to connect an external monitor, or to enter Safe Mode and re-enable the device from there. That is a general Windows recovery path, not a guarantee, and it should be attempted carefully.
Code 22 Compared with Neighbouring Codes
Code 22 is easy to confuse with nearby codes, but the differences are clear once the status text and the icon are read properly.
| Code | Meaning | How it differs from Code 22 |
|---|---|---|
| Code 45 | Windows considers the device not connected. The device cannot be enumerated, and the cause is usually a leftover entry or a connection problem. | Code 45 is a detection problem; Code 22 is a disabled state on a device that is still enumerated. |
| Code 43 | Windows has stopped the device because the device reported a problem during operation. | Code 43 is an operation-layer fault reported by the device; Code 22 is a disabled state set by a user, a driver, or a policy, with no device-reported problem involved. |
| Code 28 | The driver is not installed, so the device often appears as Microsoft Basic Display Adapter. | Code 28 is a missing-driver state; Code 22 is a disabled state on a device whose driver is already installed and whose name still shows normally. |
Don't confuse this with Code 43: a card that works briefly after being disabled and re-enabled, then fails again after a restart, is showing Code 43 behaviour. That pattern is not evidence about Code 22, and it should not be used to predict what a Code 22 card will do.
Common Misconceptions
| Misconception | What is actually true |
|---|---|
| "Code 22 means the card is dead." | Wrong. Code 22 only says the device is disabled. The card is usually fine, and enabling it may solve the problem completely. |
| "The yellow exclamation mark and the down arrow mean the same thing." | Wrong. The down arrow means disabled. The yellow exclamation mark means an error, such as Code 10, Code 31, or Code 43. |
| "No enable button means there is no fix." | Wrong. Variant C, where a driver disabled the device, has no enable button by design. The correct fix is to uninstall the device and scan for hardware changes. |
| "Reinstalling the driver will always fix Code 22." | Wrong. Code 22 is not driver damage, so reinstalling the driver does not clear the disabled state. The device must be enabled first. |
| "Windows Update disabled the card." | Wrong. Windows Update replaces drivers; it does not disable devices. A problem that appears at the same time as an update is not necessarily caused by the update. |
| "A disabled card has disappeared." | Wrong. A disabled device is still enumerated and still listed in Device Manager. A card Windows cannot detect at all is a different problem. |
Disabling a device should also not be treated as a performance or power-saving technique. It does not fix driver conflicts; it only hides the problem from view while leaving the underlying cause in place. Devices that are not in use are best left enabled unless there is a specific, documented reason to disable them.
Before Bringing the Card In: A Short Checklist
If the steps above do not clear the code, gather the following before seeking a hands-on inspection, so the inspection can start from facts rather than from scratch:
- The exact status text from the General tab, and which of the three variants it matches.
- Whether the icon shows a down arrow or a yellow exclamation mark.
- When the code first appeared, and what was done just before it appeared, such as a manual disable, a driver change, or a policy change.
- Whether the code changed to a different code after enabling, and which code it changed to.
- Whether the machine is a desktop or a laptop, and whether it has dual graphics.
- The Windows version and the installed driver version.
Repairs are charged on the site's published three tiers, from HK$400 to HK$2,800, with the final quote confirmed after inspection. The workshop is at Room 1209, Dali Plaza, Shek Mun. The phone number is 2186 8010, and WhatsApp is 6558 6806. There is no Mong Kok shop and no on-site service.
Frequently Asked Questions
What does Code 22 mean on a graphics card?
It means Device Manager has marked the device as disabled. The device node carries the flag DNF_DISABLED, the Plug and Play manager skips it, and the driver is not loaded. The card is still detected and the driver files remain installed.
How do I re-enable a graphics card showing Code 22?
Open Device Manager, find the card under Display adapters, and choose Enable Device from the Action menu or the right-click menu, then restart the computer. If no enable button is shown, the device was disabled by a driver: uninstall the device, then choose Scan for hardware changes from the Action menu so Windows detects it again.
Why is there no Enable Device button for my card?
Because the device was disabled by a Windows driver rather than by a user. That variant of Code 22 has no enable button by design. The documented fix is to uninstall the device and scan for hardware changes, not to keep looking for a button.
Does Code 22 mean my graphics card is broken?
No. Code 22 is a state, not a diagnosis of hardware failure. The card is usually working normally and has simply been switched off. Only if enabling fails, or the code changes to a fault code such as Code 43, does the investigation move towards hardware.
What is the difference between Code 22 and Code 43?
Code 22 means the device is disabled by a user, a driver, or a policy, with no device-reported problem involved. Code 43 means Windows stopped the device because the device reported a problem while running. The two codes have different icons, different causes, and different fixes.
Should I reinstall the driver to fix Code 22?
Not as a first step. Code 22 is not driver damage, so a driver reinstall does not clear the disabled state. Enable the device first. Only if the code changes to a driver-related code after enabling does a driver reinstall become the relevant next step.