Windows HDR Toggle Missing and Games Say HDR Is Not Supported? HDR Capability Detection, EDID Reporting & Three-Layer Switch Diagnosis Guide

2026-11-14 | GPU Repair | 39 minutes | HK GPU Fix Editorial Team

Windows HDR Toggle Missing and Games Say HDR Is Not Supported? HDR Capability Detection, EDID Reporting & Three-Layer Switch Diagnosis Guide

Key Summary

A missing HDR switch means one link in Windows' capability-detection chain has not been established, not that the graphics card has failed. Read the Display capabilities listing and dxdiag first, then test the monitor's menu, cable and port, driver, and monitor in order, re-reading capability after each change.

The Opposite Direction: Cannot Enable, Not Enabled But Wrong

This guide deals with the opposite direction from the companion guide on HDR picture problems after HDR is already on. That companion guide starts from a position where HDR is enabled and the picture looks wrong — washed out, tinted, too dark, or badly mapped. This guide starts from a position where HDR cannot be enabled at all: the switch is missing, greyed out, or the capability listing says "Not supported", or Windows HDR is on but a game still reports that the display does not support HDR.

The distinction matters because the remedies point in opposite directions. When HDR is on and the picture is wrong, the work is picture adjustment. When HDR cannot be turned on, the work is capability detection, and picture adjustment cannot help — there is no HDR picture to adjust yet. A reader who applies picture-adjustment advice to a missing switch will spend an evening changing settings that have no bearing on whether the switch appears.

The core claim of this guide is simple: "Not supported" is not a verdict on the monitor. It is a statement about a detection chain at this moment, in this combination of monitor, cable, port, and driver. The chain has four links, and the switch appears only when all four hold. The task is to find which link has not held, by reading what Windows itself reports, and then to test that link directly — not to reinstall the driver first, and not to conclude that the monitor is fake.

This guide covers Windows 10 and Windows 11 desktop computers where the monitor is labelled as HDR-capable, or the user believes it is, but the HDR switch cannot be found in Windows Settings, the Display capabilities listing says "Not supported", or a game reports that the display does not support HDR, while the ordinary SDR picture itself is normal. A normal SDR picture is itself useful evidence: it shows that basic output from the graphics card to the monitor is working, and the fault is confined to the HDR capability chain that sits on top of it.

What HDR Capability Detection Actually Is

Windows does not decide whether to show an HDR switch by feeling, or by reading the marketing label on the monitor's box. It runs a capability-detection chain, and the switch appears only when every link in that chain is established. Understanding the chain is the whole diagnosis, because each link has a different test and a different remedy, and a remedy aimed at the wrong link changes nothing.

The chain has four links. First, the monitor must report its HDR capability in its EDID — the block of data a display sends to the computer describing what it can do. That report is not a single sentence saying "I support HDR". It is a set of specific data: support for HDR10, the BT.2020 colour gamut, the ST.2084 electro-optical transfer function (the PQ curve), and peak brightness information. Second, that report must travel intact through the cable, the port, and any adapter, switch, or dock in between, and reach the graphics card. Third, the graphics driver must read the report and tell Windows that advanced colour is supported. Fourth, Windows must list the capability as supported in Settings, and only then does it show the switch.

If any one link fails, the switch does not appear, and Windows does not say which link failed. It simply says "Not supported". That silence is the defining feature of the problem. The user sees only the absence of a switch, and has to work out which link failed by testing them in order.

Two consequences follow immediately. First, a monitor can be genuinely HDR-capable and still produce no switch, if its report never reaches Windows intact. Second, a monitor can produce no switch because it genuinely has no HDR capability to report, and no amount of cable changing or driver updating will create one. Both outcomes look identical at first — no switch — and only the diagnostic steps in this guide separate them.

The Capability Chain, Link by Link

Link one: the monitor reports HDR in its EDID

EDID is the display's self-description. When a monitor is connected, it sends EDID to the computer over the DDC channel, a low-speed communication channel that runs alongside the video signal. The video channel carries the picture; the DDC channel carries the description of what the monitor can do. The two channels can fail independently: a picture can be perfect while the description is incomplete or never arrives, and that independence is the key to this whole problem.

For HDR, the relevant part of the description is the HDR10 static metadata: support for HDR10, the BT.2020 colour gamut, and the ST.2084 EOTF. Microsoft's own dxdiag readings look for exactly these items. A display counts as an HDR10 display for Windows when the monitor capabilities include HDR support together with BT2020RGB or BT2020YCC and Eotf2084Supported. If those items are absent from the report Windows receives, Windows has no basis for offering an HDR switch, whatever the box says.

