← Back
Tracking Breakdown

Privacy script breaks Microsoft services

A new script from Windscribe removes Microsoft's hidden tracking but breaks some core services.
By
Person uses laptop at desk with "Core Privacy Tools" display visible on monitor.
Foto: Symbolbild | outrank.so · Symbolbild (Bildsuche: laptop running Windows with privacy software interface) - nicht das Originalfoto der Quelle.
The essentials
  • Windscribe created a script called 'deGDID' to erase Microsoft's tracking IDs in Windows.
  • The script breaks Microsoft account authentication and some cloud services.
  • It works by deleting and blocking the creation of Global Device Identifier (GDID) keys.
  • The script only functions on non-domain-managed systems with admin rights.

A well-known virtual private network (VPN) provider named Windscribe has crafted a script known as 'deGDID' that targets the removal of Microsoft's Global Device Identifier (GDID) from Windows systems. This hidden tracking feature embeds itself into the operating system, and deGDID works by erasing existing GDID keys and ensuring they cannot be recreated. However, this privacy-focused tool comes with a trade-off—it can interfere with the normal functioning of some Microsoft cloud-based services.

The deGDID script tackles the problem at multiple points in the Windows system. It starts by adjusting critical registry entries and access control lists (ACLs) to prevent the system from retrieving and re-issuing GDID keys. In addition, it blocks the 'DeviceAdd' internal endpoint, which stops Microsoft from recognizing the device as part of the Windows ecosystem. This two-step strategy ensures existing keys are purged and new ones cannot be generated. But it's important to note that server-side keys, which already reside with Microsoft, remain untouched. Also, users must run the script with admin privileges, and it only functions on unmanaged systems. For enterprise or domain-joined PCs, deGDID is not compatible.

Testing the Script's Efficacy

Windscribe conducted tests on a Windows 11 machine and confirmed the script worked as intended. By using the –Protect flag, all existing GDID keys were removed, and a fresh reboot did not generate new ones. The team also tested the –Status flag, which identified cached keys before removal. Despite these successes, some Microsoft services, such as apps and account verification via login.live.com, failed to connect and returned errors. However, other Microsoft services like login.microsoftonline.com and online gaming platforms continued to operate without disruption.

The need for deGDID stems from the fact that Windows provides no built-in option to disable GDID. This device identifier operates at a system level, meaning it can track user activity across different IP addresses, even when a person uses a virtual private network. This type of persistent tracking can pose serious privacy concerns, especially if the data is misused or accessed without user consent. Windscribe claims the script is an ongoing research initiative, with the team expecting to expand and refine deGDID further as more details about GDID emerge.

Potential Consequences for Users

However, for many users, the script's consequences may outweigh its benefits. By blocking Microsoft's ability to recognize the device, deGDID disrupts some essential Windows features, including cloud authentication and application functionality. This brings up an important consideration for privacy-focused users: what are you willing to sacrifice for enhanced privacy? Windscribe acknowledges that the current version of deGDID may not be ideal for all users. It does not eliminate every GDID instance, and Microsoft may still retain access to older keys. That said, it remains a valuable step in the ongoing battle against hidden tracking systems.

Ultimately, deGDID represents a significant effort to reclaim user privacy in an ecosystem that often prioritizes convenience over security. For those who place their data privacy above all else, the tool offers a compelling, if imperfect, solution. But for the average user, the decision to deploy deGDID will likely depend on whether the loss of some Microsoft services is a price worth paying for a cleaner, more private computing experience.

The script is freely available on GitHub and can be executed using PowerShell. It is designed with multiple command-line flags to suit different scenarios, including checking the system's status, redacting GDID data from logs, and restoring the device to its default state if needed. This flexibility allows users to tailor the script to their needs, although the –Protect flag is by far the most impactful in eliminating tracking.

Looking Ahead in the Privacy Debate

As the conversation around digital privacy continues to evolve, efforts like deGDID demonstrate the growing demand for transparency and control over personal data. While Microsoft remains a dominant force in the tech industry, solutions like Windscribe's script remind users that they have the tools—and the responsibility—to take a stand against invasive tracking mechanisms.

Person uses laptop at desk with "Core Privacy Tools" display visible on monitor.
Running the deGDID script · Foto: Future
Person uses laptop at desk with "Core Privacy Tools" display visible on monitor.
Running the deGDID script · Foto: Future
Person uses laptop at desk with "Core Privacy Tools" display visible on monitor.
Microsoft online services degraded after running the deGDID script · Foto: Future
The other side

Microsoft has not commented on deGDID, but the company's own documentation suggests GDID is used for device management and account tracking. Users may find the script too disruptive for their needs.

Frequently asked questions

What is Microsoft's GDID?

GDID is a persistent identifier in Windows used by Microsoft to track devices. It cannot be removed through standard user settings.

What happens if I run deGDID?

Running deGDID removes existing GDID keys and blocks new ones from being created, but it breaks some Microsoft cloud services like account verification.

Does deGDID work on all Windows systems?

No, deGDID only works on unmanaged systems with admin accounts. It will not run on domain-joined or managed systems.

Based on reporting by Tom's Hardware, compiled by the Tradingbird newsroom. Published 06 Aug 2026, 14:06.
Read this in: English · Arabiy · Deutsch · Espanol · Italiano · Portugues · Russkij · Turkce