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

Ever want to use Skype again? #79

Closed
aubincc opened this issue Oct 31, 2016 · 15 comments
Closed

Ever want to use Skype again? #79

aubincc opened this issue Oct 31, 2016 · 15 comments

Comments

@aubincc
Copy link

aubincc commented Oct 31, 2016

Hi,

After reinstalling Windows 10 Pro N x64 and using these great Debloat tools, I had trouble using Skype. Not the Entreprise version that comes with the OS, just the regular one.

Well I went to the "hosts" file in "C:\Windows\System32\drivers\etc" and removed the lines where "skype" appeared.

For the users of the Block-Telemetry script, I recommend quoting the lines as follows:

File:

Debloat-Windows-10/scripts/block-telemetry.ps1

Lines:
# "ui.skype.com",
# "pricelist.skype.com"
# "apps.skype.com"

This will save you some trouble. 👍
Have a nice day!

Nicolas / Mole

@pepoweb
Copy link

pepoweb commented Nov 25, 2016

I can second this issue. I have a few Win 10 Pro machines at work who have the same issue.
After the weekend I will try to find a way to reverse this.
Pepo

@pepoweb
Copy link

pepoweb commented Dec 1, 2016

It seems skype also uses c.msn.com So if you have already ran the script you can edit C:\Windows\System32\drivers\etc\hosts and commend out the following lines:
...
”c.msn.com"
...
"ui.skype.com"
"pricelist.skype.com"
"apps.skype.com"
...
Hope this helps.
Pepo

@aubincc
Copy link
Author

aubincc commented Jan 6, 2017

Thank you pepo, you're right, I had forgotten "c.msn.com"

@aubincc aubincc closed this as completed Jan 6, 2017
@jkalousek
Copy link

In my case "s.gateway.messenger.live.com" also caused problems with skype.

@W4RH4WK
Copy link
Owner

W4RH4WK commented May 15, 2017

Should I also comment the line containing "s.gateway.messenger.live.com"?

@majkinetor
Copy link
Contributor

I have all those in my hosts file and my Skype works fine.

Skype 7.35.0.101 , my location Serbia/Belgrade.

@jkalousek
Copy link

jkalousek commented May 15, 2017

(Disclaimer: I'm using this list in pfSense, so on my firewall - which however should not make a difference).
When I put "s.gateway.messenger.live.com" in blocked list, Skype on Windows 7/10 can't go online (it only shows rotating arrows).

Location: Czech Republic
Skype versions: 7.34.0103 (Windows 7) & 7.35.0.103 (Windows 10)

@majkinetor
Copy link
Contributor

Must be location specific then ...

@majkinetor
Copy link
Contributor

My list comes from https://github.com/StevenBlack/hosts

@jkalousek
Copy link

Btw can any of you actually reach "s.gateway.messenger.live.com" with tracert?

Because I get "Unable to resolve target system name s.gateway.messenger.live.com".

@majkinetor
Copy link
Contributor

Looks like aforementioned github project had the same issue:
StevenBlack/hosts#127

@jkalousek
its reachable from http://www.monitis.com/traceroute

@jkalousek
Copy link

Ok, thanks for checking. So it would be good to put comment next to this host so people could find this faster.

W4RH4WK added a commit that referenced this issue May 15, 2017
@madeso
Copy link

madeso commented May 7, 2018

login.live.com caused issues for me logging in to the latest skype classic (desktop version)

@ekr1
Copy link

ekr1 commented Jun 2, 2018

Confirm login.live.com required for Skype (Desktop) on Win10.

@pepoweb
Copy link

pepoweb commented Jun 14, 2018

I can confirm that login.live.com is now also required to login to skype.
After taking that line out of C:\Windows\System32\drivers\etc\hosts, it works again.

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

7 participants