The report can be absent for two different reasons, and the distinction decides the whole diagnosis. Either the monitor never sent the report, because its HDR function is switched off in its own on-screen display (OSD) menu, or because the monitor genuinely has no HDR capability to report; or the monitor sent the report and something between the monitor and the computer lost it. The first reason is tested in the OSD step. The second is tested in the direct-connection step. Neither can be settled by looking at the box.

Link two: the cable, port, and anything in between carry the report

The report must travel from the monitor to the graphics card through the cable and the port, and through any adapter, switch, dock, or hub in between. An adapter or switch that sits in the middle can fail to pass the HDR report along, or can substitute a simplified EDID of its own in place of the monitor's real one. In either case Windows receives a description that says nothing about HDR, and the switch does not appear — even though the monitor itself is capable and the picture is fine.

This is why a cable that works perfectly for SDR can still be the cause of a missing HDR switch. SDR does not need an HDR report, so a cable that carries the picture correctly can still fail to carry the HDR capability report. The test for this link is a direct-connection comparison: remove everything in between, connect the graphics card directly to the monitor with a different known-good cable, and try another port. Each change is made one at a time, and the capability reading is re-checked after each change, so that it is clear which change made the difference.

Microsoft's guidance for an external HDR display lists DisplayPort 1.4 or HDMI 2.0 or above, or USB-C or Thunderbolt, as the connection requirement. Those are minimums for the connection, not a guarantee: meeting the minimum does not prove the cable in hand is carrying the report, and the direct-connection comparison is still the test that settles it.

Link three: the driver reads the report and reports it to Windows

The graphics driver must be able to read the monitor's HDR report and tell Windows that advanced colour is supported. A generic driver — the Microsoft Basic Display Adapter that Windows falls back to when no proper graphics driver is installed — or an outdated driver may not read the report or may not report it onwards, and Windows will then treat the display as not supporting HDR.

This link is the reason driver updating appears in so many generic guides, and also the reason it must not be the first step here. The driver is the third link in the chain, not the first. If the OSD has HDR switched off, or the cable is not carrying the report, updating the driver changes nothing, because there is still no report for the driver to read. The driver check belongs after the OSD check and the direct-connection check, and it is a comparison — confirming the driver identity in Device Manager, updating to the manufacturer's latest stable driver, or rolling back if the problem began immediately after a driver update — not a blind reinstall.

Link four: Windows lists the capability and shows the switch

Only when the first three links hold does Windows list the capability as supported in Settings, and only then does it show the HDR switch. The listing itself is the first diagnostic reading in this guide, and it is described in detail in the next section. Two capabilities are listed separately — "Play HDR games and apps" and "Stream HDR video" — and the two can disagree: one can be supported while the other is not. That split is information, not a contradiction, and it points at a partial capability rather than a broken chain.

Windows 10 and Windows 11 name the page differently, and the names must not be confused. Windows 10 calls it "Windows HD Color settings", with "Play HDR games and apps" and "Stream HDR video" as two separate switches. Windows 11 calls it the HDR page, with the two combined under a single "Use HDR" switch. The logic is the same in both versions; only the layout differs. A reader following instructions written for one version on the other version will search for a label that does not exist on that machine, and may conclude wrongly that the feature has been removed.

The Two Readings That Decide Everything: Display Capabilities and dxdiag

The most important diagnostic tools in this guide are two readings Windows itself provides. They must be read and written down before anything is changed, because they are the baseline against which every later change is judged. A reader who changes cables and drivers without first recording these readings cannot tell afterwards whether any change made a difference.

Reading one: Display capabilities in Settings

Go to Settings, then System, then Display, then HDR — and first select the correct display at the top of the Display page if more than one display is connected. HDR settings are per display, so reading the capabilities of the wrong display proves nothing about the display that is actually in question. On a multi-display system, this selection step is not optional.

On the HDR page, Windows lists Display capabilities. Two items matter here: "Play HDR games and apps" and "Stream HDR video". Each is listed as Supported or Not supported. Write down both, exactly as shown, before changing anything.

