Hi.
Skype does not work correctly after the update.
The statuses of users are not displayed, notifications are not received, new messages are not visible.
http://prnt.sc/euv8ht
Skype on my smartphone works without problems.
http://prnt.sc/euv83w
Tried a clean installation of sPortable. Enter login / password and then a long boot and check the input. You can not even see the work area.
http://prnt.sc/ewepol
I returned to version 7.32.0.104 (D:\PortableApps\PortableApps\sPortable\Data\SkypePortableBackup)
Everything works without problems. Messages can be received, statuses are displayed.
Can I temporarily disable the update check for Skype only in the PortableApps Platform?
OS: Microsoft Windows 7 SP1 Ultimate x64 (6.1.7601 Service Pack 1 build 7601)
Previous working version of Skype: 7.32.0.104
Not working version of Skype: 7.34.0.103
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
As mentioned in my earlier comment, sPortable works without issue on both my Windows 10 machine with Skype installed locally and my Windows 7 virtual machine without Skype so it is something specific to your machine. Do you have anything that could be interfering antivirus or firewall wise? Please try copying SkypePortable that is working to another location like your Desktop directory to see if it still works from there. That will help determine if something on your PC is configured to allow it in one location but not in another.
You can rename it to SkypePortableOld and the platform won't update it.
Sometimes, the impossible can become possible, if you're awesome!
Tried to install sPortable on another computer, then PortableAppps Platform downloaded and installed the version of Skype 7.35.0.101 and it works.
In doing so, the firewall asked for permission on the Internet for a new version of Skype.
Does the version of Skype depend on Windows or location?
OS: Windows 10
Windows Firewall whitelists things based on their location.
Sometimes, the impossible can become possible, if you're awesome!
The "Allow unknown connections" mode is enabled in the firewall.
Disconnected completely the firewall - still does not work the new sPortable (Skype).
I tried to directly run the D:\PortableApps\PortableApps\sPortable\App\Skypе\Phone\Skype.exe file - it still asks for a login and password, and then a long boot will not continue.
I conducted the test with the firewall. Enabled interactive mode to see which hosts Skype sends requests to.
Not working skype:
At startup
Tcp: //40.114.149.220 (mobile.pipe.aria.microsoft.com) 443 port
Udp: //157.55.130.153 (dsn5.d.skype.net)
Udp: //157.55.130.153 (dsn5.d.skype.net)
Working Skype:
At startup
Tcp: //191.233.95.169 (a.config.skype.com)
Tcp: //0.0.0.0
Tcp: //65.55.223.24
Udp: //157.55.130.149
After entering login and password:
Tcp: //91.190.219.38 (104.0.32.7.0.rst9.r.skype.net)
Tcp: //64.4.23.150
Tcp: //64.4.23.174
Tcp: //65.55.223.40
Tcp: //157.55.235.169
Tcp: //157.55.130.154
Udp: //111.221.77.145
Udp: //157.55.130.158
Udp: //65.55.223.35
Udp: //111.221.77.175
Udp: //65.55.223.36
Udp: //157.55.130.159
Udp: //157.55.235.161
Udp: //65.55.223.45
Udp: //64.4.23.161
Udp: //157.56.52.43
Udp: //157.55.235.145
Udp: //157.56.52.31
Udp: //157.55.235.150
Udp: //157.55.235.146
Udp: //157.55.56.144
Udp: //157.55.235.147
..................
And other about 20 hosts \ domains
Then I turned on the "Allow all" rule, because there were a lot of requests for access to the hosts.
UPDATE 2017-04-15:
The problem is solved.
The problem is in Skype itself. Perhaps the developers have changed the algorithm for checking IP addresses.
In general, the IP of my computer: 192.168.25.4 (the default working subnet).
Additional subnets: 192.168.0.4 and 192.168.1.4 (for access to another subnet and for configuring routers, GSM gateways). In order not to change the primary IP address every time, I added two other subnets to one network card in my computer.
The old version of Skype defined the main IP address and used it, and the new version of Skype used the first IP address from all my computers on the network card (this is the address 192.168.0.4) and therefore the new version of Skype could not connect to the servers, because on additional subnets There is no gateway and no Internet.
Screenshot of the working version of Skype: http://prnt.sc/ewltqu
Screenshot not working version of Skype: http://prnt.sc/ewltwe
As soon as I removed all the additional IP addresses of the subnets, I restarted the new version of Skype, entered the login / password and immediately connected to the servers and Skype started working.
This error was revealed when I decided to scan the network traffic of Skype (Skype is configured on port 14603) using the Wireshark program.
The firewall did not affect the operation of the new version of Skype.
Maybe someone will benefit from this information in the future.
Thanks to everyone who helped solve the problem