Ill do that.
For the previous request about ipconfig. you may want to check another app I have called IP Changer. I may satisfy your need.
Ill do that.
Thanks, I'll consider adding this.okiedokie400 wrote: ↑Fri Jul 10, 2026 6:28 am Consider add 'Clean Shellbags' to file cleaner.
"Shellbags are hidden Windows registry keys that track your folder viewing preferences, such as window size, icon layout, and view mode (e.g., list vs. details). They are primarily used by digital forensic investigators to reconstruct user activity and uncover deleted, hidden, or external directories.
From an IT security and digital forensics standpoint, Shellbags are highly valuable because they are persistent. Even if a user deletes a folder, unplugs a USB drive, or clears their recent history, the Shellbag entry for that folder usually remains in the Windows registry."
I have been doing it manually it is delete 4 keys-
HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags
HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\BagMRU
HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags
HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\BagMRU
They come back automatically so no further steps required.
=================================================================
Consider adding cleaner for Windows Defender files. There are several files that can be cleaned, like logs and temp files, but it must be done in safe mode. Copy however Bleachbit does this.
Added most stuff that I consider safe to do.okiedokie400 wrote: ↑Sun Jul 12, 2026 4:26 am Potential suggestion for 'Optimize' section with other telemetry disabling.
GDID was a big tech privacy story over the past week. https://www.windowslatest.com/2026/07/1 ... -captures/
Test and copy the mitigations from this repo
First read - https://windowsforum.com/threads/gdid-o ... it.436048/
https://github.com/Korben00/no-gdid
it is to block
'dds.microsoft.com'
'fd.dds.microsoft.com'
'aad.cs.dds.microsoft.com'
'cdpcs.access.microsoft.com'
'geo.prod.do.dsp.mp.microsoft.com'
it is to disable these services
CDPSvc -> Disabled (via Set-Service)"
DoSvc -> Disabled (via registry Start=4; SCM denies Set-Service)"
CDPUserSvc -> Disabled (stop first in services menu, then set registry Start=4)"
https://github.com/SmtimesIWndr/gdid-reversal
Reducing the exposure
The GDID exists because your device is registered into the Microsoft Account device graph and the Connected Devices Platform keeps it synced. To cut it back:
Kill the Connected Devices Platform (CDPSvc, CDPUserSvc) and turn off Activity History (Settings, Privacy, Activity history) to stop the graph sync and the activity uploads.
I have been testing some of these mitigations - blocking those addresses, and disabling both CDP services. It says it breaks Phone Link / "Continue on PC", and nearby sharing, but I dont use those functions so I have not noticed any issues with having those services disabled. CDP services seem to be the primary agreed upon services to disable to break functionality of GDID. PC still updates normally.