The reading splits the problem at once. If both items say "Not supported", the investigation follows the capability chain in the next sections. If one says Supported and the other says Not supported, the chain is not wholly broken — the display has a partial capability, and the split itself is the finding. Microsoft's own documentation states plainly that the two are listed separately and can disagree, so a split reading should not be treated as an error in the listing or as evidence that the whole display is faulty.

Reading two: dxdiag — the tutorial

The second reading comes from dxdiag, the DirectX diagnostic tool built into Windows. It is the deeper of the two readings, because it shows what the driver is actually reporting to Windows, rather than what the Settings page has chosen to display. The steps are:

  1. Press Win + R to open the Run box.
  2. Type `dxdiag` and press Enter.
  3. Wait for the tool to finish gathering information. If a prompt asks whether to check for digitally signed drivers, either answer is acceptable for this purpose; the readings below do not depend on it.
  4. Click "Save All Information" and save the text file, or read the values directly from the Display tab. Saving the file is the better habit, because it preserves the exact wording for comparison later.
  5. In the saved file, or on the Display tab, find the following three values and write them down exactly.

The three values are:

The honest point about these readings must be stated plainly, because it is the point most often missed. "HDR Not Supported" in dxdiag describes the current combination — this monitor, this cable, this port, this driver — not the monitor itself. After changing the cable, changing the port, or switching HDR on in the monitor's OSD, the readings must be taken again. A reading taken before those changes cannot be used to declare that the monitor has no HDR capability. Only a reading taken after the OSD, cable, and driver checks, and confirmed by the cross-check in step six, can support that conclusion.

Keep the saved dxdiag file. If the machine later needs inspection, that file — together with the Display capabilities reading, the monitor model, the cable type, and the port used — is the record that lets an inspection start at the right link instead of repeating the whole sequence.

The Five Layers of Suspicion

Once the two readings have been taken, the fault can be placed in one of five layers. Each layer has its own decisive test, and the order matters: the layers are arranged from the easiest to check to the deepest, so that the driver is reached after the monitor's own settings and the cable, not before them.

LayerWhat it coversDecisive test
1. Wrong-display layerThe wrong display was selected in a multi-display setup, or a laptop's built-in screen and external monitor are bound together in duplicate modeSelect each display in turn at the top of the Display settings page and confirm which display is being read; on a laptop, cancel duplicate display and use Extend instead
2. OSD layerHDR is switched off in the monitor's own on-screen display menu, or a TV's HDMI port has not had its enhanced format switched onSwitch HDR or HDR mode on in the OSD; on a TV, switch on the enhanced format for the HDMI port in use, then re-read the capability
3. Cable and port layerAn old cable, an old port, or an adapter, switch, or dock has consumed the HDR report, or the wrong port was usedDirect-connection comparison: remove everything in between, connect the graphics card directly to the monitor, try a different known-good cable, and try another port
4. Driver and Windows layerA generic driver, an outdated driver, a driver update that changed behaviour, the Windows version, or a laptop battery policy switching HDR off while on battery powerConfirm the driver identity in Device Manager; update to the manufacturer's latest stable driver, or roll back if the problem began after an update; on a laptop, plug in mains power and test again
5. Monitor itself layerThe monitor genuinely does not support HDR10, or its EDID data is damaged, or its firmware is reporting incorrectlyCross-check: connect the same monitor to another computer, or connect the same computer to a different monitor known to support HDR; check the manufacturer's specifications

The order is itself the diagnosis. A reader who jumps straight to layer four and reinstalls the driver has skipped two layers that have nothing to do with the driver, and will usually find the switch still missing afterwards, with the same silence and no new information. A reader who works through the layers in order will either find the fault early or arrive at layer five with four layers already ruled out, which is a far stronger position — including the honest possibility that the monitor itself does not support HDR.

Layer one: the wrong display

In a multi-display setup, a common early mistake is reading the capabilities of the wrong display. Windows shows HDR settings per display, and the display selected at the top of the Display page decides which display the HDR page describes. A reader who has an HDR-capable external monitor and a non-HDR laptop screen, and who reads the laptop screen's capabilities, will conclude that HDR is not supported — correctly, for that screen, and irrelevantly for the monitor in question.

The test is to select each display in turn and read its capabilities separately. On a laptop, there is a related trap: duplicate display mode binds the built-in screen and the external monitor together, and the duplicated output can block HDR on the external display. Cancelling duplicate display and switching to Extend separates the two displays so that each can be judged on its own. This is a setting change, not a hardware fault, and it costs nothing to test.

Layer two: the monitor's own HDR switch

