Jump to content

Windscribe Pro 1.81


freeforever03

Recommended Posts

freeforever03

I have been using Windscribe Pro for several months and am happy with the VPN. Recently the program update from version 1.80 to version 1.8.1. This update has caused a serious problem on my Windows 10 (32 bit OS) that has forced me to revert back to version 1.80. Basically, when I turn on the VPN, I get 100% cpu usage. The usage spreads across three main program processes: 1. Managed Machine Service 2. Acronis Active Protection Service 3. Cybereason RansomFree. I've looked on-line and couldn't find any good information. Therefore, I thought I would ask if anyone here has encountered this problem or know of a solution. Thanks.

Link to comment
Share on other sites


  • Replies 3
  • Views 1.1k
  • Created
  • Last Reply

whilst i haven't noticed your issue myself (or i've forgotten) i did find that connectivity was hit and miss with v1.81+, i've reverted back to v1.80.33 a few times  (usually withing an hour) as the VPN options are much simpler. connecting to US EAST, WEST or CENTRAL is exactly that, whereas the new versions specify other counties (local ISP exchanges) which aren't really needed as US EAST, WEST + CENTRAL worked. maybe later on when websites ban VPN's they may be of use, but not at the moment

 

as a temporary fault finder/ fix, try disabling most or all non-microsoft startup programs,and run Windscribe on its own and see if there's a difference. if there is, start to re-enable what you disabled, if not revert back to v1.80

Link to comment
Share on other sites


freeforever03

Thank you for your suggestion. After a little investigation, it looks like BD Anti Ransomware,  Cybereason Anti Ransomware and Acronis Protection Service are incompatible with the latest version of Windscribe. They obviously changed something that causes these anti ransomware programs to react.

Link to comment
Share on other sites


freeforever03

I contacted Windscribe and this is what they said:

 

This is a bug in Acronis (and Plex, qBittorrent, and some other apps). It doesn't handle forcible TCP socket termination, which 1.81 does now. No other VPN does this, but without this feature, existing connections can linger for a while, bypassing the VPN tunnel.
We're gonna add a setting in the next version to turn off this feature, but keep in mind, existing apps may leak your IP. In the mean time, you can install the old version if you wish.


Yegor Sak
Founder

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

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