Problems with latest version of malwarebytes

On 4/01/2017, I installed Malwarebytes 3.0.6.1469 on Windows XP, Windows 7, and Windows 10 systems.
1) Malwarebytes 3.0.6.1469 doesn't give choice of installing "premium trial". It always installs it.
2) With Windows XP:
a) It hangs “scanning root kits”.
b) It declares HKLM\SOFTWARE\MICROSOFT\SECURITYCENTER\UPDATESDISABLENOTIFY a PUM
(Possibly Unwanted Modification)!
c) It slows LAN traffic (between XP and W10) to take over an hour for a 30-second operation!
3) With Windows 7:
-MB3 won't update definitions
-crashes on start-up
-prevents re-installation of mbam-setup-2.2.1.1043.exe.
-Mbam-clean-2.3.0.1001.exe doesn't remove any mbam files!
4) With Windows 10:
-no problems so far
Malewarebytes has ruined a previously good product. I've gone back to using 2.2.1.

Is version 3 stated to support Windows XP?

jadinolf said:

According to them:
Windows XP (Service Pack 3 or later, 32-bit only)*

That surprises me, but good for them, at least in that respect. I can't say I like the direction they're headed in at the moment but I'll see what happens to the definitions on Version 2 as well as how the reviews go on Version 3 before I decide whether to stay with MBAM beyond June I think it is.

jadinolf said:

cdgoldin, you should go on the Malwarebytes forum and tell about the problems you are having.

That's the only way they can fix them.

I have posted the same information on the Malwarebytes forum. I have also reported it to their poor excuse for "technical support". I don't expect either post to make a difference. So I warn people through this forum. That way, when they experience difficulties, they will know they are not alone, and not waste time trying to make a bad product work.

Seffrid said:

Is version 3 stated to support Windows XP?

Yes. Malwarebytes claims to support all versions of Windoze from XP to W10. The "anti-ransomwear" feature is not supported on XP, and this is listed as a "known problem". Many of the W7 problems were reported in earlier versions of 3.0, and they were purportedly fixed, but obviously insufficiently tested.