A monitor's HDR function is not always on by default. Many monitors have an HDR setting in their own OSD menu — the menu operated by the buttons on the monitor itself — and Windows cannot offer an HDR switch while the monitor's own HDR is switched off, because the monitor is not reporting HDR capability while its own HDR is off. The OSD setting may be called HDR, HDR Mode, or a similar name, and its location varies by brand; the monitor's manual is the authority for where it sits.

For a TV connected to a PC, the equivalent setting is the HDMI port's enhanced format. TV manufacturers give it different names — Input Signal Plus and Enhanced format are two of them — and it must be switched on for the HDMI port actually in use. A TV whose enhanced format is off for that port will not report HDR capability to the computer, and the Windows switch will not appear. The brand-specific name should be checked against the TV's manual rather than assumed.

The decisive point about this layer is the re-read. After switching HDR on in the OSD, or the enhanced format on for the TV port, go back to the Display capabilities reading and the dxdiag reading and take them again. If the readings change, this layer was the cause, and the diagnosis is finished. If the readings do not change, the cause lies in a deeper layer, and the investigation continues. A change that is not verified by a re-read is a guess, not a finding.

Layer three: cable, port, adapter, switch, and dock

This layer covers everything between the graphics card and the monitor. An old cable, an old port, or an adapter, switch, or dock in the middle can consume the HDR report while still carrying a perfect SDR picture. The decisive test is the direct-connection comparison: remove every device in between, connect the graphics card directly to the monitor, try a different known-good cable, and try another port on the graphics card and on the monitor.

Three rules govern this test. First, change only one thing at a time — cable, then port, then removing the adapter — and re-read the capability after each change. Changing everything at once and finding the switch appear proves that something in the chain was responsible, but it does not identify which item it was, and the problem will return the next time that item is used. Second, use a cable known to be good, not merely a cable that is new or expensive: price is not a test. Third, meet the minimum connection standard — DisplayPort 1.4 or HDMI 2.0 or above, or USB-C or Thunderbolt — and remember that meeting the minimum is a precondition, not a proof that the particular cable in hand is carrying the report.

A further note belongs here. Some docks and switches substitute a simplified EDID of their own for the monitor's real one. When that happens, Windows receives a description that says nothing about HDR, and no cable change downstream of the dock will fix it, because the dock itself is the source of the wrong description. Removing the dock from the chain is the test that reveals it.

Layer four: driver and Windows

The driver check has two parts: identity and version. First, confirm the driver identity in Device Manager. If the display adapter is listed as the Microsoft Basic Display Adapter, Windows is using a generic driver, and the graphics card's proper driver is not installed. A generic driver may not read or report HDR capability at all, and the remedy is to install the manufacturer's driver, not to keep testing cables.

Second, consider the driver version. An outdated driver may not support the HDR reporting path for a newer display. Updating to the manufacturer's latest stable driver is a legitimate comparison — but it is a comparison, made after the OSD and cable checks, and it must not be presented as a guaranteed fix. If the monitor itself has no HDR report to give, no driver update will create a switch, and repeating the update will not change that. Conversely, if the HDR switch disappeared immediately after a driver update, rolling back to the previous driver version is a legitimate comparison in the other direction: the update may have changed how the driver reads or reports the capability, and the rollback tests exactly that.

Laptop users should also check the power state. Microsoft's own documentation states that HDR can be switched off while a laptop is running on battery power. A laptop that shows no HDR switch on battery may show one when plugged into mains power. This is a power policy, not a hardware fault, and the test is simply to plug in and re-read the capability.

Two matters in this layer must be recorded honestly rather than stated as absolute rules, because the sources do not agree. First, some third-party guides suggest that switching off Night light can bring the HDR option back, but Microsoft's own documentation and other sources do not state this. That suggestion is an unverified third-party claim, and this guide does not present it as a fact or as a step. Second, different sources give different minimum WDDM versions for HDR — one gives WDDM 2.4, another gives WDDM 2.7 for a newer Windows 10 build — and the two numbers correspond to different Windows versions. No single WDDM number is stated here as a hard requirement; the requirement varies with the Windows version, and Microsoft's documentation for the version actually installed is the authority.

Layer five: the monitor itself

If the OSD is on, the connection is direct and known-good, the driver is the manufacturer's current stable version, and the capability readings still say "Not supported", the investigation reaches the monitor itself. Two possibilities remain: the monitor genuinely does not support HDR10, or its EDID data is damaged or its firmware is reporting incorrectly.

