Night Light not working on Windows 11 — where the warm colour shift that should happen at sunset doesn’t appear, or the toggle in Settings does nothing — is annoying because it’s usually a simple fix but the Settings page doesn’t explain what’s wrong. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
Start here: is Night Light visible in Settings? Settings → System → Display → Night light. Does the toggle actually appear? If yes: toggle it on → click “Turn on now” to test immediately. If the screen doesn’t shift at all (no warm tones, no visible change): continue to Fix 1. If the toggle appears greyed out and non-interactive: a specific display configuration is preventing it — Fix 3.
Fix 1: Display driver issue
Night Light works by applying a gamma adjustment through the display driver. If the driver is outdated, generic, or incompatible: the gamma adjustment either doesn’t work at all or reverts immediately.
Update the display driver from the manufacturer’s website — NVIDIA, AMD, or Intel (for laptops: use the laptop manufacturer’s page rather than Intel’s generic installer). After installing and restarting: test Night Light. This resolves the most common case where Night Light worked previously and stopped after a Windows or driver update.
Fix 2: Time zone and location causing schedule issues
Night Light’s automatic schedule (“Sunset to sunrise”) requires correct time zone and an approximate location to calculate sunset and sunrise times. If the time zone is wrong, the “sunset” time Night Light is looking for may never arrive during your actual evening hours.
Settings → Time and language → Date and time → Time zone → confirm it’s correct for your location. Also: Settings → Privacy and security → Location → confirm location access is on if Night Light uses location services. After correcting the time zone: Settings → Display → Night light → Schedule → toggle off “Sunset to sunrise” → toggle it back on. This forces Night Light to recalculate the schedule with the correct time zone.
Fix 3: Night Light greyed out — HDR or multiple displays
Night Light is disabled by Windows when HDR is active. This is intentional — HDR manages colour through a different pipeline that Night Light’s gamma adjustment doesn’t interact with correctly, so Windows disables Night Light rather than showing incorrect colours.
If HDR is enabled: Settings → System → Display → Windows HD Color → Use HDR → toggle it off. Night Light becomes available immediately. The choice is HDR or Night Light — both simultaneously isn’t currently possible on Windows 11.
Multiple monitors with mixed HDR configurations cause a similar situation. If one monitor is HDR and another isn’t: Night Light may be greyed out for the HDR monitor while working on the non-HDR one. The per-display Night Light toggle in newer Windows 11 builds allows individual control — check whether Night Light settings show per-monitor options.
Fix 4: Registry repair
Night Light stores its configuration in the registry. When these entries become corrupted — after Windows updates, profile migrations, or registry-editing tools — Night Light may appear in Settings but not function, or may always show as off regardless of the toggle state.
Reset Night Light’s registry entries: Win+R → regedit → navigate to HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionCloudStoreStoreDefaultAccountCurrentdefault$windows.data.bluelightreduction.settings → delete the entry → confirm → close Registry Editor → sign out and back in (or restart). Night Light reinitialises from defaults.
An alternative without manually editing the registry: Settings → System → Display → scroll down → look for “Reset” options, or create a new Windows user account → log into the new account → test Night Light. If it works in the new account, the issue is specific to the current user’s profile.
Fix 5: SFC for corrupted system files
The Night Light feature depends on specific Windows components. If these components are corrupted by a bad update or disk error:
sfc /scannowAdministrator Command Prompt. After completion and restart: test Night Light. If SFC found and repaired corruption, Night Light should work correctly again.
Fix 6: Task Scheduler — Night Light schedule service
Night Light uses Windows Task Scheduler to trigger colour changes at scheduled times. If the relevant scheduled tasks are corrupted or disabled, Night Light turns on but doesn’t follow the schedule — it stays in its last state rather than transitioning.
Task Scheduler → Task Scheduler Library → Microsoft → Windows → look for tasks named “NightLight” or related to blue light reduction → confirm they exist and are enabled → right-click → Run manually to test. If running manually triggers the colour change but the schedule doesn’t: the trigger configuration in the task is corrupted. Delete the task and restart — Night Light recreates the task automatically on the next scheduled transition.
Night Light intensity — if it’s on but you can’t see the effect
Settings → Display → Night light → Night light settings → the “Strength” slider. If this is set to minimum (leftmost position), Night Light is technically active but applying such a small colour adjustment that it’s imperceptible. Increase the strength to see a noticeable warm tone. Different people perceive the colour shift differently — someone expecting a dramatic orange-red shift from a maximum-strength setting may not notice the default mid-strength warm tone at all.
Our guide on Windows 11 display settings covers the display driver and colour profile interactions that affect both Night Light and other display customisation features. For the HDR configuration that blocks Night Light, our screen configuration guide covers HDR settings and display output configuration. Microsoft’s Night Light documentation covers the per-application override settings (some apps can suppress Night Light) and the Windows Colour Management profiles that sometimes interact with Night Light’s gamma adjustments.
Third-party display software conflicts
Software that manages display colour — NVIDIA Control Panel colour settings, AMD Radeon colour enhancement, Dell Display Manager, manufacturer-specific screen calibration tools — sometimes conflicts with Windows Night Light by applying their own gamma settings that override or cancel Night Light’s adjustments. You enable Night Light, the screen shifts warm for a second, then the manufacturer software resets the gamma back to neutral.
Test: exit all manufacturer display utilities from the system tray → enable Night Light → observe whether it persists. If it does: one of those utilities was overriding it. Reconfigure the conflicting utility to leave gamma and colour temperature alone while Night Light is active, or disable the conflicting utility permanently if Night Light is the preferred tool.
Night Light not persisting after sleep
Night Light that works correctly but reverts to normal colour temperature after the display wakes from sleep: the display driver resets gamma settings during the sleep/wake cycle and Night Light’s scheduled task doesn’t always re-apply immediately on wake.
Fix: Night Light Settings → toggle Night Light off → toggle it back on. This forces an immediate re-application. For a more permanent fix: update the display driver — manufacturers frequently address gamma persistence through sleep/wake cycles in driver updates because this is a common reported issue on Windows 11.
Custom ICC colour profiles interfering
ICC (International Color Consortium) colour profiles applied to the display for colour accuracy override parts of Night Light’s colour adjustment. A professional monitor calibration profile loaded in Windows can partially or fully prevent Night Light from shifting the colour temperature because the ICC profile takes precedence in the colour pipeline.
Settings → Display → Advanced display settings → Display adapter properties → Color Management tab → Profiles → if a custom ICC profile is listed as the device profile, Night Light’s warm shift competes with the profile’s colour correction. This is expected behaviour — Night Light and colour-critical ICC profiles are fundamentally incompatible because they’re trying to achieve opposite things (accurate colour vs warm-shifted colour). Use Night Light when colour accuracy isn’t needed; disable it when doing colour-critical work.
Windows Quick Access and Night Light toggle
The notification area (bottom right → expand system tray) has a Night Light quick toggle. This toggle and the Settings toggle are separate UI elements that both affect the same underlying setting — but occasionally they get out of sync due to UI refresh issues. Toggling Night Light through the Quick Settings panel (Win+A → Night Light tile) sometimes works when the Settings toggle appears unresponsive, because it uses a different code path to apply the change.
Night Light and remote desktop sessions
When using Remote Desktop to connect to another machine: Night Light on the remote machine is typically disabled or overridden by the remote display driver that RDP uses. Night Light settings may appear correct on the remote machine but the colour shift isn’t visible through the RDP session because RDP uses its own colour pipeline.
Configure Night Light on the local machine (the one you’re physically looking at) rather than the remote one. Night Light affects the physical display — the machine you’re sitting in front of. Remote machines’ Night Light settings don’t affect what you see on your local screen through an RDP connection.
Fast startup and Night Light state restoration
Windows Fast Startup saves system state during shutdown. Night Light’s on/off state is included in this saved state. When the saved state becomes inconsistent — Night Light was on when shutdown happened, but the stored state says it was off — Night Light doesn’t initialise correctly on the next boot and may appear to not be working.
Test: disable Fast Startup (Control Panel → Power Options → Choose what the power buttons do → uncheck “Turn on fast startup”) → shut down completely → power on → check Night Light. If Night Light works correctly after a “real” shutdown (no Fast Startup): the Fast Startup saved state had a Night Light inconsistency. A full shutdown clears this. Re-enable Fast Startup after confirming.
When Night Light is working but not helping with eye strain
Night Light reduces blue light emission by shifting colour temperature to warmer tones. The amount of blue light reduction at Windows’ default settings is modest. If the goal is reducing eye strain or improving sleep: increase the Night Light strength slider to its maximum, enable Night Light earlier (before sunset rather than at sunset), or combine it with reducing overall screen brightness (which has more impact on eye strain than colour temperature alone).
Third-party alternatives like f.lux provide more aggressive colour reduction and finer schedule control than Windows’ built-in Night Light. They work through the same gamma pathway and have the same HDR compatibility limitation, but allow lower colour temperatures than Windows permits — reaching 2700K and lower, compared to Windows Night Light’s minimum of around 3400K. If Windows Night Light’s maximum strength still isn’t enough, f.lux is the practical next step rather than assuming Night Light is broken.
Checking Night Light is actually applying via gamma values
To confirm Night Light is applying (even if the visual change is subtle): while Night Light is enabled, open Display Color Calibration (search in Start → “calibrate display color”). The gamma curve shown should be shifted — the curve not centered at its neutral position indicates gamma adjustments are being applied. If the gamma curve looks neutral when Night Light is supposed to be active: the driver isn’t accepting the gamma adjustment, which points back to the driver update as the fix.
For Night Light that worked fine and then stopped after a Windows update: the update likely changed the display driver or the Night Light component itself. The registry reset (Fix 4) combined with a driver update from the manufacturer covers both possibilities. If neither works: check whether Windows Update has any “Display adapter” updates pending that weren’t installed — sometimes a driver update that would fix Night Light is sitting in Windows Update history as optional or pending. Installing all pending updates, restarting, and retesting takes 10 minutes and resolves a significant proportion of post-update Night Light failures.
A summary of the fix priority: Night Light greyed out → check HDR setting (most likely cause). Night Light on but no visible change → check Strength slider, then driver update. Night Light not following schedule → check time zone, then Task Scheduler tasks. Night Light resets after sleep → driver update. Night Light works for some users but not this one → registry reset for the current user profile. These five scenarios cover 95% of Night Light failures — the display colour profile conflicts, third-party software overrides, and remote desktop scenarios are genuinely edge cases that most users won’t encounter.
Worth noting: Night Light’s visual effect varies significantly by monitor. An IPS panel with wider colour gamut shows a more dramatic warm shift from Night Light than a TN panel. A calibrated professional monitor with a D65 white point looks “orange” in Night Light at the same colour temperature that looks “slightly warm” on a laptop display. These are normal differences in display technology rather than Night Light working differently on different machines — the underlying gamma adjustments are identical, but the visual result depends on the monitor’s natural colour reproduction characteristics. Related: Windows 11 Context Menu Slow.
