QBittorrent.exe leaves zombie process after exit. Cause: KB4338818 #7498

Author

Owner

@Dobatymo commented on GitHub (Jul 13, 2018):

I had this happen also. Sometimes after the close qBittorrent the processes remains (probably 20% of the time). And I usually wait up to one hour for it to close by itself as I know this sometimes can take some time.
Usually the process will still still show some activity (CPU, IO) and usually I can kill the process.
Sometimes (only recently) however the process cannot be killed using the task manager and the only way indeed is to restart Windows.

It could be related to the latest Windows updates like YuryMatveev mentions, as I only saw this behaviour very recently and I was using 4.1.1 since it was released.

Windows 7 x64, qBittorrent 4.1.1

Edit: newest uTorrent shows the same issue.

@Dobatymo commented on GitHub (Jul 13, 2018): I had this happen also. Sometimes after the close qBittorrent the processes remains (probably 20% of the time). And I usually wait up to one hour for it to close by itself as I know this sometimes can take some time. Usually the process will still still show some activity (CPU, IO) and usually I can kill the process. Sometimes (only recently) however the process cannot be killed using the task manager and the only way indeed is to restart Windows. It could be related to the latest Windows updates like YuryMatveev mentions, as I only saw this behaviour very recently and I was using 4.1.1 since it was released. Windows 7 x64, qBittorrent 4.1.1 Edit: newest uTorrent shows the same issue.

deekerman commented

Author

Owner

@YuryMatveev commented on GitHub (Jul 13, 2018):

There wasn't this bug for me before latest win7 updates. So, probably it's because of .Net 4.7.2 latest updates on 2018-07-11.
Also, I can start the second qbittorrent.exe process that works normally, except for magnet/.torrent file fetching. Manual add torrent still works in this case.
PS: updated reproducing

@YuryMatveev commented on GitHub (Jul 13, 2018): There wasn't this bug for me before latest win7 updates. So, probably it's because of .Net 4.7.2 latest updates on 2018-07-11. Also, I can start the second qbittorrent.exe process that works normally, except for magnet/.torrent file fetching. Manual add torrent still works in this case. PS: updated reproducing

deekerman commented

Author

Owner

@OrpheusXx commented on GitHub (Jul 14, 2018):

After i closed Qbittorrent normally, it stays in the processes, but not eating up that much ram, than normally would.
I can't start Qbittorrent, nor kill it via process explorer.
I just noticed that long after closing bittorrent, something like 30+ minutes i was still seeding some torrents on a private tracker, less and less as time goes on. (this is kind of normal, but not sure what time after closing Qb is considered normal)
After that tracker showed 0 seeds by me i could restart Qbittorrent, but could not kill the process still.
I have ~900 torrents in total, some somewhat big.

