Windscribe Releases Open-Source PowerShell Script to Remove Microsoft's Persistent Global Device Identifier from Windows

Windscribe has published an open-source PowerShell script called deGDID that removes Microsoft's Global Device Identifier (GDID) from Windows systems and prevents the creation of new identifiers. The persistent tracker survives IP address changes and operates below the VPN layer, allowing Microsoft to maintain device tracking even when users employ privacy tools. The script was developed after the FBI used GDID to identify a suspected hacker, raising concerns about undisclosed device fingerprinting. deGDID modifies registry access control lists and blocks the DeviceAdd interface to stop Windows from regenerating the identifiers after reboots or server contacts. While effective at disabling the tracking mechanism, the tool can break authentication to login.live.com and disrupt certain Microsoft cloud services. It is intended only for unmanaged consumer devices and will not run on domain-joined or corporate-managed systems. The project is described as experimental and cannot delete identifiers already transmitted to Microsoft servers.

AntiMalwareTranslated from Russian

Read at source

Windscribe has released an open-source PowerShell script named deGDID that removes Microsoft's hidden Global Device Identifier from Windows and blocks the operating system from generating replacement identifiers.

The Global Device Identifier is a persistent device fingerprint that remains unchanged when users switch IP addresses and functions below the level of VPN tunnels. Recent reports indicate that this identifier helped the FBI locate a suspected hacker, prompting renewed privacy concerns among Windows users.

The script is distributed via GitHub and must be executed in PowerShell with administrator privileges. Available parameters include -Status to display detected identifiers, -Status -Redact to mask them in diagnostic logs, -Protect to delete stored keys and prevent new ones from being issued, and -Unprotect to restore default settings.

Simply deleting registry entries is insufficient because Windows silently recreates the identifiers after a reboot or contact with Microsoft servers. Therefore deGDID alters registry access control lists, modifies permissions, and blocks the internal DeviceAdd interface so that Microsoft's identification services no longer recognize the computer as a registered device.

After running the script, users may experience partial loss of functionality. During testing, authentication through login.live.com became unavailable in all browsers, while login.microsoftonline.com, online games, and several other applications continued to operate normally. The script cannot remove identifiers that have already been sent to Microsoft.

deGDID is designed exclusively for unmanaged consumer devices. It will refuse to run on corporate or domain-joined systems. Windscribe describes the project as experimental and does not claim it eliminates every trace of the Global Device Identifier.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Privacy & Surveillance

Maximizing iPhone Privacy: Essential Settings to Enable, Disable, and Verify Immediately
Top 10 Secure DNS Servers for Privacy, Threat Blocking and Ad Filtering in 2026
WebRTC IP Leaks Explained: Why Disabling the Protocol Harms Anonymity in Anti-Detect Browsers