Jump to content

mole13

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral
  1. @ dagar74: Thanks a lot for your very detailed and excellent instruction how to run MalwareBytes parallely with Bitdefender – highly appreciated! Recently I decided to renounce Kaspersky (not least because of conflicts of the KIS 2019 version with MBAM) and to switch to Bitdefender. But during install process of BD I was surprised to learn that the full version of BD could only be installed if MB was uninstalled. And like @gregwatson I´m a diehard fan of MBAM for years. So happy to note that it´s possible to use both engines nevertheless. Using Windows 11 (v 21H2) on a brand-new HP device and in compliance with your instruction it seems to work properly. But I installed that combination only a few days ago so it´s maybe to early to give an educated feedback. But anyway – regarding the mentioned instruction some questions remain (at least for me): Under “Add folders” you mentioned both folders of MalwareBytes, under “Program Files” as well as “ProgramData” to be excluded in any antivirus software. But below “Manage exceptions” (for Bitdefender) it seems that you exclude the folder “C:Program Files\Malwarebytes” only within Bitdefender. Is there any reason for that? When selecting the several files to be excluded in Bitdefender according to your instruction I found one additional file which you didn´t mention: mbam.sys (path: C:\Windows\System32\drivers). So as a precaution I added this file too to the exceptions within Bitdefender. What is your recommendation to that? Due to that my list in Bitdefender / … / “Manage exceptions” now reads as follows: C:\Program Files\Malwarebytes (folder) C:\ProgramData\Malwarebytes (folder) C:\Windows\system32\mbam.sys (additional file; see above) C:\Windows\system32\MbamElam.sys (file; your additional recommendation) C:\Windows system32\mbamchameleon.sys (file; initially present*) C:\Windows\system32\mbamswissarmy.sys (file; funny to read this exception) C:\Windows\system32\mwac.sys (file; initially present*) C:\Windows\system32\farflt.sys (file; initially present*) C:\Windows\system32\mbae64.sys (file on 64-bit machines) * means initially present after installing MBAM regularly without any speciality. So my list of exceptions in Bitdefender consists of 9 entries in total (2 x folders, 7 x files). Do you agree? 3. At the end of your instruction you recommended – as a precaution – to turn off the function “Scan potentially unwanted apps” and you wrote that you wanted to try to enable that function later on. What are your experiences since then? Happy to get a short feedback from you or other bloggers.
  2. Hi @AdvancedSetup, thanks for clarification. This fits well from a timely perspective, because my PC troubles started in January when setting up a brand new PC with KIS 20 initially (of course by using the regular online installer at that time) and upgrading from KIS 19 to KIS 20 on my laptop parallely. Didn´t check the KIS patch version but it must have been patch E or later.
  3. @x64 From my point of view YES. Meanwhile I´m using KIS 19 and MB both in real time scan mode on 3 PCs/Laptop up to now pretty stable and without any problems. KIS v 19.0.0.1088 (l) [means incl. Patch "L"]; MB v Premium 4.1.0; Win10 Pro v 1909 on each PC. My experience was that KIS 19 posed no problems at any time by using MB as real time scanner regardless of KIS 19 patch and MB version. (Although KIS 19 lost some good features compared to KIS 18 - but that is another issue.) Didn´t try KIS 20 in combination with new MB fix up to now - had definitely too much trouble with KIS 20 in the past. Will wait for more positive feedback and confirmations from the community.
  4. @muizamsa If you want to use KAV / KIS / KTS v 2020 there will be no need to uninstall MBAM; for the time being (i.e. until KL will fix the conflict issue for 2020 versions) it should be possible to run Malwarebytes not as a real time scanner but only "on demand" (meaning checking your PC by Malwarebytes by a manually initiated scan) without being conflicted by Kaspersky. This is a hint I red in the Kaspersky forum but to be honest I didn´t try whether this will really work and your complete PC system will be stable. (Will not try this because I had too much trouble with KIS 2020.) Up to now I also rely on KIS but in my opinion the KIS v 2019 is absolutely equal to v 2020 - at least the databases are the same. And please do not forget: Malwarebytes is not a pure AV like Kaspersky but a protection against several kinds of malware beside viruses which Kaspersky is not able to detect. So the decission is between a Kaspersky AV in the latest version which even then will not detect everything and a Kaspersky AV version which is not the newest one but also useful and therefore able to work together with Malwarebytes in real time scan mode. Of course I respect your decission and I do not want to missionize. Just thinking about efficiency
  5. Hi all, Would like to share my experiences since upgrading to KIS (Kaspersky Internet Security) 2020. Did it unfortunately on 2 PCs (Workstation & laptop, both HP, both W10 v 1909) while MBAM version 4.0.4. premium has been installed (and still is installed). All problems described by @Conexion21 appeared and more. Parallely I´m using another PC (also W10 v 1909) but with former KIS 2019 - and it runs without any problems while both scanners KIS and MBAM run real time! So I did a new setup (not fully) of my laptop by proper deinstalling KIS 2020, cleaning it by Regitry First Aid 11(to be really sure that KIS 2020 didn´t leave any Registry marks) and using the full installer of KIS 2019 - and the laptop runs very well again since then. So for me it´s pretty clear: all new Kaspersky versions 2020 cause these conflicts. Posted this issue also on the Kaspersky forum but didn´t get any reply from the KL moderators up to now. See therefore https://community.kaspersky.com/kaspersky-total-security-14/malwarebytes-compatibility-merged-3064/index2.html#post36069 https://community.kaspersky.com/kaspersky-free-for-windows-72/compatability-with-malwarebytes-pro-2874 Some hints for those who need to re-install KIS or other KL products v 2019: - For re-installing you will need the full installer .exe of the KL products 2019 or 2018 which is between 150 and 165 MB (maybe depending upon which language you´re using). To get the link use the 1st link above and scroll down to the post of @FLOOD of 22 Feb. 2020 (it´s not possible to copy and paste the full URL here; don´t know why). - Before re-installing KL-product 2019 you should install MBAM in the latest version (and do a proper de-installing of KL 2020). During installing KL product v 2019 or former the warning of a conflicting program being "Malwarebytes V3.x" will appear. You should ignore this message by deactivating the conflict message (nothing serious will happen if you do so) and go ahead. (By the way: the workstation mentioned above was brand new and never ever MBAM v 3.x was installed before. But the same conflict message appeared, so I´m wondering what KIS would like to de-install if the conflict message is set to "active") - After completion of installing KL product 2019 immediately deactivate the automatic upgrade function of Kaspersky within the KL settings / Additional / update-settings (=> "Do not download new versions automatically ..."). - Probably the 1st patch version of KL 2019 will be installed by using the full KL installer which is of course patch a version. Run a regular Database Update (not to be confused with the version upgrade before), and all further patches will be installed automatically (for KIS 2019 it´s patch k or later). - Updating databases and application mudules can (and should) be set to "automatically". On my PCs in this combi of settings all work fine, as well as running both scanners KL and MBAM in real time mode. - You are able to use your regular KL licence as well as the adequate activation on your KL account after re-installing KL v 2019 (do not know whether this will work too if you´re using a KL product 2020 for the very 1st time). - Until the described issues caused by KL 2020 versions will not be fixed by KL itselfe I cannot recommend to use the KL 2020 versions. To support MalwareBytes (no, I´m not an employee of Malwarebytes, I´m not related to it and I do not get any provisions for my post, unfortunately) because you like MBAM like I do please post as any messages you can on the according Kaspersky forum resp. their Malwarebytes threads (actually 2) - only then KL maybe will see that they have to change their unfriendly policy of disability of unwelcome concurrence (please note that MBAM is not a concurrence but a useful protection supplement !!!). Hope this post will help all those who have problems with KL 2020 products while using MBAM. (Myself I lost days by days by figuring the conflicting app and solving all problems out.) Best
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.