Another wierd problem i started having recently, not sure if it's related to this problem:
I had the green connection icon on fresh windows start on the bottom before closing Qb, now after restarting it i have the yellow icon.
(downloading only works sometimes and seeding is not working and adding new torrents is wierd, only by dropping the .torrent file into Qb or opening the magnet link inside Qb works. Tracker site says i'm seeding, but there are 0 traffic) Only a computer restart fixes it, whatever it is..

@OrpheusXx commented on GitHub (Jul 14, 2018): After i closed Qbittorrent normally, it stays in the processes, but not eating up that much ram, than normally would. I can't start Qbittorrent, nor kill it via process explorer. I just noticed that long after closing bittorrent, something like 30+ minutes i was still seeding some torrents on a private tracker, less and less as time goes on. (this is kind of normal, but not sure what time after closing Qb is considered normal) After that tracker showed 0 seeds by me i could restart Qbittorrent, but could not kill the process still. I have ~900 torrents in total, some somewhat big. Another wierd problem i started having recently, not sure if it's related to this problem: I had the green connection icon on fresh windows start on the bottom before closing Qb, now after restarting it i have the yellow icon. (downloading only works sometimes and seeding is not working and adding new torrents is wierd, only by dropping the .torrent file into Qb or opening the magnet link inside Qb works. Tracker site says i'm seeding, but there are 0 traffic) Only a computer restart fixes it, whatever it is..

deekerman commented

Author

Owner

@Scias90 commented on GitHub (Jul 14, 2018):

I'm having the exact same issue. The process will not die in task manager, and after the initial boot up, once closed. It will not boot back up afterwards. I, too, updated Windows just the previous day.

Hopefully qbittorrent comes out with an update to fix this.

@Scias90 commented on GitHub (Jul 14, 2018): I'm having the exact same issue. The process will not die in task manager, and after the initial boot up, once closed. It will not boot back up afterwards. I, too, updated Windows just the previous day. Hopefully qbittorrent comes out with an update to fix this.

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 14, 2018):

I can also confirm this issue with the same OS and version as @YuryMatveev.

@Smithy3 commented on GitHub (Jul 14, 2018): I can also confirm this issue with the same OS and version as @YuryMatveev.

deekerman commented

Author

Owner

@YuryMatveev commented on GitHub (Jul 14, 2018):

If it will be helpful, here's what ProcessExplorer shows

I tend to think this situation is only when qbittorrent is a child process of Firefox, that loads it by magnet/torrent link click, and then exit Firefox.

C:>taskkill /F /T /IM qbittorrent.exe
ERROR: The process with PID 2612 (child process o PID 4088) could not be terminated.
Reason: There is no running instance of the task.

@YuryMatveev commented on GitHub (Jul 14, 2018): If it will be helpful, here's what ProcessExplorer shows ![qbittorrent](https://user-images.githubusercontent.com/18564442/42729581-ed9ae1b2-87e4-11e8-9675-f474290c7fd3.png) I tend to think this situation is only when qbittorrent is a child process of Firefox, that loads it by magnet/torrent link click, and then exit Firefox. C:\>taskkill /F /T /IM qbittorrent.exe ERROR: The process with PID 2612 (child process o PID 4088) could not be terminated. Reason: There is no running instance of the task.

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 14, 2018):

I doubt it has much to do with Firefox, I'm getting the same issue on a machine that doesn't even have it installed.

@Smithy3 commented on GitHub (Jul 14, 2018): I doubt it has much to do with Firefox, I'm getting the same issue on a machine that doesn't even have it installed.

deekerman commented

Author

Owner

@YuryMatveev commented on GitHub (Jul 14, 2018):

Then Chrome/other browser, that loads it as a child process. Anyway, the issue is with qbittorrent.
Never though that there can be unkillable process under WinNT, though looks like this is it:
https://blogs.technet.microsoft.com/markrussinovich/2005/08/17/unkillable-processes/

@YuryMatveev commented on GitHub (Jul 14, 2018): Then Chrome/other browser, that loads it as a child process. Anyway, the issue is with qbittorrent. Never though that there can be unkillable process under WinNT, though looks like this is it: https://blogs.technet.microsoft.com/markrussinovich/2005/08/17/unkillable-processes/

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 15, 2018):

I added a torrent via File > Add Torrent Link and the issue still persists, so I think its safe to assume its completely unrelated.

Just based on the contents of this issue and my own experience I would guess its something to do with the latest Windows update, as this wasn't an issue a few days ago before the update, and qBittorrent hasn't been updated since May. I wonder if it can be fixed on qBittorrent's end or whether its Microsoft's problem.

~~Just for some more info, Transmission is unaffected.~~
Actually, it is. As @Zealand69 says, all torrent clients must be affected.

@Smithy3 commented on GitHub (Jul 15, 2018): I added a torrent via `File > Add Torrent Link` and the issue still persists, so I think its safe to assume its completely unrelated. Just based on the contents of this issue and my own experience I would guess its something to do with the latest Windows update, as this wasn't an issue a few days ago before the update, and qBittorrent hasn't been updated since May. I wonder if it can be fixed on qBittorrent's end or whether its Microsoft's problem. ~~Just for some more info, Transmission is unaffected.~~ Actually, it is. As @Zealand69 says, all torrent clients must be affected.

