How to Fix Windows 11 Night Light Not Working or Grayed Out

By Derek V. Mackown | IT Technician & Display Hardware Specialist

Night Light is one of those Windows features that works invisibly for months, maybe years quietly shifting your screen toward warmer tones at sunset, doing its small, good deed for your sleep quality without asking for any attention. And then one day it just stops. The toggle is grayed out. Or it’s on but the screen stays ice-cold blue at 11pm. Or the setting disappears from Display entirely. Or it used to work and a Windows update quietly killed it.

There’s something specifically frustrating about a comfort feature failing. It’s not dramatic. Nothing crashed. You can still work. But the screen is cold and you know it’s supposed to be warm and there are approximately seven different reasons it might not be working and Windows gives you precisely zero diagnostic information about which one applies to you.

I’ve fixed this across dozens of machines. The causes span from HDR being enabled (which silently disables Night Light without telling you) to a corrupted sensor service to a display driver that doesn’t support the color transformation Night Light needs. Let’s find yours.

How Night Light Actually Works | The Chain That Has to Hold

Before the self-triage, one minute of context that makes every fix below immediately obvious.

Night Light in Windows 11 is not a simple toggle. It’s a feature that depends on five separate system components all being functional and compatible simultaneously:

Link 1 — The display driver color path. Night Light works by applying a gamma ramp adjustment, a color transformation that pushes the display output toward warmer color temperatures. This requires the display driver to support the Windows Color System (WCS) color transformation interface. A driver that doesn’t support this interface, a generic Microsoft driver, certain older OEM drivers, simply cannot apply the adjustment. Night Light grays out entirely.

Link 2 — The Sensor service. Night Light’s automatic scheduling uses Windows’ location and time-zone awareness to calculate local sunrise and sunset. This runs through the Sensor Monitoring Service (SensrSvc). If this service is stopped or disabled, which some aggressive Windows optimization tools do. Night Light loses its ability to auto-schedule, and on some configurations, grays out the entire feature.

Link 3 — Location services. For “sunset to sunrise” timing, Windows needs to know your location. Not precisely, just enough to calculate solar times. If Location Services are disabled globally or for Windows specifically, Night Light falls back to a manual schedule. If no manual schedule is configured, the feature appears to do nothing.

Link 4 — The registry Night Light state. Windows stores Night Light’s active state, schedule configuration, and current color temperature offset in the registry. When this data becomes corrupted, which can happen after Windows updates, user account changes, or profile migrations. Night Light loads in a broken state from that corrupted baseline.

Link 5 — HDR compatibility. This is the most commonly overlooked link and the most frequent culprit on modern gaming setups. Windows Night Light and HDR are incompatible by design. When HDR is enabled on a display, Windows hands color management to the HDR pipeline, which operates in a color space that Night Light’s gamma ramp adjustments cannot reach. Night Light doesn’t just stop working silently, it grays itself out with no explanation, leaving most users to assume a driver problem when it’s actually a display feature conflict.

Break any one of these links and Night Light fails. The symptom of how it fails tells you which link broke.

What Exactly Is Your Screen Showing | Find Your Symptom

Don’t start fixing until you’ve identified your specific symptom. Night Light fails in four distinct ways that require completely different interventions.

The Night Light toggle is grayed out – unclickable.

Settings → System → Display → Night Light toggle is present but frozen. You can see it. You cannot interact with it.

This is either Link 1 (display driver doesn’t support color transformation) or Link 5 (HDR is enabled). These are the two conditions that lock the toggle completely. Check HDR first, it takes ten seconds. Settings → System → Display → HDR. If HDR is on and your screen goes to Normal when you turn it off: that was it. Night Light will be interactive immediately.

If HDR is already off and the toggle is still gray: the display driver is the problem. Jump to the Driver section.

Night Light is toggled ON but the screen doesn’t change color at all.

The toggle works, the schedule is set, Night Light appears to be active, but the screen remains cold and white at midnight. You watch the clock hit the scheduled time and nothing happens.

This is Link 3 (location services disconnected from scheduling), Link 4 (registry state corruption), or a manual schedule that isn’t correctly configured. The feature is enabled in the UI but the color transformation isn’t reaching the display. Jump to the Scheduling and Registry sections.

The Night Light option has disappeared from Display Settings entirely.

Not grayed out, completely absent. No toggle, no schedule, nothing. As if the feature was uninstalled.

This is either the display driver running in a Basic Display Adapter state (no WCS support, so Windows removes the UI element entirely) or a Windows build issue where the feature registration became corrupted. Jump to the Driver section, and if the driver is correct, the Windows Feature section.

