Jump to content

About disabling Aero Glass by Creators Update


Recommended Posts

14 hours ago, raiden89 said:

NoelC is paranoid with a tinfoil hat lmao.

Not just him, many guys around here think in the same way, LOL

14 hours ago, raiden89 said:

especially when its not supported by BM yet, as he's stated multiple times in this thread.

BM was the one that sent that "test version" to NoelC, so that version it is supported by BM.

Link to comment
Share on other sites


Hey, my hat is custom machined titanium with gold leaf!  :)  Hey, if they don't have any of my data, they can't abuse it. 

I logged what sites the  v1703 Creator's Update system tried to contact just after updating my fully private v1607 Anniversary setup and choosing the most private settings in the "privacy configuration" provided by Microsoft...   Some of these are legitimate security certificate servers, but the rest...  You decide whether all these comms are necessary or wanted.

crl.thawte.com A resolved from Forwarding Server as 23.4.181.163
crl.usertrust.com A resolved from Cache to 178.255.83.2
crl.usertrust.com A resolved from Forwarding Server as 178.255.83.2
ctldl.windowsupdate.com A resolved from Cache to 118.214.160.178
ctldl.windowsupdate.com A resolved from Forwarding Server as 118.214.160.178
dev.virtualearth.net A resolved from Forwarding Server as 65.52.108.59
dns.msftncsi.com A resolved Locally to 131.107.255.255
download.windowsupdate.com A resolved from Forwarding Server as 118.214.160.200
download.windowsupdate.com A resolved from Forwarding Server as 8.253.165.248
ecn.dev.virtualearth.net A resolved from Forwarding Server as 23.50.229.80
fe2.update.microsoft.com A resolved from Cache to 134.170.53.29
fe2.update.microsoft.com A resolved from Forwarding Server as 134.170.53.29
fe2.update.microsoft.com A resolved from Forwarding Server as 134.170.58.118
fe2.update.microsoft.com A resolved from Forwarding Server as 191.232.80.62
fe2.update.microsoft.com A resolved from Forwarding Server as 23.103.189.158
fs.microsoft.com A resolved from Forwarding Server as 23.50.230.187
g.live.com A resolved from Forwarding Server as 65.52.108.27
g2.symcb.com A resolved from Forwarding Server as 23.4.187.27
gn.symcd.com A resolved from Forwarding Server as 23.4.187.27
insiderppe.cloudapp.net A resolved from Forwarding Server as 52.168.24.174
login.live.com A resolved from Cache to 131.253.61.84
login.live.com A resolved from Forwarding Server as 131.253.61.84
ocsp.comodoca.com A resolved from Forwarding Server as 178.255.83.1
ocsp.digicert.com A resolved from Forwarding Server as 72.21.91.29
ocsp.msocsp.com A resolved from Forwarding Server as 198.41.214.185
ocsp.thawte.com A resolved from Forwarding Server as 23.4.187.27
ocsp.usertrust.com A resolved from Forwarding Server as 178.255.83.1
ocsp.verisign.com A resolved from Forwarding Server as 23.4.187.27
oneclient.sfx.ms A resolved from Forwarding Server as 23.50.230.130
settings-win.data.microsoft.com A --- blacklisted by DNS server ---
sls.update.microsoft.com A resolved from Forwarding Server as 157.55.240.220
sls.update.microsoft.com A resolved from Forwarding Server as 157.56.77.140
sls.update.microsoft.com A resolved from Forwarding Server as 157.56.77.141
t0.ssl.ak.dynamic.tiles.virtualearth.net A resolved from Forwarding Server as 23.50.228.135
t0.ssl.ak.tiles.virtualearth.net A resolved from Forwarding Server as 23.50.229.84
th.symcb.com A resolved from Forwarding Server as 23.4.181.163
th.symcd.com A resolved from Forwarding Server as 23.4.187.27
time.nist.gov A resolved from Forwarding Server as 128.138.141.172
time.nist.gov A resolved from Forwarding Server as 216.229.0.179
v10.vortex-win.data.microsoft.com A --- blacklisted by DNS server ---
www.microsoft.com A resolved from Forwarding Server as 23.0.87.187
www.msftconnecttest.com A resolved from Forwarding Server as 13.107.4.52

Since booting up my re-tweaked system and letting it run this morning, it contacted these sites:

dns.msftncsi.com A resolved Locally to 131.107.255.255
On ‎4‎/‎21‎/‎2017 at 10:48 AM, dhjohns said:

Ya think?  But he's still a good guy.

Thanks dhjohns.  We butt heads from time to time, but I think the same of you.

-Noel

Link to comment
Share on other sites

Hey whatever the OS wants to contact is OK.  I keep the viruses out, but I want my OS to operate as intended.  I do realize that some people do not like communication, but I am fine with it.  All is good.  I am running build 16184 with Aeroglass 1.4.6.  No transparency, but my 3rd party themes are right.  No message boxes at startup from aeroglass stating incompatibility.  No water marks.  I do not expect any build I am using to have any transparency on the borders again since BM does not support Insider Previews, but I am alright with that.  Just so long as there are no errors or anything.  Aeroglass is a royal pain anyway.  The colors seem to change when I switch themes, and since I like the borders of windows in the foreground to be the same color as the ones in the background, it can be a real headache.  But, like I said, I have a very nice setup with the newest Insider Preview.  I think it works much better than the Creators Update.  My themes work very well, and all is good.

Link to comment
Share on other sites

  • 2 months later...
On 4/22/2017 at 0:30 AM, carlitosoo555 said:

Not just him, many guys around here think in the same way, LOL

BM was the one that sent that "test version" to NoelC, so that version it is supported by BM.

Um, could the rest of us get this funcioning "test version" as well? :/

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...