deekerman commented

Author

Owner

@Zealand69 commented on GitHub (Jul 15, 2018):

I to am having the same issue, have had NET 4.7.2 update, running Win7 x64.
It seems I'm not just having these issues with QBittorrent but with other Torrent clients as well (uTorrent, Bit torrent).

@Zealand69 commented on GitHub (Jul 15, 2018): I to am having the same issue, have had NET 4.7.2 update, running Win7 x64. It seems I'm not just having these issues with QBittorrent but with other Torrent clients as well (uTorrent, Bit torrent).

deekerman commented

Author

Owner

@jonskeee commented on GitHub (Jul 15, 2018):

Can confirm same issue happening to me.
I'd press the power off button on my PC and head to bed, then wake up in the morning to find my PC still attempting to shutdown with qBittorent still attempting to close :(

@jonskeee commented on GitHub (Jul 15, 2018): Can confirm same issue happening to me. I'd press the power off button on my PC and head to bed, then wake up in the morning to find my PC still attempting to shutdown with qBittorent still attempting to close :(

deekerman commented

Author

Owner

@bargergo commented on GitHub (Jul 15, 2018):

I have this problem, but I haven't installed NET 4.7.2 update, yet.
Win7 x64
qBittorrent 4.1.1 64 bit
I enabled AutoEndTasks in the registry as a temporary solution, so that the system can shutdown.

@bargergo commented on GitHub (Jul 15, 2018): I have this problem, but I haven't installed NET 4.7.2 update, yet. Win7 x64 qBittorrent 4.1.1 64 bit I enabled AutoEndTasks in the registry as a temporary solution, so that the system can shutdown.

deekerman commented

Author

Owner

@Mor9 commented on GitHub (Jul 15, 2018):

Have issue like user jonskeee.
Cant kill process and system cant close qbittorrent after shutdown without user action.
This other discussion of problem https://github.com/qbittorrent/qBittorrent/issues/8157

Upd.
System windows 7 x64. Past version QB ~3.20, try last version result is same. Try different settings, no effect (Version x86-x64, torrent queueing all 100).
Like this client and donate to dev before. Now maybe have to leave app to time until fix this issue.
In shutdown screen write "Saving torrent progress..." and dont nothing happen, PC not shutdown. Process QB after that cant kill. Have about 45 distributions, active ~6.
Start it about a week before.

@Mor9 commented on GitHub (Jul 15, 2018): Have issue like user jonskeee. Cant kill process and system cant close qbittorrent after shutdown without user action. This other discussion of problem https://github.com/qbittorrent/qBittorrent/issues/8157 Upd. System windows 7 x64. Past version QB ~3.20, try last version result is same. Try different settings, no effect (Version x86-x64, torrent queueing all 100). Like this client and donate to dev before. Now maybe have to leave app to time until fix this issue. In shutdown screen write "Saving torrent progress..." and dont nothing happen, PC not shutdown. Process QB after that cant kill. Have about 45 distributions, active ~6. Start it about a week before.

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 15, 2018):

I wonder if https://github.com/qbittorrent/qBittorrent/issues/8157 is actually the same issue though, most people here are reporting that the problem only stared a few days ago while that issue was made months ago, not to mention how this is affecting all clients.

As https://github.com/qbittorrent/qBittorrent/issues/8157#issuecomment-354565704 says, it could be an issue with libtorrent?

@Smithy3 commented on GitHub (Jul 15, 2018): I wonder if https://github.com/qbittorrent/qBittorrent/issues/8157 is actually the same issue though, most people here are reporting that the problem only stared a few days ago while that issue was made months ago, not to mention how this is affecting all clients. As https://github.com/qbittorrent/qBittorrent/issues/8157#issuecomment-354565704 says, it could be an issue with libtorrent?

