Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Update check doesn't work #62

Closed
Gittyperson opened this issue May 30, 2017 · 13 comments
Closed

Windows Update check doesn't work #62

Gittyperson opened this issue May 30, 2017 · 13 comments
Assignees

Comments

@Gittyperson
Copy link

Gittyperson commented May 30, 2017

A few times it might work, but usually results in: "We couldn't connect to the update service. We'll try again later..." or an endless "Checking for updates...". When disabling the rules found in data/firewall/win10/spy.txt, it works again.

Windows 10 Pro 64 bit

@crazy-max crazy-max self-assigned this May 30, 2017
@daveimagery
Copy link

Me too, just noticed it. Thank you

@Atavic
Copy link

Atavic commented May 30, 2017

@Gittyperson @daveimagery Can you both report the IP that's blocked?

EDIT: @crazy-max Request was for the issuer. Who opens issues should give more feedback!

@crazy-max
Copy link
Owner

Yes, i keep you in touch

@Atavic
Copy link

Atavic commented May 31, 2017

On a sidenote, the IP checked by updates changes from the location of the caller; - so an update from a different continent than the one where @crazy-max did this research may definitely change - moreover the same calls change due to network optimizations.

An IP like 207.46.7.252 hosts a gateway that manages various services as OneDrive or MSN Search. So you may encounter a blocked IP because it is related to other services.

@crazy-max
Copy link
Owner

@Atavic Thanks for your feedback!
There is already an issue concerning geolocation. Can you tell me the IP address you have detected for Windows Update?

@Atavic
Copy link

Atavic commented May 31, 2017

I do offline updates! I just had a look at your list. By looking at the first series of the IP, I see there's 20 ASN involved:

13...
23...
40...
51...
52...
64...
65...
66...
77...
104...
111...
131...
134...
137...
157...
168...
191...
195...
207...
213...

@crazy-max
Copy link
Owner

Ok, i think i have found the problem. Can you remove these IPs and tell me if it works ?

  • 40.113.8.255
  • 51.141.32.51
  • 52.187.60.107
  • 207.46.7.252
  • 207.46.101.29
  • 207.46.153.155
  • 207.46.194.40

@crazy-max
Copy link
Owner

And maybe this one too : 66.119.144.*

crazy-max pushed a commit that referenced this issue Jun 1, 2017
Error parsing OpenWRT data (Issue #63)
Move 66.119.144 to update for Windows 10 (Issue #62)
Move 207.46 to extra for Windows 10 (Issue #15)
@crazy-max
Copy link
Owner

Can you try the latest release (4.4.1) ?

@Gittyperson
Copy link
Author

Gittyperson commented Jun 1, 2017

Tested it once right now and it worked.

update: sorry no, it failed but perhaps for other reasons. I'll try again later.

@crazy-max
Copy link
Owner

Ok i keep it open for the moment

@Gittyperson
Copy link
Author

It worked now so I assume there's no problem.

crazy-max added a commit that referenced this issue Nov 22, 2017
Error parsing OpenWRT data (Issue #63)
Move 66.119.144 to update for Windows 10 (Issue #62)
Move 207.46 to extra for Windows 10 (Issue #15)
@Atavic
Copy link

Atavic commented Mar 19, 2018

the IP checked by updates changes from the location of the caller

...and OS version, see: #104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants