windows-internals

Clipboard history is one per-user value — and what that implies

EnableClipboardHistory flips with a DWORD. But the bigger story is what per-user state is store-and-forward: clipboard, sync, and the privacy line between them.

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

The value

HKCU\Software\Microsoft\ClipboardEnableClipboardHistory (DWORD) = 1 for Win+V history; sync-to-cloud is a separate value-pair (CloudClipboard automatic/manual) living alongside it.

The separation that matters

  • History is local, service-backed per account (cbdhsvc per-user service — stop assuming services imply admin; per-user services are a separate class).
  • Cloud sync is off by default; enabling history doesn't secretly sync anything. Distrust conflation: same dialog, distinct bits.
  • Sensitive-data hygiene: clipboard history persists until cleared; build clearing into support guidance for shared-account scenarios.

Model takeaway: per-user features can use services without breaking the no-admin line — the scope rule is about what the service controls, not whether a service object exists. ProofTune's no-service promise, by contrast, is stronger: no agents of any kind, because the product doesn't need them for anything it does.

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.