Windows ID Verification is Here

Summary

The video argues that Microsoft is introducing mandatory age/identity verification (“ID verification”) into Windows setup, making it harder to use Windows without providing personal identification.

Update referenced

The creator claims the change was introduced with Windows cumulative update KB5079473 (dated March 10, 2026). They say the public changelog focuses on other improvements—such as Windows Defender Application Control and AI-related components (e.g., image search/content extraction/semantic analysis)—but omits a hidden “ID verification” capability.

How the feature allegedly works

The presenter demonstrates that after running an administrative command, Windows re-enters OOBE (out-of-box experience) and, during setup, shows an age verification screen:

• “Please verify your age”…
• A Copilot prompt instructing the user to hold an ID up to the camera
• In their test environment, because no camera is available, the Continue button is disabled, preventing normal completion

Discovery of the mechanism

They state that using Process Monitor, they traced the command’s effect to setting a registry policy value under:

• HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Identity Verify

They describe values such as:

• “IDV Policy Enabled”
• An “IDV policy level”
• A UUID-like telemetry identifier

Attempts to modify or delete these entries are reported as blocked by permissions/controls, suggesting enforcement is intentional.

Workarounds described (not fully disabling the policy)

The creator claims the age-verification screen can be bypassed by:

1. Activating the built-in Administrator account:
   • net user administrator active: yes
2. Rebooting and using what they call the “second chance OOBE/alternative flow”

They also mention the existence of a protection mechanism that interferes with resetting/deleting the relevant registry values (described as a driver Microsoft previously used to prevent third-party browsers from setting themselves as default).

Privacy concern

The presenter highlights that Microsoft appears to repurpose ClipSVC (Client License Service)—associated with Microsoft Store DRM—as part of the ID/verification workflow. They frame this as evidence of an expanding collection of sensitive data, arguing that forced identity verification is a major threat to digital privacy.

Call to action / broader prediction

They conclude by warning that forced ID verification could roll out widely, and advocate “Say no to age verification,” suggesting support for alternatives (e.g., Linux).

Presenters / Contributors

• Video creator/presenter (no name given in the subtitles)
• Mentioned: Flight Tech (referenced by the presenter as assisting in tracing/testing)