pfefferc

Thanks.. it sounds like MWB has a long way to go before this is ready.

Malwarebytes on Twitter: "We are aware of a temporary issue with the web filtering component of our product that may be blocking certain domains, including https://t.co/LnURsrOUW1. We are actively working on a fix and will update Twitter as soon as we have more information." / Twitter

Does not help us...we have these options disabled for our end users. It must be done from the cloud console

How are you disabling web protection... half of our cloud console will not even load, including endpoints and policies!

It seems to just be affecting Google Chrome and not MS Edge

Same issue on our end... and now the console cant load the endpoints

No, this does not even come close to answering my questions.

I am looking for information on the Patch Management feature. Does it simply update supported installed software, or will it also allow you to push installations or uninstalls of supported software? In better terms for Ninite users, how does this feature compare to Ninite?

We have no next gen firewall, content filter, proxies, etc... you are not using the correct software for a business environment yes we are. We use the Corporate version and have a Corporate license. We inquired about the 3.0 update for this version and this is what they sent us to install for the update. Some of our machine are running the legacy 1.80.2.1012 version so I will gladly use a separate update tool if you can provide one for 3.0 + Corporate. As of yet, I have not seen a 3.0 corporate installer.

There is no firewall blocking it Ping request could not find host https://data-cdn.mbamupdates.com/. Please check the name and try again. Ping request could not find host https://keystone.mwbsys.com. Please check the name and try again. Direct click on the links results in 403 Forbidden You don't have permission to access / on this server. Tested the above again from a separate network with same result nslookup data-cdn.mbamupdates.com Non-authoritative answer: Name: e4280.g.akamaiedge.net Address: 23.63.111.107 Aliases: data-cdn.mbamupdates.com data-cdn.mbamupdates.com.edgekey.net ping e4280.g.akamaiedge.net Pinging e4280.g.akamaiedge.net [23.63.111.107] with 32 bytes of data: Reply from 23.63.111.107: bytes=32 time=8ms TTL=57 Reply from 23.63.111.107: bytes=32 time=8ms TTL=57 Reply from 23.63.111.107: bytes=32 time=8ms TTL=57 Reply from 23.63.111.107: bytes=32 time=9ms TTL=57 Ping statistics for 23.63.111.107: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 9ms, Average = 8ms nslookup keystone.mwbsys.com Non-authoritative answer: Name: keystone-key-prod-web.us-east-1.elasticbeanstalk.com Addresses: 34.200.15.211 34.204.230.41 Aliases: keystone.mwbsys.com Pinging keystone-key-prod-web.us-east-1.elasticbeanstalk.com [34.204.230.41] with 32 bytes of data: Reply from 34.204.230.41: bytes=32 time=45ms TTL=238 Reply from 34.204.230.41: bytes=32 time=46ms TTL=238 Reply from 34.204.230.41: bytes=32 time=45ms TTL=238 Reply from 34.204.230.41: bytes=32 time=51ms TTL=238 Ping statistics for 34.204.230.41: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 45ms, Maximum = 51ms, Average = 46ms

files attached MB-CheckResult.txt Addition.txt FRST.txt

Well 1) you should believe it as it is true and 2) Not something you should say to a client paying thousands of dollars a year on a product!

Is this really your default troubleshooting step? This is not practical in the business environment with machines that are all remote.

No, it is still not updating and more users are reporting this issue now as well. It also does not work on a fresh windows install and mbam install... everything installs and works correctly except for the updates.

We have about 1000 business machines running Malwarebytes Premium. One by one they are no longer updating. This started this morning.

I really don't think we need separate topics for an obvious issue on the update engine!

This is a wide spread problem! I now have 100 machines and rising that are having this issue!

This is a wide spread problem! I now have 100 machines and rising that are having this issue!