windows-internals

Snap layouts live in the per-user hive too

Snap assist, hover-to-show layouts, and zone persistence are HKCU values. For multimonitor dwellers these are the highest-return changes per byte you can make.

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

The values

…\Explorer\Advanced\EnableSnapBar
Snap layout strip shown on a dragged window against a screen edge
…\Explorer\Advanced\EnableSnapAssistFlyout
hovering Maximize shows the grid chooser
…\Explorer\Advanced\DITest… family
zone memory for restoring snapped sets across sleeps/restarts

All documented per-user, restart-Explorer semantics, zero machine coupling.

Why these change real days

  • Hover-flyout trims the cognitive click-count per arrangement; for tiling-heavy work it re-couples poorly transferred habits from FancyZones without a new runtime.
  • Consistency note: FancyZones' layout editor writes its own settings elsewhere — the two systems stack cleanly but have separate “what persists” conventions.
  • Where performance meets window management: disabling shell animations can make Snap feel snappier without touching layout memory — combine only deliberately.

Per-user means per-habit: your colleague's machine keeps stock Snap; yours becomes the institutional knowledge you came for.

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.