deekerman commented

Author

Owner

@zeule commented on GitHub (Jul 15, 2018):

#5097

@zeule commented on GitHub (Jul 15, 2018): #5097

deekerman commented

Author

Owner

@YuryMatveev commented on GitHub (Jul 15, 2018):

@zeule

#5097
If I want to start qBittorrent again I have to kill the old process in the task manager.

This is surely another type of bug, because it's unkillable by all means.

@YuryMatveev commented on GitHub (Jul 15, 2018): @zeule > #5097 > If I want to start qBittorrent again I have to kill the old process in the task manager. This is surely another type of bug, because it's unkillable by all means.

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 15, 2018):

@zeule
It sounds like a very similar issue but this literally only started a few days ago for me and the only thing that changed in that time was that I ran a Windows update. Also as @YuryMatveev says, you can't kill the process.

@Smithy3 commented on GitHub (Jul 15, 2018): @zeule It sounds like a very similar issue but this literally only started a few days ago for me and the only thing that changed in that time was that I ran a Windows update. Also as @YuryMatveev says, you can't kill the process.

deekerman commented

Author

Owner

@zeule commented on GitHub (Jul 15, 2018):

Maybe the problem is the same (pending DNS requests), but the app can't be killed because of a change in the recent Windows update?

@zeule commented on GitHub (Jul 15, 2018): Maybe the problem is the same (pending DNS requests), but the app can't be killed because of a change in the recent Windows update?

deekerman commented

Author

Owner

@n-o-o-b commented on GitHub (Jul 15, 2018):

I have the same but mine can be killed by Task Manager. It's just annoying that it leaves a process there - I have to manually end it if I want to open qBit again after exiting. This doesn't always happen but quite frequently does.

Edit: Actually, right now I have a thing where I exited qBit and it's not in Task Manger under Processes but I can't open it again. Maybe related?

@n-o-o-b commented on GitHub (Jul 15, 2018): I have the same but mine can be killed by Task Manager. It's just annoying that it leaves a process there - I have to manually end it if I want to open qBit again after exiting. This doesn't always happen but quite frequently does. Edit: Actually, right now I have a thing where I exited qBit and it's not in Task Manger under Processes but I can't open it again. Maybe related?

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 15, 2018):

but I can't open it again.

Yes, that should be related to this issue. I think.

@Smithy3 commented on GitHub (Jul 15, 2018): >but I can't open it again. Yes, that should be related to this issue. I think.

deekerman commented

Author

Owner

@zoocey commented on GitHub (Jul 15, 2018):

Issue is due to a bug in the latest Microsoft Patches, e.g. KB4338818 for Windows 7. And is affecting other programs see: https://forum.filezilla-project.org/viewtopic.php?f=6&p=163932 and https://www.reddit.com/r/sysadmin/comments/8z08yf/some_processes_not_closing_after_windows_update/

@zoocey commented on GitHub (Jul 15, 2018): Issue is due to a bug in the latest Microsoft Patches, e.g. KB4338818 for Windows 7. And is affecting other programs see: https://forum.filezilla-project.org/viewtopic.php?f=6&p=163932 and https://www.reddit.com/r/sysadmin/comments/8z08yf/some_processes_not_closing_after_windows_update/

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 15, 2018):

Ah, so it was a Windows update issue.
Thanks a lot for the information.

Microsoft is working on a resolution and estimates a solution will be available mid-July.

@Smithy3 commented on GitHub (Jul 15, 2018): Ah, so it was a Windows update issue. Thanks a lot for the information. >Microsoft is working on a resolution and estimates a solution will be available mid-July.

deekerman commented

Author

Owner

@ygfytf commented on GitHub (Jul 15, 2018):

