madbassist1

This may not be an issue to individual users, but you can surely see the impact this would have in an enterprise environment. Installing the software, rebooting, then immediately having to install it again and then rebooting again is a deal killer from where I sit. Is there any way around this?

Agreed. In my experience, however, sometimes the best advice comes 'from the trenches' if you will. I thought I would ask here first. I am almost certain that the issue is due to conflicting registry entries, and regardless will post back to let you know what I find for future reference. Thanks!

Wow nothing at all, huh? no one has EVER seen this before? since it happens on every machine, I would think that it has to have happened somewhere else. Ok, thx anyways.

What I am saying is that malwarebytes cannot get to the internet. Something is blocking it. Your desktop looks like you work in an office. You may need to find out which proxy server you use to get to the internet and provide that information to the program. As I said, I am no expert on the program or how it should be configured. I will step aside here for some of the forum experts to help you.

You using a proxy to connect to the Internet? The error (and I'm no expert), looks like Mbam is trying to connect to the internet but is running into a proxy or firewall along the way. I'd start there.

I am putting together an enterprise install of malwarebytes. The program appears to install fine, I configured updateing and scanning scheduling according to the instructions (including startup of mbamgui) the sceduled tasks all do not run with the error 'could not start' more worrying, though, is when trying to manually update the app, it connects to the server (provided the proxy information is now manually entered into the registry) downloads the update, then when going to apply it, the mbam gui needs to close crash message comes up, followed immediately by malware bytes successfully updated to version (whatever). This is happening on every machine I install the app on. Can a brutha get a little help with troubleshooting? Even though the code says its 1.44, it is actually 1.45. I hoped upgrading would help with the issue, but instead has just caused more registry entries to be added to the install file for proxy settings. Those reg entries are excluded from this install file, but are valid and working, for the most part.