25 lines
3.8 KiB
Markdown
25 lines
3.8 KiB
Markdown
# Additional Windows privacy channels and tool findings
|
|
|
|
Reviewed 19 September 2026. These additions concern documented features and investigation leads. They are not discoveries of previously undisclosed surveillance mechanisms.
|
|
|
|
## Beyond the GDID screenshot
|
|
|
|
Keep the original complaint's attribution and the two research repositories' confidence levels distinct. The source review and workbook already track those claims. Additional controls should be justified by the function producing a connection, rather than by treating every Microsoft destination as equivalent.
|
|
|
|
- **Connectivity probes:** NCSI sends connectivity tests and influences applications' view of network availability. Disabling it can create false offline status and application problems. A private probe endpoint is a possible managed-network option, not a universal anonymity feature. Treat this as optional and verify the exact edition/build. [NCSI overview](https://learn.microsoft.com/en-us/windows-server/networking/ncsi/ncsi-overview).
|
|
- **Certificate trust:** trusted and disallowed certificate information is security maintenance. Fully offline designs need a separate refresh path. Clearing certificates or turning off validation would undermine the protection we want to retain. [Microsoft trust-list guidance](https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/configure-trusted-roots-disallowed-certificates).
|
|
- **Windows Error Reporting:** fault reports are distinct from an application's own telemetry. Reducing optional diagnostics does not configure every third-party reporter. Use vendor-specific controls and keep bounded local diagnostics useful for repair. [WER overview](https://learn.microsoft.com/en-us/windows/win32/wer/windows-error-reporting).
|
|
- **Activation, Store licensing and update eligibility:** treat these as separate dependencies. Offline update selection must not assume that a package is licensed or applicable merely because its filename contains the right Windows version. Do not implement activation bypasses.
|
|
- **Names on local networks:** hostname discovery, LLMNR/mDNS, NetBIOS and sharing warrant a separate local-network inventory. This is a planned investigation, not a claim that all those channels reach Microsoft. Avoid breaking printers or local discovery blindly.
|
|
- **Cached credentials and tokens:** identity-provider state is not an ordinary disposable temp cache. Deleting it can affect login, licensing and recovery. The proposed retention module excludes credentials and identity stores; the GDID script review explains why deleting a CDP cache does not prove remote deletion.
|
|
|
|
## Additional GitHub comparisons
|
|
|
|
| Project | Finding | Decision |
|
|
| --- | --- | --- |
|
|
| [LeDragoX/Win-Debloat-Tools](https://github.com/LeDragoX/Win-Debloat-Tools) | Archived 3 October 2025; README scopes its last supported builds and warns that removal may not be easily reversed | Historical reference; exclude from current deployment |
|
|
| [HotCakeX/Harden-Windows-Security](https://github.com/HotCakeX/Harden-Windows-Security) | Security hardening and App Control resources; recommendations include connected Microsoft services | Review individual security controls to preserve protections. Do not adopt its entire recommendation set as a privacy profile |
|
|
| [DavidXanatos/wumgr](https://github.com/DavidXanatos/wumgr) | Windows update-management project described for Windows 10 | Management UI is not an anonymity boundary. Current Windows 11/ESU applicability and update behavior need testing before selection |
|
|
|
|
Together with the previous register, these make 19 tool/research entries. None of these projects was executed. The best-fit design remains a small supported-policy layer, optional dependency-aware app removal, measured network enforcement, and a distinct offline-maintenance option for users who need no direct Microsoft contact.
|