Does this only apply to the Preview builds or the RTM versions? or both? Last I heard MSFT was only applying this to the insider and tech builds but released a public statement that they would not have it in the RTM version.
This about RTM, who cares about Previews atm, they are frozen. Even if you opt out of Insider-Program and disable all by hand, there will be a lotta communication. Some also want to get rid of all as far as possible ... for those is the thread.
It must be clear in; Search & Cortana: Microsoft-Windows-Search2-WOW64-base-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-base-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-shell-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-shell-Package~31bf3856ad364e35~amd64~~10.0.10240.16384
Using windows command line is more effective for example route ADD 157.56.124.101 MASK 255.255.255.255 192.168.1.208 Anybody know how to block whole ranges this way? Explorer.exe connects to lots of addresses on these ranges. 156.56 156.57 so a command to block the range 157.56.0.0 - 157.57.255.255 would be nice.
bing.com msedge.net watson.live.com microsoft-hohm.com microsoft-hohm.com a973.g.akamai.net a973.g.akamai.net a569.g.akamai.net a569.g.akamai.net a1095.g2.akamai.net a1095.g2.akamai.net db3aqu.atdmt.com db3aqu.atdmt.com db3aqu.atdmt.com db3aqu.atdmt.com w3.b.cap-mii.net a1961.g.akamai.net a1961.g.akamai.net a1856.g2.akamai.net a1856.g2.akamai.net cs1.wpc.v0cdn.net any.edge.bing.com c.msn.com.nsatc.net g.msn.com.nsatc.net m.anycast.adnxs.com m.anycast.adnxs.com m.anycast.adnxs.com ui.skype.akadns.net dns.msftncsi.com act-3-blu.mesh.com m.anycast.adnxs.com m.anycast.adnxs.com m.anycast.adnxs.com m.anycast.adnxs.com m.anycast.adnxs.com a-0001.a-msedge.net ads.msn.com.nsatc.net c.atdmt.com.nsatc.net atlas.c10r.facebook.com a-0002.a-msedge.net a-0003.a-msedge.net a-0004.a-msedge.net a-0005.a-msedge.net a-0006.a-msedge.net a-0007.a-msedge.net a-0008.a-msedge.net a-0009.a-msedge.net bn1cd.wns.windows.com telemetry.microsoft.com rad.msn.com.nsatc.net aidps.msn.com.nsatc.net ssw.live.com.nsatc.net e4593.g.akamaiedge.net flex.msn.com.nsatc.net ssw.live.com.nsatc.net e9946.g.akamaiedge.net dart.l.doubleclick.net e8011.g.akamaiedge.net e7173.g.akamaiedge.net secure.anycast.adnxs.com secure.anycast.adnxs.com secure.anycast.adnxs.com secure.anycast.adnxs.com bn1-2cd.wns.windows.com df.telemetry.microsoft.com bs.eyeblaster.akadns.net secure.anycast.adnxs.com secure.anycast.adnxs.com secure.anycast.adnxs.com secure.anycast.adnxs.com bn2wns1.wns.windows.com bn2wns1b.wns.windows.com login.live.com.nsatc.net login.live.com.nsatc.net login.live.com.nsatc.net login.live.com.nsatc.net login.live.com.nsatc.net login.live.com.nsatc.net compatexchange.cloudapp.net login.live.com.nsatc.net skyapi.skyprod.akadns.net skyapi.skyprod.akadns.net skyapi.skyprod.akadns.net skyapi.skyprod.akadns.net siweb.microsoft.akadns.net ads2.msn.com.c.footprint.net skyapi.skyprod.akadns.net skyapi.skyprod.akadns.net skyapi.skyprod.akadns.net skyapi.skyprod.akadns.net t.urs.microsoft.com.nsatc.net survey.watson.microsoft.com ads2.msn.com.c.footprint.net schemas.microsoft.akadns.net choice.microsoft.com.nsatc.net wes.df.telemetry.microsoft.com sqm.df.telemetry.microsoft.com watson.microsoft.com.nsatc.net ads2.msn.com.c.footprint.net fesweb1.ch1d.binginternal.com static-2mdn-net.l.google.com BN1WNS2011508.wns.windows.com global.msads.net.c.footprint.net global.msads.net.c.footprint.net global.msads.net.c.footprint.net support.msn.microsoft.akadns.net global.msads.net.c.footprint.net activesync.glbdns2.microsoft.com watson.ppe.telemetry.microsoft.com global.msads.net.c.footprint.net msnbot-65-55-108-23.search.msn.com vortex-cy2.metron.live.com.nsatc.net sls.update.microsoft.com.akadns.net fe2.update.microsoft.com.akadns.net fe2.update.microsoft.com.akadns.net fe2.update.microsoft.com.akadns.net fe2.update.microsoft.com.akadns.net fe2.update.microsoft.com.akadns.net vortex-bn2.metron.live.com.nsatc.net win10.ipv6.microsoft.com.nsatc.net win10.ipv6.microsoft.com.nsatc.net bl3302.storage.skyprod.akadns.net oca.telemetry.microsoft.com.nsatc.net sqm.telemetry.microsoft.com.nsatc.net statsfe2.ws.microsoft.com.nsatc.net fe2.update.microsoft.com.akadns.net statsfe1.ws.microsoft.com.nsatc.net directory.services.live.com.akadns.net directory.services.live.com.akadns.net vortex-hk2.metron.live.com.nsatc.net reports.wes.df.telemetry.microsoft.com corpext.msitadfs.glbdns2.microsoft.com statsfe2.update.microsoft.com.akadns.net fe2.update.microsoft.com.akadns.net fe2.update.microsoft.com.akadns.net services.wes.df.telemetry.microsoft.com vortex-sandbox.data.glbdns2.microsoft.com diagnostics.support.microsoft.akadns.net watson.telemetry.microsoft.com.nsatc.net onesettings-cy2.metron.live.com.nsatc.net onesettings-bn2.metron.live.com.nsatc.net fe3.delivery.dsp.mp.microsoft.com.nsatc.net telemetry.appex.search.prod.ms.akadns.net bn1.skype.msnmessenger.msn.com.akadns.net onesettings-hk2.metron.live.com.nsatc.net fe3.delivery.dsp.mp.microsoft.com.nsatc.net onesettings-db5.metron.live.com.nsatc.net telecommand.telemetry.microsoft.com.nsatc.net settings-sandbox.data.glbdns2.microsoft.com legacy-redirection-westus-prod-hp.cloudapp.net legacy-redirection-eastus-prod-hp.cloudapp.net 204.79.197.200 204.79.197.197 207.46.223.94 64.4.6.100 65.55.39.10 96.6.122.184 96.6.122.218 96.6.122.216 96.6.122.144 96.6.122.67 96.6.122.73 94.245.121.177 94.245.121.178 94.245.121.176 94.245.121.179 216.38.172.128 96.6.122.169 96.6.122.224 96.6.122.67 96.6.122.74 93.184.215.200 204.79.197.200 65.52.108.11 65.52.108.27 68.67.152.94 68.67.153.87 68.67.153.37 157.56.109.8 131.107.255.255 65.55.194.241 68.67.152.174 68.67.152.173 68.67.152.110 68.67.152.120 68.67.152.172 204.79.197.200 157.56.23.91 65.52.108.11 31.13.74.2 204.79.197.201 204.79.197.203 204.79.197.206 204.79.197.204 204.79.197.208 204.79.197.209 204.79.197.210 204.79.197.211 157.56.96.80 65.52.100.9 65.52.108.251 65.52.108.3 207.46.7.252 23.211.228.52 131.253.40.47 207.46.101.29 23.222.166.121 216.58.217.198 23.222.170.100 23.222.169.232 68.67.129.45 68.67.129.53 68.67.129.47 68.67.129.61 157.56.96.208 65.52.100.7 12.129.210.71 68.67.128.234 68.67.128.231 68.67.128.235 68.67.128.215 131.253.34.230 65.52.108.254 131.253.61.80 131.253.61.68 131.253.61.84 131.253.61.96 131.253.61.66 131.253.61.82 23.99.10.11 131.253.61.100 134.170.111.72 134.170.111.24 134.170.111.96 134.170.111.48 134.170.185.70 8.254.11.126 134.170.104.168 134.170.104.160 134.170.104.152 134.170.104.176 65.55.176.90 207.68.166.254 8.254.172.254 65.54.226.187 157.56.91.77 65.52.100.93 65.52.100.94 65.55.252.71 205.128.73.252 131.253.14.76 216.58.217.198 157.56.100.83 8.27.243.253 8.254.11.126 8.253.38.126 157.55.129.21 8.254.172.254 157.56.17.248 65.52.100.11 205.128.73.252 65.55.108.23 64.4.54.254 157.56.77.139 191.232.80.58 65.55.138.126 65.55.138.114 207.46.114.58 65.55.138.112 65.55.44.109 94.245.121.251 157.56.144.215 134.170.107.224 65.55.252.63 65.55.252.93 134.170.115.60 23.103.189.158 134.170.115.60 65.55.52.23 65.55.52.56 111.221.29.254 65.52.100.91 65.55.29.238 64.4.54.22 134.170.165.249 134.170.165.253 65.52.100.92 64.4.54.32 157.56.57.5 65.55.252.43 64.4.54.253 65.55.44.108 64.4.54.18 168.61.24.141 157.56.108.82 111.221.29.253 65.52.108.90 191.232.139.253 65.55.252.92 111.221.29.177 23.101.196.141 137.117.100.176
Thanks! taking a look, it might be a bit drastic to block that large range, from my findings Microsoft for sure is connecting explorer to these ranges 157.56.124.0 - 157.56.124.255 157.55.236.0 - 157.55.236.255 I will block these, then once it panics at not being able to connect on those it will probably move to 157.56.125 etc etc. these are the ones I noted that explorer.exe had connected to. Code: 157.55.236.29 157.55.236.40 157.55.236.44 157.55.236.66 157.55.236.89 157.55.236.92 157.55.236.101 157.55.236.101 157.55.236.110 157.55.236.147 157.55.236.166 157.56.124.30 157.56.124.38 157.56.124.38 157.56.124.55 157.56.124.73 157.56.124.95 157.56.124.101 157.56.124.102 157.56.124.126 157.56.124.132 157.56.124.154 157.56.124.208 157.56.124.219
The path must be the root folder where you mounted using DISM. It works for me. For me was C:\WIN\1 because I mounted it on C:\WIN and then \1 because it creates a folder with the index number.
@s1ave77 A small tip : No need to remove these packages individually Code: Microsoft-Windows-Search2-base-Package~31bf3856ad364e35~amd64~en-US~10.0.10240.16384 Microsoft-Windows-Search2-base-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Search2-Package~31bf3856ad364e35~amd64~en-US~10.0.10240.16384 Microsoft-Windows-Search2-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Search2-shell-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384 Microsoft-Windows-Search2-shell-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Code: Microsoft-Windows-Search2-WOW64-base-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-base-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-shell-Package~31bf3856ad364e35~amd64~it-IT~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-shell-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Removing the below two packages alone will remove the rest of the packages Code: Microsoft-Windows-Search2-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Search2-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 Also when you remove any main package then it will remove the associated language packages for e.g. : If you remove this main package : Code: Microsoft-Windows-Search2-Package~31bf3856ad364e35~amd64~~10.0.10240.16384 then it remove its associated en-US package too Code: Microsoft-Windows-Search2-Package~31bf3856ad364e35~amd64~en-US~10.0.10240.16384
Will it be better if i block those ips in my router's firewall, instead of using the domains in the hosts file?
abcdef12, I would say yes. the reason being is that there seem to be certain DLL's that "whitelist" domains from being blocked via hosts file.