Known limitations

Here you can find a list of limitations for the latest Auto Dark Mode version 11.1.0.23, as well as issues we are aware of that may or may not be fixed in the future:

• The process list on the condition page isn't filtering processes while typing (tracked in https://github.com/AutoDarkMode/Windows-Auto-Night-Mode/issues/1105).
• We are investigating in some config saving issues, resulting in app language and window size not being saved properly (tracked in https://github.com/AutoDarkMode/Windows-Auto-Night-Mode/issues/1249).

• Changing the offset of night light right after it activated may cause the theme to switch back as the switch time is moved to the past.
  We are only able to detect if night light turns on or off and the time when it changes state at the moment.
• When switching to or from daylight savings time, it may take up to 24 hours to update geopos-based suntimes, as that is the internal update rate of the location module

• Wallpapers may not update correctly for single monitor systems that use virtual desktops
• Using a different charset than CodePage1252 or ANSI in the theme name may result in failed theme switches

• Roamed themes may cause wallpaper switch to malfunction.
• Negative offsets for the Windows Night Light mode are not permitted.
• Especially on dual-monitor-setups, the taskbar colors sometimes glitches.

• When you don't use Auto Dark Mode to switch your apps theme while having the auto switch notifications enabled, the following limitation applies: Starting the service and choosing to postpone the theme immediately will cause theme changes via our GUI to instantly trigger a full theme switch, disregarding postpone status. After this switch has been performed, postponing while changing theme settings in the UI will function as expected.