Resolving an unusual wifi issue


Late last year, I started experiencing some unusual intermittent connection issues on my Desktop. In general, I had a stable connection with average latency; however, at (seemingly) random times throughout the week, I would start experiencing sudden 2000ms+ latency spikes every couple of seconds.

Screenshot of intermittent latency spikes while pinging

This made all audio/video calling software unusable and most online games unplayable.

This issue appeared to line up with my cross-country move from Washington State to South Carolina, so there were too many factors to easily pinpoint the issue. However, as it mainly only effected gaming and audio/video calls, I didn’t put too much focus on it.

Over the past couple of months I have (slowly) tried to figure out why this was happening, with little luck until today.


Initially, the only thing that was clear about the issue was that it was limited to my desktop computer only. My laptop and other devices connected to the wifi did not have this issue, even when placed in the exact same spot as the desktop.

First, I purchased a new, highly-reviewed, wifi adapter on Amazon. It didn’t resolve the issue. It did, however, come with an offer for a free 64GB flash drive in exchange for a good reviews.

(That was a pretty terrible purchase overall) screenshot of a free flash drive offer, in exchange for a good review

Later, (for unrelated reasons) I built an entirely new desktop computer, not using anything from the old one, except the new wifi adapter. This included a fresh install of Windows 10.

It was great, this new computer had no issues! I had suspected that my old motherboard’s USB ports might have been damaged during the move to SC, so that must have been the case. Everything is good now, right?

No. Everything is not good now.

A few weeks later, and the issue suddenly began happening on the new computer also, and I had no idea what the cause could be.

I tried using multiple different wifi adapters that I owned.

I tried changing the wifi channel, as it appeared to overlap a neighbors.

I tried turning off Windows Update Delivery Optimization (p2p update sharing). After turning this off and restarting, the issue appeared to be resolved, but then reappeared later.

At one point, my wifi issue even annoyed one of my brothers so badly, due to dropping Skype calls, that he bought me another (slightly less sketchy) wifi adapter on Amazon. This appeared to temporarily resolve the issue after installing the Realtek driver and restarting, but then it came back.

Amazon gift message from my brother: “ANDREW FIX YOUR FUCKING WIFI PLEASE DEAR GOD IMPORTANT: Install Realtek 8812au driver from Realtek website NOT manufacturer website”

Nothing seemed to work.

Today, in a last-ditch desperate attempt at fixing the issue, I:

The issue stopped.

I immediately suspected interference from the wireless drawing tablet or box fan, so tried those again, but they were not the cause.

I couldn’t possibly imagine how a web browser or drawing application could cause this, but I tried anyway.

First I ran FireFox, opened multiple tabs on different sites, and waited…


Then I ran MediBang Paint Pro.

another ping lag spike


Why the hell would digital painting software cause wifi lag spikes?

As it turns out, there are multiple instances of people complaining about this issue with MBPP.

If we take a quick look with ProcMon, we can see that it’s definitely doing something odd.

screenshot of procmon filter

screenshot of procmon log, showing MediBangPaintPro.exe querying the network interface registry keys

At the exact same time the lag spikes occur, MBPP starts querying the registry keys for all of you network interfaces.

To dig a bit deeper into why this is happening, we can attach to the process with a debugger (x64dbg here), and set breakpoints on the Win32 Reg* APIs.

screenshot of x64dbg registry API breakpoints

Eventually, our RegOpenKeyExInternalW breakpoint is hit, and we can take a look at the call stack to determine where this is being called.

screenshot of x64dbg callstack

Looking at the call stack, we can see that first non-system library in the callstack is qt5network.

Surprisingly, no more debugging is needed, as a quick google search for “q5network ping issue” will lead you to QTBUG-40332.

If I understand correctly, any Qt5 (<5.14) application using QNetworkAccessManager will check for wifi interface changes every 10 seconds for the purpose of bearer management, causing massive lag spikes and/or packet drops entirely. Even if QNetworkAccessManager is instantiated internally for something simple, like an HTTP request.

I suppose the workaround is simple enough, set the environment variable QT_BEARER_POLL_TIMEOUT to -1.

I just wish I knew that around 8 months ago.


Qt5 has been crippling my wifi system-wide for past 7-8 months, just by running MediBang Paint Pro. I stupidly attributed it to many other things, because, honestly, who would expect Qt to be the cause of their system-wide wifi problems?