Jump to content
Kevin Fulton

Enpass Desktop causing wireless network issues on Windows 10 14393

Recommended Posts

On multiple PCs (Surface Pro 4, Asus UX32VD) that I have running Windows 10 insider preview build 14393 (which will be released to the general public as the Anniversary update very soon), if Enpass Desktop is running (tested with versions 5.2.1 and 5.2.3), it causes cyclic network delays on wireless networks. Every 8-10 seconds, ping times over wireless are greatly increased for 1-3 seconds, and throughput drops to near nothing.

For example, if Enpass is not running, I get between 27-29ms latency when I ping Google DNS.

As soon as I launch Enpass Desktop, this is what I get:

Reply from 8.8.8.8: bytes=32 time=332ms TTL=41
Reply from 8.8.8.8: bytes=32 time=287ms TTL=41
Reply from 8.8.8.8: bytes=32 time=320ms TTL=41
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=74ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=28ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=158ms TTL=41
Reply from 8.8.8.8: bytes=32 time=94ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=111ms TTL=41
Reply from 8.8.8.8: bytes=32 time=294ms TTL=41
Reply from 8.8.8.8: bytes=32 time=358ms TTL=41
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=28ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=349ms TTL=41
Reply from 8.8.8.8: bytes=32 time=474ms TTL=41
Reply from 8.8.8.8: bytes=32 time=85ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=146ms TTL=41
Reply from 8.8.8.8: bytes=32 time=28ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=28ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=236ms TTL=41
Reply from 8.8.8.8: bytes=32 time=125ms TTL=41
Reply from 8.8.8.8: bytes=32 time=280ms TTL=41
Reply from 8.8.8.8: bytes=32 time=449ms TTL=41
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=432ms TTL=41
Reply from 8.8.8.8: bytes=32 time=40ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=226ms TTL=41
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 
Reply from 8.8.8.8: bytes=32 time=27ms TTL=41 

As soon as Enpass is closed, the problem stops and ping times return to normal. This is not just a cosmetic issue. Throughput speeds greatly decrease or hit 0, as tested by speedtest.net, iperf, and the Windows file copy dialog. This problem does not happen when running the UWP Enpass from the Windows Store, only the desktop version. It also does not happen on a wired network connection. 

It took me quite a while to figure out that Enpass was causing my network problems. I really love the Desktop version and would hate to have to stop using it. Any suggestions would be appreciated!

 

Thanks

 

Share this post


Link to post
Share on other sites

I do have exactly the same problem, but with a normal Windows 10 Version (no preview).

I also get those ping peaks and the bandwidth drops as soon as I start Enpass. I've created a video of it so you can see how it looks like:

 

Would be nice if Enpass can fix this as I can't use the application on this computer with this bug.

Share this post


Link to post
Share on other sites

Hi @Kevin Fulton

Thanks for notifying the issue. This is a Qt framework (used by Enpass)  issue. It keeps polling network status every 10 seconds by default. This is reported here:

https://bugreports.qt.io/browse/QTBUG-40332

https://bugreports.qt.io/browse/QTBUG-46015

As a quick solution, add following  environment variable in your system. It will turn off the polling.

QT_BEARER_POLL_TIMEOUT=-1

 

 

  • Like 1

Share this post


Link to post
Share on other sites

I don't know if this was fixed before and came back, but I have been affected by this for the last few weeks. Online games became unplayable until I exited Enpass.

Thank you for the solution. Works fine!

Share this post


Link to post
Share on other sites

Hi there,

I am experiencing this same type of issue on a Windows 7 Home Premium computer. The workaround does not work for me.

Processor: AMD E2-1800 APU
RAM: 4 GB
64-bit operating system

Is there a current workaround for Windows 7 specifically?

Thank you.

Share this post


Link to post
Share on other sites

Thanks for the response @Vinod Kumar,

However the system gets shut down daily, so I know it's not a re-login issue, but it still hasn't been effective.

And as far as I can tell I've imputed it into the system correctly. It freezes the whole computer, even when I don't have much running: Spotify and a few browser taps of chrome. It does it mainly when I go to log into something or if I try to use enpass's autofill feature. Several times it's caused the whole screen to black out and come back on, slowly reloading any windows I had open. 

Any ideas would be appreciated. Thank you.

 

Share this post


Link to post
Share on other sites
On 2/17/2017 at 1:24 AM, Vinod Kumar said:

@Topa Can I see a screen shot of Envrionment variable, so that I can spot a typo just in case?

It's an office computer, so I wasn't sure if it needed to go in both User and System or just one.

Thanks again for your help!

enpassscreengrab.PNG

Share this post


Link to post
Share on other sites

Hi @Topa,

You should set QT_BEARER_POLL_TIMEOUT variable with -1 value. QT_BEARER_POLL_TIMEOUT should come under variable column  and -1 should be under Value column. A screenshot is attached for your reference.

 

Capture.PNG

Share this post


Link to post
Share on other sites

Hi @Gatto

Yes, you have to add an environment variable in your system as mentioned above. This is due to an issue in Qt framework as mentioned in this comment here

On 8/5/2016 at 2:25 PM, Vinod Kumar said:

This is a Qt framework (used by Enpass)  issue. It keeps polling network status every 10 seconds by default. This is reported here:

https://bugreports.qt.io/browse/QTBUG-40332

https://bugreports.qt.io/browse/QTBUG-46015

 

 

 

Share this post


Link to post
Share on other sites

I would not have known this without finding this topic accidentally.

You really should make that a part of your user guide and setup instructions.

Share this post


Link to post
Share on other sites

@Vinod Kumar @Anshu kumar

I have this issue again even when setting the system variable.
As soon as I start Enpass I get those high pings and the network throughput is terrible slow. Sometimes also when Enpass is closed.

I would also like to quote @Vinod Kumar

On 5.8.2016 at 10:55 AM, Vinod Kumar said:

We will fix the same in next release.

As I can see this (for me) big issue hasn't been fixed in over one year. This is unacceptable.

Share this post


Link to post
Share on other sites

Hi @rauppe31,

This issue is related to the Qt framework bug which has not been resolved yet. We tried to hardcode the environment variable, but it keeps on causing sync related issues on some of our test systems. We prefer to wait until the upstream bug has been fixed. However, next major release, Enpass 6 will not use Qt network APIs and will not have this bug.

We are sorry that you have to live with manual workaround for a while.

Share this post


Link to post
Share on other sites

Thanks for your reply.

I could solve my Wifi issues by updating the routers firmware.

The Qt framework fix is still working fine. I'll then wait for Enpass 6 :-)

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×
×
  • Create New...