Night Light works on one monitor but not another in a multi-monitor setup.

One display shifts to warm tones correctly. The other stays cold.

Night Light applies per-display based on each monitor’s color capability profile. If one monitor’s display driver supports WCS color transformation and the others doesn’t or if one is connected through a pathway that bypasses the color transformation (certain USB-C docking stations, HDMI switches, some capture cards) Night Light can selectively apply only to the displays with compatible pathways. Jump to the multi-monitor section.

Fix 1 – Turn Off HDR (The Fix That Works for Most People)

This is where a disproportionate number of Night Light problems live, and I’ll say it plainly: Windows should tell you that Night Light is disabled because HDR is on. It doesn’t. It just grays out the toggle and offers nothing. This design choice has confused more people than it should.

Settings → System → Display → look for HDR or Use HDR → confirm it’s set to Off.

If you see “Windows HD Color” instead of a simple HDR toggle: click it → toggle Use HDR to Off.

After disabling HDR, return to Night Light settings. The toggle will be interactive immediately.

If you use HDR for gaming or media and don’t want to disable it permanently: HDR can be toggled per-session with Windows + Alt + B. A keyboard shortcut that switches HDR on and off without opening Settings. Set your display to SDR for evening work sessions when Night Light matters to you, and switch back to HDR when you launch content that benefits from it. Night Light and HDR simply cannot coexist in the current Windows color architecture, you choose one.

Why they conflict: Night Light modifies the display’s gamma ramp, a color transformation applied in the SDR color pipeline. HDR bypasses the SDR pipeline entirely and operates through a separate high-dynamic-range color path. The gamma ramp adjustment that Night Light applies doesn’t exist in the HDR pipeline. Windows’ solution to this architectural incompatibility is to disable the inaccessible feature rather than attempt an incomplete implementation. It’s technically correct. It’s also terrible UX.

Fix 2 – The Display Driver Is Blocking Color Transformation

If HDR is off and Night Light is still grayed out or missing, the display driver doesn’t support the color transformation interface Night Light requires.

Confirm which driver is active:

Press Windows + X → Device Manager → expand Display adapters.

If Microsoft Basic Display Adapter is showing:

Night Light is completely inaccessible without a real display driver. Install the correct driver from your GPU manufacturer’s site (nvidia.com, amd.com, intel.com) or your laptop manufacturer’s support page. Night Light will appear and function immediately after a successful driver install and restart.

If the correct GPU is showing but Night Light is still grayed out:

The driver version may be outdated enough to lack WCS color transformation support, or the driver installation is partially corrupted. Run a clean driver reinstall:

1. Download the latest driver from your GPU manufacturer
2. Download DDU (Display Driver Uninstaller) from guru3d.com
3. Boot into Safe Mode (hold Shift → click Restart → Troubleshoot → Advanced options → Startup Settings → press 4)
4. Run DDU → Clean and restart
5. Install the fresh driver
6. Restart and test Night Light

After a clean driver install, if Night Light is still grayed out with HDR confirmed off, there is a display driver level incompatibility specific to your GPU and driver version. Check your GPU manufacturer’s known issues page or community forums for your specific GPU and Windows build version. Some driver releases have documented Night Light regressions that subsequent updates fix.

Fix 3 – The Sensor Service Has Been Stopped

The Sensor Monitoring Service Feeds Windows’ awareness of time and location context that Night Light uses for automatic scheduling. When it’s stopped, Night Light loses its scheduling capability and on some Windows 11 builds, this causes the toggle itself to become unresponsive even when HDR is off and the driver is correct.

Check the service state:

Press Windows + R → type services.msc → Enter → scroll to Sensor Monitoring Service.

If the Status column shows anything other than “Running” – right-click → Start.

Then scroll to Sensor Data Service and confirm it’s Running as well. Both services feed the same context pipeline that Night Light’s scheduler depends on.

After starting both services, test Night Light without restarting first, the toggle should become responsive immediately if this was the cause.

Make the fix permanent:

If either service was stopped and Night Light works after starting them, right-click each service → Properties → Startup type → change from Disabled or Manual to Automatic. Click Apply. This ensures they start with Windows automatically rather than waiting to be manually triggered.

Why these services get disabled: Aggressive Windows “optimization” guides and debloating scripts routinely disable sensor services as part of batch operations targeting services, they consider unnecessary. The Sensor service genuinely uses minimal resources and disabling it saves nothing meaningful but it’s listed as “non-essential” in many optimization templates. If you’ve ever run a Windows debloat script or used an optimization tool, check these services first.