Soooo, forsake a Windows Security Update in favor of qbtorrent?
Why don't I turn off my firewall and shut of my anti virus as well? .....
Maybe I'll just poke my eye out with a sharp stick instead.

@ygfytf commented on GitHub (Jul 15, 2018): Soooo, forsake a Windows Security Update in favor of qbtorrent? Why don't I turn off my firewall and shut of my anti virus as well? ..... Maybe I'll just poke my eye out with a sharp stick instead.

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 15, 2018):

No one is telling you to uninstall it, they're simply pointing out what the problem is and what the current solution for it is, which is uninstalling that update.

From what I understand Microsoft is aware of the issue and an update should be out soon anyway.

No need to be so melodramatic.

@Smithy3 commented on GitHub (Jul 15, 2018): No one is telling you to uninstall it, they're simply pointing out what the problem is and what the current solution for it is, which is uninstalling that update. From what I understand Microsoft is aware of the issue and an update should be out soon anyway. No need to be so melodramatic.

deekerman commented

Author

Owner

@natalik commented on GitHub (Jul 16, 2018):

I was about to format my computer until I saw this, the same issue happened to me, I have Windows 7 and thought it was utorrent 2.2.1, I uninstalled it and installed qbitorrent same thing and as you said the only change was windows latest update,

@natalik commented on GitHub (Jul 16, 2018): I was about to format my computer until I saw this, the same issue happened to me, I have Windows 7 and thought it was utorrent 2.2.1, I uninstalled it and installed qbitorrent same thing and as you said the only change was windows latest update,

deekerman commented

Author

Owner

@philippemorindotca commented on GitHub (Jul 16, 2018):

Well I found a "workaround" when I saw that this might be a pending DNS issue. I just unplugged my network cable and it shutdown the app when I lost connection. Not great but hey, when task manager fails...

@philippemorindotca commented on GitHub (Jul 16, 2018): Well I found a "workaround" when I saw that this might be a pending DNS issue. I just unplugged my network cable and it shutdown the app when I lost connection. Not great but hey, when task manager fails...

deekerman commented

Author

Owner

@Mor9 commented on GitHub (Jul 17, 2018):

Big thanks for solution of this problem. Remove KB until microsoft not fix this.

@Mor9 commented on GitHub (Jul 17, 2018): Big thanks for solution of this problem. Remove KB until microsoft not fix this.

deekerman commented

Author

Owner

@Scias90 commented on GitHub (Jul 17, 2018):

And now Transmission-qt has the same problem. Can't kill the process and now I'll have to restart my pc every time I want to use it.

Windows needs to patch this asap, this is ridiculous.

@Scias90 commented on GitHub (Jul 17, 2018): And now Transmission-qt has the same problem. Can't kill the process and now I'll have to restart my pc every time I want to use it. Windows needs to patch this asap, this is ridiculous.

deekerman commented

Author

Owner

@jonskeee commented on GitHub (Jul 19, 2018):

Installed KB4338821 seems to have fixed it for me

