windows-internals

Apps and shell themes diverge deliberately: what each listens to

AppsUseLightTheme drives app surfaces; SystemUsesLightTheme drives the shell. Setting them independently is a feature — with documented restore.

ProofTune Project··4 min read
Windows internals illustration Windows internals

The two bits

AppsUseLightTheme
what modern app surfaces follow (WinUI/Win32 with theming)
SystemUsesLightTheme
taskbar, Start, system flyouts

Why two, not one

  • Users have settings-consistent subpreferences with visual hierarchy logic: dark shell + light document apps; light shell + dark code editors. Two bits exist because the design team concluded the same; it's a deliberate combo.
  • Complain about the Settings UI instead of the registry: Settings → Personalization → Colors → Custom exposes both toggles independently already. The registry is for automation, not for surviving without an option.
  • Older Win32 apps take whatever they hard-coded; they were never subscribed. Your theme flip doesn't respone-break paint their pixels.

Live-testing diagnostics: read the values before concluding the tool wrote them — PowerShell diff both befores/afters — and waypoint-app them against the pivot-key primer. Every per-user flip should be a measurement with un-do, not a narrative.

ProofTune ProjectEngineering notes — every claim here names the bytes a real tool touches. Verify first, install second.
ProofTune logo

See these exact settings inside the real tool

The browser replica runs the same strings and states as the installed app — click around before you ever install anything.