Fix 4 – Location Services Need to Be On for Auto-Scheduling

Night Light’s “Sunset to Sunrise” mode calculates local solar times using your device’s location. Location Services being off doesn’t prevent Night Light from working with a manual schedule, but it does prevent auto-scheduling, and on some configurations, it causes “Sunset to Sunrise” to silently fail, making Night Light appear to activate and deactivate at random or not at all.

Check Location Services:

Settings → Privacy & security → Location → Location services → toggle On.

Below that, scroll to Let apps access your location → confirm it’s On.

Further down the list, find Time zone or Windows Time Service and ensure Windows is allowed to use location for time zone auto-detection.

After enabling Location Services, return to Night Light settings → Schedule → if “Sunset to sunrise” was selected and your location is now accessible, Windows will calculate your local solar times and display them next to the setting. If the times shown match your actual location’s sunrise and sunset, the location feed is working.

If you prefer not to enable Location Services:

Switch Night Light to a manual schedule. Settings → System → Display → Night Light → Schedule → select Turn on at a set time → configure your preferred hours. Night Light will activate and deactivate at those fixed times regardless of location or sunrise/sunset data.

Manual scheduling is more reliable than auto-scheduling for users who work unusual hours or in locations with extreme day/night variation and it eliminates the location service dependency entirely.

Fix 5 – The Registry Night Light State Is Corrupted

This is the fix for Night Light that toggles, shows as active, has a schedule configured and simply doesn’t change the screen color at all. The UI is functional. The actual color transformation isn’t happening. The registry data Windows uses to track Night Light’s active state has become inconsistent.

Windows stores Night Light configuration in two registry locations:

HKCU\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\DefaultAccount\Current\default$windows.data.bluelightreduction.bluelightreductionstate

HKCU\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\DefaultAccount\Current\default$windows.data.bluelightreduction.settings

These keys contain binary data encoding Night Light’s active state, scheduled hours, and current color temperature value. When this data becomes corrupted, after a Windows update that changes the data schema, after a user account migration, or after a profile sync issue. Night Light reads the corrupted baseline and cannot apply the correct transformation.

The fix – delete and regenerate the keys:

1. Press Windows + R → type regedit → Enter
2. Navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\DefaultAccount\Current\

3. Look for two subkeys beginning with default$windows.data.bluelightreduction
4. Right-click each → Delete → confirm
5. Close Registry Editor
6. Open Settings → System → Display → Night Light
7. Configure Night Light from scratch, toggle it on, set your schedule and color temperature

Windows regenerates these registry keys fresh when Night Light is configured through Settings. The fresh keys contain valid data and the color transformation will apply correctly.

Before deleting: If you want to be cautious, right-click each key → Export → save a backup to your Desktop. If the deletion causes any unexpected behavior, you can restore the original keys by double-clicking the exported .reg files.

Fix 6 – Resetting Night Light Completely Through the UI

Before going to the registry, try this softer reset that accomplishes a similar result without touching registry keys directly.

1. Settings → System → Display → Night Light → click Night Light settings
2. Turn Night Light Off if it’s on
3. Set the schedule to Off (no schedule)
4. Change the Color temperature slider to its warmest point and back to center
5. Close Settings completely
6. Press Windows + I to reopen Settings → System → Display
7. Toggle Night Light On → set your schedule fresh

This forces Windows to rewrite the Night Light configuration from a clean state. For corrupted settings that aren’t severe enough to require registry deletion, this surface-level reset clears the inconsistency.

If this doesn’t work and the registry fix above also hasn’t helped: the corruption is deeper, proceed to the Windows build fix below.

Fix 7 – Multi Monitor Night Light Inconsistency

One screen warm, one screen cold. This specific symptom has a specific cause: each display in Windows is processed through its own color transformation pipeline, and Night Light’s gamma ramp applies independently to each display’s pipeline.

The selective application diagnosis:

Which monitor is staying cold? If it’s the one connected through HDMI rather than DisplayPort, or through a USB-C hub rather than directly to the GPU: the color transformation pipeline for that connection may not support WCS gamma ramp adjustments. Certain connection paths, USB-C DisplayLink adapters, HDMI audio extractors, some docking stations with their own display processing, insert intermediate signal processing that breaks the color transformation chain.

Tests in sequence:

Connect the non-responding monitor directly to the GPU with a direct DisplayPort cable bypassing any hub, dock, or adapter. Test Night Light.

If Night Light now applies to both monitors: the intermediate device in the previous connection path was breaking the color pipeline. Either use a direct GPU connection for that display, or replace the intermediary device with one that passes color transformation data without modification (Thunderbolt docks from major manufacturers generally preserve color pipelines better than generic USB-C DisplayLink docks).

