Deletes all instances of Microsoft's GDID and prevents minting of new ones
Source Entity
Hacker News
The 'degdid' project provides a tool to remove Microsoft's Global Device Identifier (GDID) from Windows systems. It specifically targets the server-assigned 64-bit device PUID to prevent further tracking and minting of this identifier.
Understanding the GDID and the degdid Initiative
The release of the degdid PowerShell script marks a significant development in the field of Windows privacy hardening. At its core, the project addresses the Global Device Identifier (GDID), a server-assigned 64-bit Device PUID (Platform Unique Identifier) that Windows systems acquire through Microsoft's 'DeviceAdd' infrastructure. Unlike traditional telemetry, which often relies on user-level activity, the GDID operates at the machine level, allowing the operating system to maintain a unique identity even when a user is logged in via a local account rather than a Microsoft account.
The Mechanics of GDID Persistence
The degdid repository clarifies that the GDID is not merely a transient token; it is a persistent identifier retained across multiple local identity stores within the Windows architecture. By interacting with the DeviceAdd infrastructure, the system ensures that even if a user attempts to remain anonymous or offline, the OS can facilitate server-side tracking via this hardware-linked identifier. The degdid.ps1 script functions as a 'completion gate,' specifically designed to purge these existing server-issued states and actively block the re-minting process.
Scope and Operational Focus
It is essential to distinguish the scope of this tool from broader privacy-focused software. The developers behind degdid explicitly state that this is not a general-purpose telemetry suppression tool, nor does it claim to mitigate browser-based tracking or other court-record-channel communication. Instead, it is a surgical intervention aimed exclusively at the GDID lifecycle. By removing the identifier from known local stores, the script effectively neuters the machine's ability to present a pre-authorized, server-tracked identity to Microsoft's backend services.
Broader Implications for Privacy Engineering
This project highlights a growing trend in 'practical hardening'—a niche field of cybersecurity focused on reducing the 'fingerprintability' of modern operating systems. As Windows integrates more deeply with cloud-based identity services, the ability for a local user to opt out of machine-level tracking becomes increasingly difficult. The existence of degdid serves as a proof-of-concept for users who wish to exert granular control over their hardware's digital identity, challenging the assumption that server-assigned identifiers are permanent, immutable characteristics of a Windows installation.
Future Trends in System Identity
Looking forward, the tension between OS-level identity management and user privacy is likely to intensify. As Microsoft continues to evolve its DeviceAdd infrastructure, tools like degdid will likely require constant maintenance to remain effective. This reflects a broader industry trend where privacy-conscious users and researchers are forced to engage in a continuous 'cat-and-mouse' game with operating system developers regarding the collection of persistent hardware identifiers. The degdid repository serves as a critical resource for those attempting to maintain system-level autonomy in an increasingly connected computing environment.