The decisive test is the cross-check. Connect the same monitor to a different computer that is known to offer HDR on another display, and read the capability there. Or connect the same computer to a different monitor that is known to support HDR, and read the capability there. If the monitor reports "Not supported" on every computer, the fault points at the monitor. If the computer reports "Not supported" on every monitor, the fault points at the computer, its cable, or its driver. If the monitor is recognised as HDR-capable on the other computer, the fault is on the original computer's side, and the earlier layers must be re-checked there.

The manufacturer's specifications should also be checked — but checked, not assumed from the box. A box label saying "HDR" can mean that the panel accepts an HDR signal, which is not the same as the monitor reporting a complete HDR10 capability set in its EDID. If the specifications confirm that the model has no HDR10 support, the honest conclusion is that the monitor does not support HDR, and that is not a fault: it is the product's specification, and no further cable or driver change will alter it.

When a Game Says HDR Is Not Supported

Windows HDR being on and a game still reporting that the display does not support HDR is not a second, separate problem. It is the same chain with a second exit point: the game asks Windows, through DXGI, what HDR capability the display has, and the game believes what Windows answers. The diagnosis therefore starts by returning to Windows, not by changing the game's settings.

There are three branches. First, Windows HDR may not actually be on — the game is reading an SDR state, because the Windows switch was never enabled, or was enabled for a different display. Confirm the Windows switch first, on the correct display, before touching the game.

Second, the game may only detect HDR in exclusive fullscreen mode, or may only re-detect HDR when it is restarted. If Windows HDR was switched on while the game was already running, the game may still be holding the old state. Restarting the game after enabling Windows HDR, and testing exclusive fullscreen, are the two comparisons for this branch.

Third, the game may require native HDR, and Windows Auto HDR does not count. Auto HDR is Windows converting an SDR game into HDR output; it is not the game's own native HDR. A game that reports no native HDR support is not necessarily reporting a Windows fault. How a game detects HDR varies from game to game — some need exclusive fullscreen, some need a restart — so no single game's behaviour should be written as a universal rule. Each game must be verified on its own terms.

The game layer is one step inside the seven-step sequence below, not a guide of its own. Picture calibration inside a game — peak brightness, paper white, and similar settings — belongs to the companion guide on HDR picture problems, and is not repeated here.

"Not Supported" Has Two Meanings

The phrase "Not supported" covers two different situations, and confusing them is the most expensive mistake in this guide.

The first meaning is that the capability chain is broken: the monitor supports HDR, but the report, the transmission, or the driver has failed somewhere, and Windows cannot see the capability. This kind can be repaired, because the capability exists and the chain can be restored link by link.

The second meaning is that the monitor itself does not support HDR: there is no HDR10 report for any chain to carry, and no comparison will produce a switch. This kind is not a fault. It is a product specification, and the honest response is to stop — not to keep buying cables or updating drivers in the hope that one of them will conjure a capability the monitor does not have.

This guide must not imply, for the sake of having a solution, that changing a cable or updating a driver will always work. The seven-step sequence ends with exactly this fork, and the stop branch is a legitimate, complete outcome.

The Seven Steps, In Order