The manual-per-monitor Night Light workaround:

Windows 11 doesn’t expose per-monitor Night Light control natively. If one monitor consistently resists Night Light due to its connection path and a direct GPU connection isn’t practical, f.lux (free, justgetflux.com) provides per-monitor color temperature control with far more granular settings than Windows Night Light, including per-display adjustments, custom color temperature curves, and profiles that work independently of Windows’ color pipeline.

Fix 8 – Windows Build and Feature Registration Issues

If every fix above has failed, HDR off, driver clean-installed, services running, location on, registry regenerated and Night Light is still absent or non-functional, the feature registration itself is corrupted in this Windows installation.

Run the Windows component repair:

Open Command Prompt as administrator (search “cmd” → right-click → Run as administrator):

DISM /Online /Cleanup-Image /RestoreHealth

Wait for this to complete, it takes 5 – 15 minutes. Then:

sfc /scannow

Both commands scan and repair Windows component files. Night Light’s display transformation component is part of the Windows Display Infrastructure, if a component file was corrupted during a Windows update or drive error, these commands restore it from the Windows Component Store.

After both commands complete, restart and test Night Light.

If the feature is still absent after component repair:

The Windows installation may have a deeper corruption that survived the repair commands. At this point, a Windows 11 in-place upgrade repair, which reinstalls Windows without removing your files is the definitive solution. Settings → System → Recovery → Reset this PC → Keep my files → Cloud download (reinstalls Windows from Microsoft’s servers, ensuring fresh component files). This is the last resort, but it resolves Night Light absence caused by installation-level corruption in 100% of cases.

The One-Minute Complete Checklist

If you want the fastest possible path through everything above:

1. HDR off? Settings → Display → HDR → Off. Test.
2. Real GPU driver installed? Device Manager → Display adapters → not “Microsoft Basic Display Adapter.” Fix if needed.
3. Sensor services running? services.msc → Sensor Monitoring Service → Running. Start if stopped.
4. Location services on? Privacy & security → Location → On. Test with Sunset to Sunrise.
5. Night Light UI reset? Turn off, clear schedule, toggle back on fresh.
6. Registry keys deleted? Both bluelightreduction keys under CloudStore → deleted and regenerated.
7. Multi-monitor: direct GPU connection? If one monitor is cold, bypass the hub.
8. Windows repair run? DISM + SFC if everything else clean.

Work through them in that order. Most people are done by step 1 or 2.

Frequently Asked Questions

Q: Night Light works perfectly but I can barely see any difference even at the warmest setting. Is something wrong?

Probably not, the warmest setting on Windows Night Light shifts the display to approximately 1200K, which is a noticeable but not dramatic warm shift. If the shift seems very subtle, confirm that your monitor’s color temperature setting in its OSD isn’t set to a very cool preset (7000K+) that’s partially counteracting Night Light’s warm shift at the hardware level. Set your monitor’s OSD color temperature to 6500K (D65) or Neutral as a baseline, then test Night Light again.

Q: Night Light turns on at 4pm even though my sunset is much later. Why?

Windows is either using an incorrect location or defaulting to a built-in schedule that doesn’t match your actual coordinates. Open Night Light settings → Schedule → if it shows “Sunset to sunrise,” check whether the displayed sunset time matches your actual local sunset. If it doesn’t, Location Services aren’t providing accurate coordinates, enable location services fully (Fix 4) or switch to a manual schedule set to your actual preference.

Q: After a Windows 11 feature update, Night Light stopped applying any color change. The toggle works and shows On. What happened?

Feature updates can reset registry Night Light state keys to a post-update default that has the feature marked “on” in the UI but with a color temperature offset of zero, effectively scheduling a warm shift of nothing. This is Fix 5’s scenario. Delete the two blue light reduction registry keys and reconfigure Night Light from Settings. This has been a documented issue after multiple Windows 11 feature updates since 22H2.

Q: Can I get Night Light to work with HDR enabled? I don’t want to lose HDR just for warmer colors at night.

Not through Windows Night Light natively. The HDR pipeline genuinely doesn’t support gamma ramp adjustments. Your options: use f.lux in “HDR-aware” mode f.lux uses a different color transformation technique that can partially work within HDR pipelines, though with less precision than Night Light achieves in SDR. Alternatively, use Windows + Alt + B to toggle HDR off in the evenings and let Night Light run in SDR mode, then re-enable HDR when you start gaming or watching content that benefits from it.