"Server operating systems are only compatible with Malwarebyte products"...

[riahc3]

Hello

I think this is really BS.

Using a legal, bought and legit malwarebytes license on WS2012R2 and now I get this message when trying to update.

After paying and using the product, I consider it bullshit that now, because Malwarebytes decides it wants to rake in more cash, I cannot update the product.

You should let people update (and stay secure) and just display a message of not being supported.

[Porthos]

 

28 minutes ago, riahc3 said:

Using a legal

I am sorry but the home/consumer version of Malwarebytes not only been unsupported but against the EULA of the program since the beginning of the program. 

Just because it "functioned" did not make it legal.

[riahc3]

5 hours ago, Porthos said:

 

I am sorry but the home/consumer version of Malwarebytes not only been unsupported but against the EULA of the program since the beginning of the program. 

Just because it "functioned" did not make it legal.

https://www.malwarebytes.com/eula/

There is the EULA. Where does it say anything that it cannot be used on Windows Server 2012 R2 at home?

I am not using it in a business.

Edited September 4, 2017 by riahc3

[Porthos]

It used to be in the EULA. Either way Not supported still means do not try to use it on a Server OS. It was never meant/supported on a Server OS so Malwarebytes is not obligated to give you one that can be used on servers.

I am sorry that my answer is not what you want to hear.

@celee

[riahc3]

1 hour ago, Porthos said:

It used to be in the EULA. Either way Not supported still means do not try to use it on a Server OS. It was never meant/supported on a Server OS so Malwarebytes is not obligated to give you one that can be used on servers.

I am sorry that my answer is not what you want to hear.

@celee

If it isnt in the EULA (you claim it was...), then I am more than entitled to a refund.

The product was bought, it worked, and all of a sudden, using the same hardware and the same operating system, it doesnt.

 

Edited September 4, 2017 by riahc3

[Porthos]

9 minutes ago, riahc3 said:

then I am more than entitled to a refund.

That you have to discuss with support.

Please open a support ticket using the following link: https://secure.livechatinc.com/licence/8473103/open_chat.cgi?groups=1

The support team can help you fix the licensing issue.

Thank you.

[gonzo]

The EULA is fuzzy on this issue, but the System Requirements on the Download page is not.  No server is on that list, for a reason.  People use the software commonly for real-time protection.  Neither the website protection or the ransomware protection will behave as expected on a server operating system due to differences between server OS and client OS.  The safest way to guard against issues which may arise is to check what OS you are using before allowing updates.

As Porthos said, a support ticket is your best bet.

[riahc3]

26 minutes ago, gonzo said:

The EULA is fuzzy on this issue, but the System Requirements on the Download page is not.  No server is on that list, for a reason.  People use the software commonly for real-time protection.  Neither the website protection or the ransomware protection will behave as expected on a server operating system due to differences between server OS and client OS.  The safest way to guard against issues which may arise is to check what OS you are using before allowing updates.

As Porthos said, a support ticket is your best bet.

Server OS are based on their desktop. So the drivers work...so should the software (which it has been working until Malwarebytes has decided to change to milk this)

[riahc3]

BTW, Ive been a Malwarebytes fan but its sickening that some of you are actually trying to defend this.

 

Shame on you.

[exile360]

While it is true that many of the core functions in Malwarebytes will work perfectly fine under most circumstances in the Server counterparts of most modern Windows versions, it is a fact that there are also several known issues which can cause problems ranging from perpetual annoyances to actual severe denial of service (DoS) problems resulting in potential loss of data and possible network failure.  Among these are certain problems between our web protection and the network stack unique to servers where it may register web blocks constantly for one or all blacklisted websites in our block database due to the APIs we use in Malwarebytes and how those differ in Server versions of Windows (you may search for posts about constant IP blocks on Server for some examples; it's something we've seen plenty of unfortunately).

So yes, while the core architecture of a Server build of Windows is essentially the same as its desktop platform counterparts in that they share the same kernel and much of the same code, there are unique aspects and components to Server builds that can cause undesirable and sometimes unpredictable issues with products not explicitly designed for those builds of Windows.  Regarding legality, EULAs etc., I'll leave that to the rest of the staff to comment on as that is not my area of expertise, but I assure you we are not attempting to mislead you in warning about known problems with our product's realtime protection components on Server operating systems because we've had customers report them to us and have replicated several on our own in-house when testing for compatibility on enough occasions to know that it is an all too common occurrence.  Obviously this is something we do wish to someday correct as we certainly have plenty of business customers who would like to protect their servers in addition to their endpoints using our flagship product, however it's just not something we can recommend at this time due to these known issues so we cannot officially support it and must advise against it for the best interests of our customers, yourself included.

I am certain that if you contact our helpdesk as advised, they will gladly do all they can to make this situation right, including most likely offering you a refund for the cost of our software; I just know that right now we don't have a version which is guaranteed to work under any Server version of Windows.

[riahc3]

I want to clear up that Malwarebytes has correctly backtraced its steps and now allows home users that have server operating systems in their environment to install and use Malwarebytes. 

[riahc3]

I want to clear up that Malwarebytes has correctly backtraced its steps and now allows home users that have server operating systems in their environment to install and use Malwarebytes. 

[exile360]

Actually, they haven't.  As you can see based on the system requirements listed at the bottom of this page, it is still not officially supported on any Server Windows versions:

Software requirements
Windows 10 (32/64-bit)
Windows 8.1 (32/64-bit)
Windows 8 (32/64-bit)
Windows 7 (32/64-bit)
Windows Vista (Service Pack 1 or later, 32/64-bit)*
Windows XP (Service Pack 3 or later, 32-bit only)*
Active Internet connection

Just as stated previously, while there is nothing explicitly barring you from running it on a home server if you choose to, the functionality of the software and compatibility of the software with any Server build of Windows is not tested by Malwarebytes, not guaranteed and not validated.  This of course does not mean that you cannot run it on a Server OS if you choose to, just be aware that you may encounter unexpected problems as it has not been coded for or tested on those platforms.

I also want to be clear that even in this very thread none of us ever said that users were not allowed to run Malwarebytes on a Server OS, we simply stated the exact same thing that I just did in this post, that it has not been tested and that it may not function as expected due to the differences in Server versions and the non-Server builds of Windows.

With all of that said, you are again free to run it on your server if you wish, and as long as it is within 60 days of your purchase you may request a refund to get your money back if it ends up not working properly or doesn't suit your needs and of course the 14 day free trial is also available so that you may test it on your server before purchasing any licenses to make sure that it works as it should in your environment.