There is a particular kind of frustration reserved for pressing play on a Netflix show, hearing the opening music, and staring at a perfectly black screen. The audio is fine, the controls respond, and every non-Dolby Vision title plays without a problem — but the moment a Dolby Vision title starts, the picture vanishes. On ARM laptops this pattern is more common than on Intel machines, because the Dolby Vision video path depends on drivers, codecs, and display negotiation that are newer and less settled on Windows on ARM.

The good news is that the stream itself is not broken, and your laptop is not failing. The black screen means one link in the Dolby Vision chain failed: the browser or app, the video codec, the graphics driver, or the display’s HDR handshake. Each link has a fix, and working through them in order usually restores playback without losing Dolby Vision entirely.

This guide starts with the fastest workarounds, then moves to the lasting fixes: testing the app, updating codecs and drivers, and correcting HDR settings so Dolby Vision titles play in full color.

Why this happens

  • ARM graphics driver gap: Dolby Vision decoding on ARM depends on driver support that may be incomplete or buggy in older driver versions.
  • Missing or broken video codec: The HEVC or Dolby Vision codec path in the browser or app can fail silently, producing audio with no picture.
  • HDR handshake failure: If Windows and the display disagree about HDR capability when a Dolby Vision title starts, the video pipeline outputs black.
  • Browser playback path issue: Edge and Chrome handle protected HDR video differently, and a browser update can break the Dolby Vision path while standard video still works.
  • Display driver color space bug: A driver that mishandles the Dolby Vision color space can output a black frame instead of the decoded picture.
  • Windows HDR setting conflict: HDR enabled in Windows but disabled or misconfigured in the app can leave Dolby Vision titles with no valid output target.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm the pattern and try the other playback path

A quick comparison tells you whether the problem is the app, the browser, or the system.

  1. Play a Dolby Vision title in the Netflix app if you were using a browser, or in Edge if you were using the app.
  2. Play a non-Dolby Vision HDR title and a standard title to confirm only Dolby Vision is affected.
  3. Note whether audio plays during the black screen, which confirms the stream itself is fine.
  4. Try the same title on an external display if one is available, to rule out the built-in panel.
  5. If one playback path works, use it while you fix the other, and focus the remaining steps on the failing path.

Fix 2: Toggle HDR and Dolby Vision settings

Settings toggles are the fastest way to restore playback, even if they cost you HDR temporarily.

  1. Open Settings, go to System, then Display, and turn HDR off, then play the title again.
  2. If video returns with HDR off, the problem is in the HDR or Dolby Vision pipeline, not the stream.
  3. Turn HDR back on and check the Netflix app’s own video settings for a Dolby Vision or HDR toggle.
  4. In Edge, check edge://flags for hardware video decoding settings only if you are comfortable changing experimental flags.
  5. Keep HDR off as a temporary workaround while you apply the driver and codec fixes below.

A similar pipeline-toggle fix helps when Eye Contact effects flicker because one processing stage fails, and the same isolate-the-pipeline approach applies when Lightroom AI Denoise crashes on Snapdragon. For a related playback check, see sleep study battery drain reports .

Fix 3: Update graphics drivers and install video codecs

Drivers and codecs are the most common lasting fix for ARM Dolby Vision black screens.

  1. Open Device Manager, expand Display adapters, and update the graphics driver.
  2. Visit your laptop maker’s support site for the latest ARM graphics driver for your exact model, since generic drivers may lag behind.
  3. Open the Microsoft Store and install or update the HEVC Video Extensions if they are offered for your device.
  4. Check for Windows updates, since codec and protected-media fixes often arrive through Windows Update.
  5. Restart the laptop and test the same Dolby Vision title again.

Fix 4: Clear the browser or app playback cache

Corrupted cached playback data can break protected HDR video while leaving everything else working.

  1. In Edge, open Settings, then Privacy, and clear cached images and files for all time, keeping passwords and history if you prefer.
  2. If you use the Netflix app, open Settings, go to Apps, find Netflix, and choose Repair, then Reset if repair does not help.
  3. Sign back into Netflix after a reset and test the same title.
  4. Disable browser extensions temporarily, since video or privacy extensions can interfere with protected video playback.
  5. Test in a private browser window to rule out extension interference before re-enabling extensions one by one.

Fix 5: Adjust display and power settings

Display power management can interrupt the HDR handshake at the exact moment a Dolby Vision title starts.

  1. Open Settings, go to System, then Power and battery, and set Power mode to Balanced or Best Performance.
  2. Play the title while plugged into the charger, since battery power limits can change display behavior.
  3. Turn off any maker display power-saving or adaptive brightness feature temporarily.
  4. If you use an external display, test with only the built-in display active, since multi-display HDR negotiation can fail.
  5. Re-enable power-saving features one at a time after playback works, to find the one that broke it.

Fix 6: Check for known driver issues and report the fault

If every fix fails, the problem may be a known ARM driver limitation that only a future update resolves.

  1. Search your laptop maker’s support forum for Dolby Vision black screen reports for your model.
  2. Check Microsoft’s official video playback guidance at Microsoft Support for ARM-specific steps.
  3. Try the latest Windows Insider or optional driver update only if you are comfortable with pre-release software.
  4. Keep HDR off for Netflix as a stable workaround and enjoy standard HDR or SDR playback in the meantime.
  5. Report the issue through the Feedback Hub with your model and driver version, since ARM Dolby Vision fixes depend on maker and Microsoft reports.

Closing

A black screen on Dolby Vision titles feels like Netflix is broken, but the stream is fine — it is the HDR video pipeline on ARM that has stumbled. Test the other playback path, update the graphics driver and codecs, and correct the HDR settings, and most ARM laptops play Dolby Vision again. If the black screen persists after every fix, keep HDR off for Netflix as a reliable workaround and watch for the driver update that closes the gap.

Frequently asked questions

Why does Netflix go black only with Dolby Vision titles?
Dolby Vision uses a separate HDR pipeline in the browser or app. If the graphics driver, codec, or display handshake fails for that pipeline, Dolby Vision titles show black while standard titles play normally.
Why does audio keep playing during the black screen?
The audio pipeline is independent of video decoding. Audio continues because the stream is fine; only the Dolby Vision video decode or display path has failed.
Does this affect the Netflix app and the browser equally?
Not always. The Windows Netflix app and Edge handle Dolby Vision differently, so one may work while the other shows black, which is a useful diagnostic clue.
Can I just turn off Dolby Vision to fix it?
Yes, disabling Dolby Vision or HDR is a valid workaround that restores playback immediately, though you lose the HDR picture until the underlying driver or codec issue is fixed.