Windows Firewall Configuration - Truly Block EVERYTHING...

Why don't you use an external update tool and only whitelist this in your firewall?

 

You need to login to view this posts content.

 

@Mr.X: As I understand your suggested tool clap, it uses also the Windows Update Service. So, I think the problem will be the same regarding the svchost IP Adresses for the Updates, right?

 

Don't know, how about you check it for me?

 

Checked it and also not working if you block the svchost.exe (possible because it's using the same MS Routine for the Updates). If you only allow Windows Update Service and BITS full - also not working.
So, this terrible new Updateservice is really not good at all... (for people who whitelist their firewall)

 

My new hero for the day... Seems to work

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

--- I do not know, there will be some difficulties to you, there is no mistake, try again.

 

Already did. Wonder if you how to yield a log to see which ones weren't added.

Although I can do it manually by comparing your ps1 file against wfc rules.

 

--- do it.

 

Problem is these rules. Rules with multiple IPs are not created with the script:

Spoiler

Code:

netsh advfirewall firewall add rule name="telemetry_watson.telemetry.microsoft.com" dir=out action=block remoteip=65.55.252.43,65.52.108.29 enable=yes


netsh advfirewall firewall add rule name="telemetry_redir.metaservices.microsoft.com" dir=out action=block remoteip=194.44.4.200,194.44.4.208 enable=yes


netsh advfirewall firewall add rule name="telemetry_fe2.update.microsoft.com.akadns.net" dir=out action=block remoteip=134.170.58.121,134.170.58.123,134.170.53.29,66.119.144.190,134.170.58.189,134.170.58.118,134.170.53.30,134.170.51.190 enable=yes


netsh advfirewall firewall add rule name="telemetry_feedback.microsoft-hohm.com" dir=out action=block remoteip=64.4.6.100,65.55.39.10 enable=yes


netsh advfirewall firewall add rule name="telemetry_dart.l.doubleclick.net" dir=out action=block remoteip=173.194.113.220,173.194.113.219,216.58.209.166 enable=yes


netsh advfirewall firewall add rule name="telemetry_ads.msn.com" dir=out action=block remoteip=157.56.91.82,157.56.23.91,104.82.14.146,207.123.56.252,185.13.160.61,8.254.209.254 enable=yes


netsh advfirewall firewall add rule name="telemetry_a.ads1.msn.com" dir=out action=block remoteip=198.78.208.254,185.13.160.61 enable=yes


netsh advfirewall firewall add rule name="telemetry_global.msads.net.c.footprint.net" dir=out action=block remoteip=185.13.160.61,8.254.209.254,207.123.56.252 enable=yes

I created the first one manually within WFC gui successfully.

 

--- no error here, will be problem with your WFC driver.

 

Yeah well maybe, I'll add manually and create a partial policy file for WFC lol to backup everything about this telemetry blockage.

 

@anyone using WFC
Could you share your partial policy file to import it to mine? TIA
I'm talking about the rules shared by @shewolf

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

--- in short
--- installs its own service
--- DNS service obligations