@jonskeee commented on GitHub (Jul 19, 2018): Installed [KB4338821](https://support.microsoft.com/en-us/help/4338821/july242018kb4338821osbuildpreviewofmonthlyrollup) seems to have fixed it for me

deekerman commented

Author

Owner

@dosudosu commented on GitHub (Jul 19, 2018):

Can confirm KB4338821 fixed it for me too.

@dosudosu commented on GitHub (Jul 19, 2018): Can confirm [KB4338821](https://support.microsoft.com/en-us/help/4338821/july242018kb4338821osbuildpreviewofmonthlyrollup) fixed it for me too.

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 19, 2018):

I can also confirm KB4338821 fixed this.

@Smithy3 commented on GitHub (Jul 19, 2018): I can also confirm KB4338821 fixed this.

deekerman commented

Author

Owner

@OrpheusXx commented on GitHub (Jul 19, 2018):

Installed KB4338821, now i can kill Qb via process explorer, and it starts again, ~~but Qb doesn't seem to be working properly now, barely seeding anything, just before installing this update everything worked fine.~~

~~And my previous problem->websites sometimes (but a lot less frequent, then before) not loading at all (couldn't connect to host/host not found or something like that) is back.~~

Now it seems fine, but not really since...
Browsing is noticable slower tho, and sometimes sites can't load, seeding is wierd also, much less torrents are seeded now, speed is all over the place.

@OrpheusXx commented on GitHub (Jul 19, 2018): Installed KB4338821, now i can kill Qb via process explorer, and it starts again, ~~but Qb doesn't seem to be working properly now, barely seeding anything, just before installing this update everything worked fine.~~ ~~And my previous problem->websites sometimes (but a lot less frequent, then before) not loading at all (couldn't connect to host/host not found or something like that) is back.~~ Now it seems fine, but not really since... Browsing is noticable slower tho, and sometimes sites can't load, seeding is wierd also, much less torrents are seeded now, speed is all over the place.

deekerman commented

Author

Owner

@Smithy3 commented on GitHub (Jul 19, 2018):

Its probably just placebo.

Also, you shouldn't need to kill off qBittorrent using the task manager, it closes down properly now after a few seconds.

@Smithy3 commented on GitHub (Jul 19, 2018): Its _probably_ just placebo. Also, you shouldn't need to kill off qBittorrent using the task manager, it closes down properly now after a few seconds.

deekerman commented

Author

Owner

@sledgehammer999 commented on GitHub (Jul 19, 2018):

Thank you all guys for hunting it down to the wrong/correct KB installs.
I think we can close this now.

@sledgehammer999 commented on GitHub (Jul 19, 2018): Thank you all guys for hunting it down to the wrong/correct KB installs. I think we can close this now.

deekerman commented

Author

Owner

@zenden2k commented on GitHub (Jul 19, 2018):

I had the same issue on Windows 8.1 64 bit and qBt 4.1.1 64 bit.
I ran Windows Update and manually installed KB4338831 (Preview of Monthly Rollup for Windows 8.1). After two attemps it had been installed. Now my computer shuts down correctly

@zenden2k commented on GitHub (Jul 19, 2018): I had the same issue on Windows 8.1 64 bit and qBt 4.1.1 64 bit. I ran Windows Update and manually installed KB4338831 (Preview of Monthly Rollup for Windows 8.1). After two attemps it had been installed. Now my computer shuts down correctly

deekerman commented

Author

Owner

@AdKiller commented on GitHub (Sep 14, 2019):

same problem started happening after adding about 2000 torrents. when I had only 100 torrents qb would always close quickly.

now after clicking exit it stays in the task manager most of the times. once I waited 2 hours and it was still stuck... (none of these issues ever happen in the 10 years old utorrent 2.0.4!!! you guys should just reverse engineer that and copy what they did and trash qbittorrent)

qb 4.1.7 64bit
Windows 10 Pro 1803 64bit (installed up to August 2019 security updates)

@AdKiller commented on GitHub (Sep 14, 2019): same problem started happening after adding about 2000 torrents. when I had only 100 torrents qb would always close quickly. now after clicking exit it stays in the task manager most of the times. once I waited 2 hours and it was still stuck... (none of these issues ever happen in the 10 years old utorrent 2.0.4!!! you guys should just reverse engineer that and copy what they did and trash qbittorrent) qb 4.1.7 64bit Windows 10 Pro 1803 64bit (installed up to August 2019 security updates)

deekerman commented

Author

Owner

@remcobob commented on GitHub (Sep 30, 2019):

Win10 Pro ver1903 - Same problem. When I restart, on closing QBT is still trying to save status and it may be 10-15 minutes after I closed it,. Even if I pause all activity and wait for the u/d to read zero and then close, it still hangs. Kind of a pain. It doesn't show in task manager.

Most recent update also.

@remcobob commented on GitHub (Sep 30, 2019): Win10 Pro ver1903 - Same problem. When I restart, on closing QBT is still trying to save status and it may be 10-15 minutes after I closed it,. Even if I pause all activity and wait for the u/d to read zero and then close, it still hangs. Kind of a pain. It doesn't show in task manager. Most recent update also.

deekerman commented

Author

Owner

@section32 commented on GitHub (Oct 24, 2019):

Win 10 Po 1903 here also, started getting this issue recently. new torrents don't show up until after the app has been restarted. speed drops to zero on active torrents. close the app works but leaves a process in task manager and only a reboot resolves it.

@section32 commented on GitHub (Oct 24, 2019): Win 10 Po 1903 here also, started getting this issue recently. new torrents don't show up until after the app has been restarted. speed drops to zero on active torrents. close the app works but leaves a process in task manager and only a reboot resolves it.

deekerman commented

Author

Owner

@remcobob commented on GitHub (Oct 24, 2019):

10/24/2019 - It's gone away. I went back to an older version of Norvpn and that took care of it. I won't let NVPN update anymore. If I do update it again, I'll keep the old version just in case.

@remcobob commented on GitHub (Oct 24, 2019): 10/24/2019 - It's gone away. I went back to an older version of Norvpn and that took care of it. I won't let NVPN update anymore. If I do update it again, I'll keep the old version just in case.

deekerman commented

Author

Owner

@TheBigBentley commented on GitHub (Nov 19, 2019):

Windows 10 1903 and I have this issue.

@TheBigBentley commented on GitHub (Nov 19, 2019): Windows 10 1903 and I have this issue.

deekerman commented

Author

Owner

@remcobob commented on GitHub (Nov 19, 2019):

I had this problem and it was the updated NordVpn. I went back to an
earlier version and it went away

On Tue, Nov 19, 2019 at 7:07 PM TheBigBentley notifications@github.com
wrote:

Windows 10 1903 and I have this issue.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/qbittorrent/qBittorrent/issues/9190?email_source=notifications&email_token=AH7CZHLNE2IHTLPTXPHFGD3QUSSYLA5CNFSM4FJ6WK6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEQRKYQ#issuecomment-555816290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH7CZHJ3WMMEDRDE67VAWVDQUSSYLANCNFSM4FJ6WK6A
.

@remcobob commented on GitHub (Nov 19, 2019): I had this problem and it was the updated NordVpn. I went back to an earlier version and it went away On Tue, Nov 19, 2019 at 7:07 PM TheBigBentley <notifications@github.com> wrote: > Windows 10 1903 and I have this issue. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/qbittorrent/qBittorrent/issues/9190?email_source=notifications&email_token=AH7CZHLNE2IHTLPTXPHFGD3QUSSYLA5CNFSM4FJ6WK6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEQRKYQ#issuecomment-555816290>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AH7CZHJ3WMMEDRDE67VAWVDQUSSYLANCNFSM4FJ6WK6A> > . >

deekerman commented

Author

Owner

@TheBigBentley commented on GitHub (Nov 20, 2019):

I'm not using NordVPN

@TheBigBentley commented on GitHub (Nov 20, 2019): I'm not using NordVPN

deekerman commented

Author

Owner

@mrthuvi commented on GitHub (Dec 10, 2019):

Fresh windows install and I'm having this issue. 1903

@mrthuvi commented on GitHub (Dec 10, 2019): Fresh windows install and I'm having this issue. 1903

deekerman commented

Author

Owner

@kitchentiger commented on GitHub (Dec 21, 2019):

Also a fresh Windows 10 PRO install, now fully updated and am currently having this issue as well. I don't use NordVPN but I do use a socks5 http proxy.

@kitchentiger commented on GitHub (Dec 21, 2019): Also a fresh Windows 10 PRO install, now fully updated and am currently having this issue as well. I don't use NordVPN but I do use a socks5 http proxy.

deekerman commented