Upon searching for a resolution I came across this thread. I also verified at that time that my ESET Firewall wasn't blocking the connection. It advised me to check my connection, which I verified was working fine.
At that time I was running version 3.7 and I kept getting an error that the software couldn't connect to verify my free license (or something similar to that), and also that it couldn't connect to the update server.
May 16th, I believe is the day I tried to run an update on Malware Bytes before doing a manual scan. I haven't tried doing any license activation on this PC. I have the premium version running on another PC, but that one is working fine. This particular instance of Malware Bytes is just the free version.
My issue wasn't with activation, but my install was affected by the bug listed in this thread as I was unable to access the update server(s). Then also attach that files in a new reply so that we can get that for review. Then provide a meaningful file name and save that. Allow enough time for the applet to load and finish. This starts the Microsoft System Information tool. Press & hold the Windows-flag-key on Keyboard & then tap the R keyĪnd tap Enter-key. Lets also do this, please, to get a Windows report. However, there was a log entry in Malwarebytes history, indicating "General network error" back on May 16 when (perhaps) you may have been trying to activate the license.
I would not imagine that the Nvidia is one of those that are 'problematic'. This Windows system does appear to have a LSP entry for Nvidia NetworkAccessManager in the Windows Winsock. Lets have you go ahead & close any open work, browsers, etc, and then Restart Windows. Windows has some pending file rename operations, that need a Windows Restart. The Malwarebytes for Windows is reported to be running as in Free mode ( not Premium).
Please attach the ZIP file in your next reply. Upon completion, click a file named mbst-grab-results.zip will be saved to your Desktop. You will be presented with a page stating, "Get Started!"Ĭlick the Advanced tab on the left columnĪ progress bar will appear and the program will proceed with getting logs from your computer Place a checkmark next to Accept License Agreement and click Next You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Once the file is downloaded, open your Downloads folder/location of the downloaded fileĭouble-click mb-support-1.4.0.615.exe to run the report
If you would run the Support tool report, we can determine whether or not this pc has 3rd party LSPs. In either case, reverting back to V3.6 fixed my updating issues. as I'm not aware of an 3rd party LSPs on my system. In the meantime, you can either uninstall the Transocks PC版 software and reboot or temporarily revert to the previous Malwarebytes version (3.6) using the following link: Edited by LiquidTension We're working on a fix for this in an upcoming Malwarebytes program update. Winsock: Catalog9-圆4 20 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp64.dll (成都飞欧比网络科技有限公司) Winsock: Catalog9-圆4 04 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp64.dll (成都飞欧比网络科技有限公司) Winsock: Catalog9-圆4 03 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp64.dll (成都飞欧比网络科技有限公司)
Winsock: Catalog9-圆4 02 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp64.dll (成都飞欧比网络科技有限公司) Winsock: Catalog9-圆4 01 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp64.dll (成都飞欧比网络科技有限公司) Winsock: Catalog9 20 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp.dll (成都飞欧比网络科技有限公司) Winsock: Catalog9 04 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp.dll (成都飞欧比网络科技有限公司) Winsock: Catalog9 03 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp.dll (成都飞欧比网络科技有限公司) Winsock: Catalog9 02 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp.dll (成都飞欧比网络科技有限公司) Winsock: Catalog9 01 C:\Users\Fenixnailo\AppData\Roaming\transocks\transockslsp.dll (成都飞欧比网络科技有限公司) In your case, this specifically relates to the Transocks PC版 software you have installed. Hi issue is caused by Malwarebytes version 3.7's incompatibility with third-party LSPs.