FeMaster

Thanks again for the reply. Checked in settings and application update was already turned off. Not sure why, I might have done it after reinstall and just don't remember. In any case, will be awaiting word of the next update. Thanks again!

Correct, with 3.7 I couldn't update. Upon reverting back to 3.6 I could. If need be, I can reinstall 3.7 and run the support tool again, if that will help you gather any necessary information. Thanks!

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). This particular instance of Malware Bytes is just the free version. I have the premium version running on another PC, but that one is working fine. I haven't tried doing any license activation on this PC. May 16th, I believe is the day I tried to run an update on Malware Bytes before doing a manual scan. 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. It advised me to check my connection, which I verified was working fine. I also verified at that time that my ESET Firewall wasn't blocking the connection. Upon searching for a resolution I came across this thread. I replaced V3.7 with V3.6 and the updates started working again. I've done the reboot since the report was made, and I've attached the System Info export as requested. MS System Info.txt

I've run the tool and gathered the logs which I've attached. While running the tool, there was an error which I believe indicated that it could not save the HOST file, so I had the software just continue anyway. After thinking about it, I do have ESET Internet Security installed, and I'm wondering if that is what falls under the LSP. In either case, log is attached. mbst-grab-results.zip

I was a victim to this issue as well. Not sure what caused it, as I'm not aware of an 3rd party LSPs on my system. In either case, reverting back to V3.6 fixed my updating issues. We are at the 1 month mark with this issue, and there has been nothing additional added to the thread. Can I assume that the problem has not yet been resolved, and that I should not attempt to update to the latest version?