#Malwarebytes rootkit disabled how to#

I’m getting the same ‘can not load Rootkit driver (error 20025) on a 13 year old Win XP system after an upgrading to 2.0) yes, I know I need a new PC and am accepting donations HAHA) I’m running the stock program configuration because I haven’t figured out how to change anything (I’m visually impaired and the current UI makes this difficult) OR amake this error go away. It is not clear if Malwarebytes will resolve the issue and make the anti-rootkit module compatible with other encryption programs. Programs like TDSSKiller, Avast's aswMBR or Gmer are all on-demand scanners that you can use for the time being. It is recommended to use other anti-rootkit software for the time being. This takes care of the error message that you get during scans.

Click on Settings > Detection and Protection.

Open the program on your system and bring the window of it to the front.

The best option currently is to disable the scan for rootkits in Malwarebytes Anti-Malware. The only option would be to switch to TrueCrypt encrypted volumes, but that is not really something that most users may want to do as it involves quite the operation (turn off the current encryption, run True Crypt, use it to encrypt the volumes).

There is not much that you can do at the moment to resolve the situation on your end.

#Malwarebytes rootkit disabled update#

I will be speaking to the Developers and will update this information as needed. No other disk encryption software is supported. To the best of my knowledge, like MBAR, MBAM 2.0's rootkit scanning has limited support for TrueCrypt encrypted volumes only. The only exception here is TrueCrypt which is supported, but if you are running a different encryption software such as Microsoft BitLocker or DiskCryptor (which I use) then you will run into the error message when Malwarebytes Anti-Malware tries to launch the Anti-Rootkit scanner. The reason for this is that Malwarebyte's Anti-Rootkit driver does not support encrypted volumes. Some even get it on system start, which I do not thankfully. If you check out the Malwarebytes forum, you notice that quite a few users get the same error message when they start a scan. I'm not the only user of the program who gets these error messages.