Windscribe Releases Open-Source PowerShell Script to Remove Microsoft's Persistent Global Device Identifier from Windows
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.
Related articles
WhatsApp Adds Support for Multiple Passkeys on Single Account
WhatsApp has expanded its account protection features by allowing users to register more than one passkey on the same profile. The update particularly benefits users who switch between Android and iOS devices while maintaining phishing-resistant login methods. Passkeys replace traditional codes and passwords with biometric authentication, facial recognition, or device lock mechanisms. Meta reports that more than one billion people already use the feature on WhatsApp, with Android support introduced in 2023 and iOS support added in 2024. The change reduces reliance on a single device during authentication by associating multiple keys with one account. Users can manage keys through Settings > Account > Passkeys. WhatsApp has also strengthened two-factor verification by allowing replacement of the six-digit PIN with longer passwords containing letters, numbers, and special characters.
Russian ISPs Begin Disrupting Encrypted DNS Services from Google and Cloudflare
Users of several major Russian internet providers have reported widespread issues accessing encrypted DNS protocols offered by Google and Cloudflare. The affected services include DNS over HTTPS (DoH) and DNS over TLS (DoT), which are designed to prevent providers from inspecting domain queries. Measurements show that connections to Cloudflare addresses 1.1.1.1 and 1.0.0.1 on port 853 establish TCP handshakes but are then reset with ECONNRESET errors before TLS authentication completes. Google Public DNS endpoints experience different interference, with sessions stalling after the TLS ClientHello or terminating with unexpected EOF errors. The disruptions have been observed across Rostelecom, Dom.ru, Tattelecom, and SkyNet subscribers, with varying impact depending on region and operator. Tattelecom support reportedly advised one customer to disable both protocols to restore connectivity. No official confirmation of centralized blocking has been issued, yet the coordinated pattern across multiple providers suggests deliberate interference rather than random failure.
DuckDuckGo Study Shows Users Confide Sensitive Personal Details in AI Chatbots Without Realizing Data Retention
A new DuckDuckGo survey reveals that chatbots have evolved from simple search tools into digital confidants where users disclose highly personal information. Nearly one in three AI users admitted sharing details they would not discuss with friends, family, colleagues, or doctors. The figure rises sharply to 56 percent among users who describe themselves as strong AI enthusiasts. The research underscores that many people remain unaware that AI systems store and can later reference these conversations. This behavior creates significant privacy risks as conversational data becomes part of long-term model memory. The findings highlight a growing gap between user expectations and the actual data-handling practices of AI platforms.
Telegram Desktop Adds WEB Proxy to Hide MTProxy Traffic Inside HTTPS and WebSocket Connections
Telegram Desktop has received an initial implementation of a new WEB proxy designed to conceal messenger connections within ordinary HTTPS and WebSocket traffic. The feature makes user activity appear as simple website browsing to network providers while MTProxy continues to operate underneath. Developers inserted more than 3,000 lines of code, including a dedicated WEB-proxy transport, domain configuration options, and interface elements such as “Open browser” and “Waiting for browser.” The mechanism works by opening an embedded web page that establishes a secure WebSocket link to a domain resembling a regular site. Multiple MTProxy connections are multiplexed into a single stream and sent through this channel. On the server side an intermediate node demultiplexes the stream and forwards the individual connections to a standard MTProxy instance without decrypting message content.