The sequence below is the diagnostic method of this guide. The order is deliberate: each step rules out one layer before the next layer is touched, and the capability readings are re-taken after every change, so that a change in the readings can be tied to the change that caused it.

  1. Describe the fault precisely. Which form of "cannot enable" is it? (a) No HDR switch can be found in Settings at all; (b) the switch is present but greyed out and cannot be pressed; (c) the switch can be turned on but immediately flips back off; or (d) Windows HDR is on, but a game reports that the display does not support HDR. Write down the current combination: which monitor, which cable, which port, and whether any adapter, switch, or dock sits in between.
  2. Read the capability. Go to Settings, System, Display, HDR, selecting the correct target display first — on a multi-display system this selection is essential, since HDR settings are per display. Write down whether "Play HDR games and apps" and "Stream HDR video" are Supported or Not supported. Then run dxdiag and write down AdvancedColorSupported, AdvancedColorEnabled, and Monitor Capabilities.
  3. Check the OSD. Switch HDR or HDR mode on in the monitor's OSD menu; on a TV, switch on the enhanced format (Input Signal Plus or Enhanced format, under whatever name the brand uses — check the manual) for the HDMI port in use. Then go back to step two and re-read the capability. If the readings change, the OSD was the cause. If they do not change, continue to the next layer.
  4. Compare with a direct connection. Remove any adapter, switch, or dock, and connect the graphics card directly to the monitor. Try a different known-good cable (HDMI 2.0 or above, or DisplayPort 1.4, the minimums in Microsoft's guidance for an external display), and try another port. Change only one thing at a time, and re-read the capability after each change.
  5. Compare the driver. In Device Manager, confirm that the graphics driver is the manufacturer's driver and not the Microsoft Basic Display Adapter. Update to the manufacturer's latest stable driver — or, if the problem began immediately after a driver update, roll back as a comparison. On a laptop, plug in mains power and test again, since battery policy can switch HDR off. Do not present a driver update as a guaranteed fix: if the monitor has no HDR report, no driver update will create one.
  6. Cross-check. Connect the same monitor to a different computer, or connect the same computer to a different monitor known to support HDR. If the monitor reports "Not supported" on every computer, the fault points at the monitor. If the computer reports "Not supported" on every monitor, the fault points at the computer, its cable, or its driver.
  7. Decide and stop. If the capability readings have changed to Supported, switch HDR on, and then confirm the game layer using the three-layer switch check — Windows, OSD, and game — as described in the companion guide on HDR picture problems. If the readings remain "Not supported" throughout, and the cross-check shows the monitor itself has no HDR report, stop: this monitor does not support HDR, it is not a fault, and further cable or driver changes will not help. If the readings remain "Not supported" but another computer does recognise the monitor, the fault is on the original computer's side — bring the machine in with the full record.

That record should include the monitor model, the cable type and port used, the Display capabilities reading, the three dxdiag values, the OSD setting found, the driver version, and the result of the cross-check. A record that precise lets an inspection start at the right link instead of repeating the whole sequence.

Diagnostic Logic: Reading the Symptom

SymptomMost likely causeNext step
No HDR switch anywhere in SettingsThe capability chain has not been established, or the wrong display is selectedSelect the correct display, then read Display capabilities and dxdiag before changing anything
Display capabilities says both items are Not supportedOne of the five layers has failedWork the five layers in order, re-reading the capability after each change
One capability item is Supported and the other is Not supportedA partial capability, not a wholly broken chainRecord which item is which; do not treat the split as an error in the listing
The switch is present but greyed outThe capability is listed as Not supported for that display, or the display is bound in duplicate modeCheck the capability reading and the display mode; on a laptop, cancel duplicate display and use Extend
The switch turns on then immediately flips back offA setting, driver, or power state is reversing the changeCheck the dxdiag readings, the driver version, and — on a laptop — whether mains power is connected
HDR disappeared after a driver updateThe update changed the driver reading, or quietly changed a settingCompare the driver version and re-check the switch and OSD; roll back as a comparison if the timing matches
Windows HDR is on but the game says HDR is not supportedThe game is reading an older state, needs exclusive fullscreen or a restart, or requires native HDRConfirm the Windows switch on the correct display, restart the game, test exclusive fullscreen, and check whether the game requires native HDR
The monitor reports Not supported on every computerThe monitor itself has no HDR10 reportCheck the manufacturer's specifications and stop; this is a specification, not a fault

Edge Cases That Are Not This Problem

HDR is on but the picture looks washed out, tinted, or too dark. That is not this guide. That is the companion guide's subject: SDR mapping, paper white, RGB range, and colour gamut, which apply once HDR is already enabled. This guide stops once HDR can be enabled.

The frame rate drops after HDR is switched on. That is not this guide. That belongs to the guide on HDR performance cost, whose premise is that HDR is already working. This guide's seven steps end once HDR is on, and do not continue into performance.

The screen goes black for a moment when HDR is switched. A brief black screen while the display renegotiates is normal. A persistent black screen that needs the cable to be unplugged and reconnected before the picture returns is a different fault, and belongs with the guides on HDR picture problems and display faults.

Individual OSD options are greyed out — brightness or contrast cannot be pressed. That is not this guide. That is the guide on OSD option locking, where the monitor itself locks its own options. This guide is about the Windows side having no switch; that guide is about the OSD side having individual options locked. The directions are opposite, and the two must not be merged.

The display is recognised as a generic PnP monitor, or resolution and refresh-rate options are missing. That is not this guide. That belongs to the guide on EDID and display recognition, which deals with the monitor being misidentified. EDID and DDC are the mechanism behind that recognition — that is all this section says about it.

Resolution or refresh rate is locked at 60Hz. That is not this guide. That belongs to the guide on bandwidth and refresh-rate limits. The point here is only this: the interface version, cable, display stream compression, and colour settings must all hold together.

A DisplayHDR 400 monitor shows the switch but the HDR picture looks flatter than SDR. The switch appearing proves capability detection succeeded; whether the picture looks better is a separate question, and it belongs to the companion guide on HDR picture problems. DisplayHDR level must not be used as a diagnostic standard in this guide.

Streaming HDR in Netflix or YouTube does not appear. Streaming has additional conditions — browser, subscription, content protection, and decoding — that are separate from Windows capability detection. Streaming conditions must not be written as a Windows capability problem.

Six Common Mistakes

  1. Assuming that a box labelled HDR guarantees a Windows switch. The box label can mean the panel accepts an HDR signal. It does not guarantee that the EDID report is complete, that the cable carries it, or that the driver reads it. The switch appears only when all four links of the chain hold.
  2. Assuming that updating the driver will always fix it. If the monitor itself has no HDR report, no number of driver updates will produce a switch. The driver is only the fourth layer; the three layers before it must be checked first, and a driver update must never be presented as a guaranteed fix.
  3. Assuming that a cable that worked for SDR must work for HDR. SDR does not need an HDR report. A cable whose picture pins work correctly can still fail to carry the DDC and HDR report, so a working SDR picture proves nothing about the HDR chain.
  4. Assuming that buying an expensive cable solves everything. A cable is only the third layer. If the OSD has HDR switched off, the driver is wrong, or the monitor itself does not support HDR, no cable at any price will help.
  5. Assuming that a game reporting no HDR means the graphics card does not support HDR. The game reads the capability Windows reports. If Windows HDR is not on, or has not been detected, the game will report no support. Read the Windows capability readings first; do not blame the graphics card directly.
  6. Assuming that a missing switch means the graphics card has failed. A missing switch proves only that one link in the detection chain has not been established. A graphics card that draws the SDR picture normally has already proved its basic output is working. Reinstalling the driver will not fix an OSD that is off, a cable that does not carry the report, or a monitor that has no HDR capability.

When to Stop and Bring the Machine In

Stop when all seven steps have been completed and the capability readings still say "Not supported" while another computer does recognise the monitor — the fault is on the original computer's side and needs inspection with the full record — or sooner if the problem is accompanied by a driver crash, a black screen that persists, or coloured artefacts on screen, because those signs have left this guide and belong to a hardware inspection.

Bring the machine in with a complete record: the monitor model, the cable type and port used, the Display capabilities reading, the three dxdiag values, the OSD setting found, the driver version, the result of the cross-check, and any error messages in their exact wording. Inspection takes place at Room 1209, Dali Plaza, Shek Mun. You can call 2186 8010, or reach the shop on WhatsApp at 6558 6806. Inspection is charged at the site's published three-tier fees of HK$400–2,800, quoted after inspection. There is no home-visit service and no Mong Kok shop; inspection is carried out in the shop.

Frequently Asked Questions

I cannot find the HDR switch anywhere in Windows display settings — where should I look first?

Start with the two readings, not with a driver reinstall. Go to Settings, System, Display, HDR, and first select the correct display at the top of the page if more than one display is connected. Write down whether "Play HDR games and apps" and "Stream HDR video" are Supported or Not supported. Then run dxdiag — Win + R, type `dxdiag`, save all information — and write down AdvancedColorSupported, AdvancedColorEnabled, and Monitor Capabilities. Those readings decide which layer to test first, and they are the baseline for judging every later change.

Display capabilities says “Play HDR games and apps” is not supported — what does that mean?

It means Windows has not established the HDR capability for games and apps on that display, in this combination of monitor, cable, port, and driver. It does not by itself mean the monitor is fake or the graphics card has failed. It means one link in the capability chain has not held: the monitor has not reported HDR capability, the report has not reached the computer intact, the driver has not read it, or Windows has not listed it. The next step is to work the five layers in order — wrong display, OSD, cable and port, driver, monitor itself — re-reading the capability after each change.

How do I read AdvancedColorSupported and Monitor Capabilities in dxdiag?

Press Win + R, type `dxdiag`, and press Enter. Click "Save All Information" and save the text file, or read the values from the Display tab. AdvancedColorSupported states whether the driver and the display together support HDR10. AdvancedColorEnabled states whether HDR is actually switched on right now — capability and current state are different things. Monitor Capabilities states whether the monitor reports HDR support, and for an HDR10 display it should also show BT2020RGB or BT2020YCC together with Eotf2084Supported. Remember that "HDR Not Supported" describes the current combination, not the monitor itself: after changing the cable, the port, or the OSD setting, take the readings again before drawing any conclusion.

My monitor is labelled as HDR-capable — why does Windows still say it is not supported?

Because the box label and the capability chain are different things. The label can mean the panel accepts an HDR signal; the switch appears only when the monitor reports HDR10 capability in its EDID, the cable and port carry that report intact, the driver reads it, and Windows lists it as supported. Any one of those links can fail while the label stays true. Common causes are HDR switched off in the monitor's OSD, an adapter or dock substituting a simplified EDID, a cable or port that does not carry the report, a generic or outdated driver, or the wrong display being selected in a multi-display setup. Work the five layers in order rather than assuming the label settles it.

Where is the HDR switch in the monitor’s OSD, and what happens if it is left off?

The switch is in the monitor's own on-screen display menu, operated by the buttons on the monitor itself; its exact location and name — HDR, HDR Mode, or a similar name — vary by brand, and the monitor's manual is the authority. If it is left off, the monitor does not report HDR capability to the computer, Windows has no basis for offering an HDR switch, and the switch will not appear no matter what is changed in Windows or in the driver. After switching it on, re-read the Display capabilities and dxdiag readings: if they change, the OSD was the cause.

Why does a TV connected to a PC need its enhanced format turned on before HDR appears?

Because the TV will not report HDR capability to the computer until the HDMI port in use has its enhanced format switched on. TV manufacturers give this setting different names — Input Signal Plus and Enhanced format are two of them — and it must be switched on for the specific HDMI port the computer is connected to, not merely somewhere in the TV's menus. Until that is done, the TV's EDID report to the computer says nothing about HDR, and the Windows switch does not appear. Check the TV's manual for the brand-specific name and location.

Can a cable or adapter make the HDR switch disappear, and how do I test that?

Yes. A cable, port, adapter, switch, or dock can fail to carry the monitor's HDR report while still carrying a perfect SDR picture, because the picture channel and the DDC channel that carries EDID can fail independently. Test it with a direct-connection comparison: remove every device in between, connect the graphics card directly to the monitor, try a different known-good cable — HDMI 2.0 or above, or DisplayPort 1.4 — and try another port. Change only one thing at a time and re-read the capability after each change, so it is clear which change made the difference. Price is not a test: an expensive cable is not proven good by its price.

Why did the HDR switch suddenly disappear after a driver update?

Because a driver update can change how the driver reads or reports the monitor's HDR capability, or can quietly change a setting. First re-check the switch location and the OSD setting, and re-read the Display capabilities and dxdiag values, before assuming the update itself is faulty. If the problem began immediately after the update, rolling back to the previous driver version is a legitimate comparison that tests exactly that timing. But a driver update is not the only explanation, and updating the driver again is not a guaranteed fix: if the monitor has no HDR report, or the OSD is off, or the cable does not carry the report, no driver version will produce a switch.

Windows HDR is on, but the game still says HDR is not supported — how do I tell what is wrong?

Start by confirming the Windows switch on the correct display, because the game reads the capability Windows reports: if Windows HDR is not actually on, the game is reading an SDR state. Then restart the game after enabling Windows HDR, since a game already running may still hold the old state, and test exclusive fullscreen, since some games only detect HDR there. Finally, check whether the game requires native HDR: Windows Auto HDR converts an SDR game into HDR output and does not count as the game's own native HDR, so a game reporting no native HDR support is not necessarily reporting a Windows fault. How a game detects HDR varies from game to game, so verify each game on its own terms.

I have tried all the steps above and it still does not work — does that mean my monitor simply does not support HDR?

It may, but that conclusion can only be drawn after the cross-check. If the same monitor reports "Not supported" on a different computer, and the same computer recognises a different monitor known to support HDR, and the manufacturer's specifications confirm the model has no HDR10 support, then yes: the monitor does not support HDR, and that is a product specification, not a fault. Stop changing cables and drivers at that point. If instead another computer does recognise the monitor, the fault is on the original computer's side — bring the machine in with the full record, including the dxdiag file, the capability readings, and the cross-check results.

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: