I’m guessing the utility does exactly that, but during the installation.
The developer claims it only does what Windows own hidden configuration tools do.
Call me the human test pilot.
![]()
I have not tried a ‘debloated’ Windows installation.
The only thing I do is to run msconfig and turn off some services and autoruns.
On the other hand, I have a very, very sophisticated firewall installation that prevents my system from sending data to a whole bunch of IPs.
When I first started looking into this, I was completely shocked by the constant stream of ‘calls’ to the mothership made by a whole bunch of applications.
The hardest part was to isolate and whitelist calls that are actually required.
Indeed.
If (and that’s a big “if”) the debloat utility does what the dev says - which is essentially creating a Windows LTSC installation - then I have to believe that necessary procedural calls would remain intact. The aspect of it I’m most unsure of is the Xbox authentication.
We’ll see…
Lord knows I’ve been wrong before. ![]()
@kido007dz - you running Pi-Hole or using firewall rules to block?
Pihole is one component (>2.5 million domains blacklisted, i.e. approx 27% of queries blocked in the past 24 hours across several clients with diverse OSs).
I also run two instances of pfsense, one locally, one in the cloud, with site 2 site tunneling using specific extensions and a whole bunch of rules.
It’s layers…