Fix Night Light That Won't Turn On

Night Light is one of those features you don’t appreciate until it breaks — then every evening reminds you. The failure modes are oddly specific: the toggle greys out, the schedule runs but the screen never warms, or it works on the laptop display but not the external monitor. Underneath, Night Light is a handshake between Windows and your GPU driver over display color controls, and most failures are that handshake breaking.

The fixes below rebuild that handshake step by step, from the registry keys that govern it to the driver that implements it.

What makes Night Light failures confusing is that the feature spans three separate systems that rarely get discussed together. Windows owns the schedule and the on/off state, stored in a CloudStore registry hive that syncs across your devices. The GPU driver owns the actual color-temperature transformation, applied per-display at the output stage. And the display’s color profile sits in between, able to veto the whole operation if corrupted. When the toggle greys out, Windows has lost the driver’s capability handshake; when the schedule runs but nothing visibly changes, the state and strength settings are usually at fault; when it works on one display but not another, the per-display path is broken. Knowing which of the three is misbehaving tells you which fix to reach for first, instead of trying them at random.

Why this happens

• GPU driver lost the color-control handshake: After a driver update, Windows can’t access the display’s color temperature controls.
• Corrupted Night Light registry state: The feature’s on/off state and schedule live in the registry; corruption freezes the toggle.
• Group policy disabled it: Enterprise-managed or tweaked systems may have Night Light policy-disabled.
• Display driver reports no support: Generic basic display drivers don’t expose the color APIs Night Light needs.
• Third-party blue-light app conflict: f.lux, SunsetScreen, or monitor utilities fight Windows for color control.
• Corrupted color profile: A damaged ICC profile can block the color-temperature transformation.
• Fast Startup preserving a bad state: The hibernated display stack carries the broken handshake across reboots.
• External monitor EDID issues: A monitor reporting bad capabilities data can disable Night Light on that output.

How to fix it

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

Fix 1: Check the toggle and schedule basics

1. Open Settings → System → Display → Night light and confirm the master toggle is on.
2. Check the schedule — if it’s set to sunset-to-sunrise, verify your location and time zone are correct.
3. Drag the strength slider to maximum temporarily to make the effect obvious.
4. If the toggle is greyed out rather than just ineffective, skip to the driver and registry fixes — the feature is blocked, not misconfigured.

Fix 2: Remove conflicting apps

1. Uninstall or fully quit f.lux, SunsetScreen, or any monitor-control utility.
2. Check the system tray for GPU utilities (Intel Graphics Command Center, NVIDIA Control Panel) with their own night-mode or color features and disable those.
3. Restart after removing conflicts — color-control hooks often persist until reboot.
4. Only one application should own the display’s color temperature at a time.

Fix 3: Reset the Night Light registry state

1. Press Windows + R, type regedit, and navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CloudStore\Store\DefaultAccount\Cloud.
2. Find and delete the keys containing windows.data.bluelightreduction (there are usually two: settings and state).
3. Restart the laptop — Windows rebuilds clean Night Light state on boot.
4. Reconfigure your schedule in Settings → System → Display → Night light. This clears the corrupted-state freezes that leave the toggle dead.

Fix 4: Reinstall the GPU driver cleanly

1. Open Device Manager → Display adapters, right-click your GPU, and choose Uninstall device (delete driver if offered).
2. Restart, then install the latest driver from the manufacturer: Intel via the Intel Driver & Support Assistant , NVIDIA from the NVIDIA driver page , AMD from AMD drivers .
3. Choose clean installation when offered.
4. The fresh driver re-registers color-control capabilities with Windows, which is what un-greys the toggle. If brightness controls also broke, see our display brightness fix .

Fix 5: Reset the color profile

1. Open Color Management from the Start menu.
2. Select your display, check Use my settings for this device, and remove any custom ICC profiles, reverting to the system default (sRGB).
3. On the Advanced tab, ensure the device profile is the system default.
4. A corrupted custom profile can silently block Night Light’s color transformation.

Fix 6: Check group policy and registry policy

1. Press Windows + R, type gpedit.msc (Pro editions), and check under User Configuration → Administrative Templates for anything disabling Night Light or display settings.
2. In regedit, check HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows for display-related restrictions.
3. Home-edition users: the same restrictions can exist as registry values set by “debloat” scripts — search for BlueLightReduction policy keys.
4. Remove offending policies and restart; policy blocks override every other fix.

Fix 7: Cold-boot past Fast Startup

1. Disable Fast Startup in Control Panel → Power Options → Choose what the power buttons do.
2. Shut down fully and power on after fifteen seconds.
3. Test Night Light immediately after the cold boot.
4. If it works now, the hibernated display-driver state was the problem — consider leaving Fast Startup off.

Fix 8: Test the external monitor separately

1. Disconnect the external monitor and test Night Light on the laptop display alone.
2. If it works internally but not externally, update the monitor’s firmware and try a different cable/port.
3. Check Microsoft’s Windows support site for Night Light known issues tied to your update.
4. For persistent external-only failure, the monitor’s EDID data may be at fault — a different monitor confirms it. The Windows 11-specific variant is covered in our Night Light on Windows 11 guide .

Closing

Night Light breaks at the handshake between Windows and the GPU driver, and the fix is rebuilding that handshake: clear the conflicting apps, reset the registry state, and reinstall the graphics driver clean. It’s a small feature with an outsized effect on evening comfort — worth the twenty minutes to get back. And once it’s working, protect it the same way you’d protect any driver-dependent feature: let the GPU driver update on your schedule, not Windows Update’s, and re-check the Night Light toggle after every major feature update, since that’s when the handshake most often breaks.

Frequently asked questions