Search the Community
Showing results for tags 'locking up'.
So i guess this is kind of a two part post. So we just replaced our on prem endpoint clients with the cloud endpoint clients and that seemed to go fine using the mbam clean tool. The problem some of our users are seeing is their chrome and firefox will lock up for 20+ minutes and just be frozen. I have turned off Web Protection and Anti Exploit to see if that fixes it, i haven't heard an update on the issue yet but i was curious if anyone has ran into this issue before. Part two, We have two policies, one for our computers and the other for our virtual machines/VDI's that DO NOT use anti exploit. I realized that using the endpoint installer provided it only uses the default policy and i can't install an endpoint solely to a specific policy like we kind of could with the on prem solution (install with anti exploit, one without). Is there a way besides installing then moving the machine to the correct policy to install the specific client to that specific policy?
I'm wondering if there's any chance that your "latest and greatest" V3.x program will work any better with my XP Pro? I don't want to install it and have it completely lock up my system, like it did a couple of months ago. I would appreciate an honest answer to this. Nathaniel, still hoping your program will get along with my legacy system.....
Hi there moderators. This is a followup from a post from a while back with a similar topic title. I had posted info about new incompatibility with Eset NOD 32. I'd like to continue exploring this as it is unresolved and the plot only thickened with a new recent discovery! Here is the original post: [snip] Hello. I haven't seen anyone post about NOD32 Antivirus 4.x. I install the free version on most of my customer's machines. Win7/Vista = no problems. WinXP SP3 = same hard crashing as mentioned above by many. I am one person, but am a tech and have installed MB 184.108.40.2060 & 220.127.116.110 on dozens of machines in the past month or three and I am getting SLAMMED with calls about computer freezes from my customers with XP. When 18.104.22.1680 first came out and started crashing machines, I did indeed use the MBAM_cleaner to perform a clean uninstall. Upon reinstallation it seemed to work for a bit, but alas, 22.214.171.1240 came out and auto downloaded and all the machines starting crashing again upon reboot. (Quietly in the back of my head, I thought, they didn't fix all of it yet... I hope someone tells them about the newly created incompatibility with NOD32!) The IMPORTANT part of my story is that this is even happening with NEW WINDOWS BUILDS, meaning, I have: tested the hard drive for bad sectors, wiped the hard drive, reinstalled windows, patched windows fully, disabled windows firewall, installed MB 126.96.36.1990, then NOD32 Antivirus 4.x and then CRASH! No need to use the cleaner as this is a brand new build. I am one person, but have experienced this hard crashing described in this thread on dozens of XP SP3 machines most of them being new builds with the commonality of NOD32 Antivirus 4.x and MB 188.8.131.520, and in the case of old builds, the problem persists after using the clean uninstall utility and reinstalling 184.108.40.2060 from scratch. As soon as you enable the protection module... BLAM! Within a few seconds, it's cyber bedlam. You cannot stop NOD32 from running its startup scan. My temp fix is to disable the protection module so I have control of the machine long enough to uninstall MB. Even with the protection module off, the MBAM.exe process still runs and crashes the machine at startup, so I have to uninstall the program entirely and wait for the next version which will hopefully have a fix. Hopefully with the info contained in this post, you wonderful folks at MB will be able to contact "Eset", the makers of NOD32, and have a chit chat... I have touted MB for years as being a rare and wonderfully harmonious program that just seems to work well with others. My winning combination of protection was NOD32 2.x and then 4.x, MB and SuperAntiSpyware. I could run all three program scans at once with NO problems as they all scan in different ways and don't step on each other’s toes. But with the advent of MB version 220.127.116.110, something went awry. Please, please, please know that 18.104.22.1680 has NOT solved all the issues! Thanks, Jayneg [end snip] I have to make some clarifications/additions to that 1st post: 1. This only affects paid for /trial versions of MB. The free version is fine due to MBAM service not running... 2. I may have been hallucinating, but I swear I BRIEFLY saw a version 22.214.171.1240. It may have only been out there for an hour or a day, and that's what I thought was the latest version when I 1st wrote the post a while back. In the end, it doesn't matter. The problem began in the version just before 126.96.36.1990 (188.8.131.520?) and persists in the current version! Plus I made a new discovery which I will detail in a bit 4. One of the admin’s replies to this first post: "I would love to test this out for you Jayneg but I'm not aware of any "free" version from ESET. They do offer a 30 free trial but it's certainly not a free version that I'm aware of. If you can provide more details on that I will investigate this error you're speaking of." *To clarify, when I am preparing a machine, I install the trial (which is a full version, but with a 30 day countdown timer). After this trial period is up, many customers go on to purchase the full program... But it did not matter if it was the trial or the paid version, the problem was occurring regardless. I realize I used the word "free" instead of "trial" in the original post. Sorry for the confusion. 3. After posting this, I started migrating folks over to the latest release of NOD 32 5.x to satisfy the MB admin's request and POOF! Same problem with the ADDITION of a new problem: 4. In NOD 5.x, there is a new feature that watches for and scans removable media when 1st inserted. Well, if MBAM.exe is running in Win XP SP3, your machine quickly grinds to a HALT whenever an external hard drive or USB key is inserted. The only solution: hard kill! I will give the link to the thread AND cut & paste from the forum I found this info on: http://www.wildersse...ad.php?t=309335 [snip from page 7, post #155] March 5th, 2012, 06:58 AM rcdailey Regular Poster Join Date: Dec 2009 Posts: 141 Re: NOD 32 184.108.40.206 & 220.127.116.11:PC freezes when USB HD is connected Quote: Originally Posted by Marcos Oswald2 resolved the issue by installing the hotfix already provided to those who requested it here before. I believe that I have isolated and resolved the issue I was having with NOD32 v 18.104.22.168. The conflict that I found and eliminated was with MalwareBytes. I have the paid version of that software and I found that even with real-time protection disabled in MalwareBytes, the MBAM service would still load with Windows. This service was what prevented ESET NOD32 from checking when a drive was initially connected to the system while up and running. When this happened, the system would lock up. By either disabling the MBAM service or setting it to "manual," the conflict went away and the popup to select the action to take with respect to the USB drive would display and the appropriate option could be selected. In any case, with my system running XP SP3, this is what I found and how I decided to handle it. I also have SuperAntiSpyware ver 5.0.1144 installed and running in real-time and it does not conflict with NOD32 ver 22.214.171.124. It is a little disappointing to have to disable MalwareBytes, but I can live with it. I can now connect a USB hard drive while the system is running and it won't lock up. I can remove a USB hard drive while the system is running and it won't lock up. If anyone else using XP SP3 is running MalwareBytes in real-time and is having issues with ESET NOD32 v 5.x, try disabling the MBAM service and see whether that solves the problem. Adding to this, MalwareBytes will run a scan and can be updated manually without the MBAM Service enabled. I have checked that just now and can confirm that. Also, if the MBAM Service is set to "manual" it does not load when MalwareBytes is run. For most people who like to use MalwareBytes, that should be enough and there won't be a conflict with ESET NOD32 ver 5.x. One more note: If you do have the paid version of MalwareBytes and you decide to re-enable protection, then the MBAM Service will be reset to "automatic" and it will load with Windows, so keep that in mind. Last edited by rcdailey : March 5th, 2012 at 07:31 AM. [end snip] My only comment on rcdailey's post is that when you change the MBAM service to manual start in "services", MB starts spitting out periodic error messages about not being able to perform expected tasks. So, to me, this is not an option when preparing a customer's machine. They won't understand/want to see any error messages on a clean built/fixed machine. So AGIAN, my only option is to uninstall MB! Boo! I'd like to also add that I vouch for rcdailey's post. I tested it out. NOD32 + MBAM service running + plug in USB HD/USB key = disaster (hard kill only way to shut machine off) As soon as I turn MBAM service off, all systems nominal! I think MBAM service and NOD removable media watch service (not sure which process it is) are fighting! In closing, I assert that this is happening on ALL the XP machines I'm working on (over 100 by now) and there are no infections and that the systems are fully patched and all hardware is tested good. Final clarification: The problem where the XP machine would just lock/freeze at startup just outright without doing anything else seems to have gone away, although NOT with the release of the latest version. Did you guys sneak in a mini-patch on one of the definition updates? XP seems to get through the startup sequence now without crashing on its own, but only as of about a few weeks ago?!? (mystery) So I thought to myself YEAY! They fixed it in an unadvertised, non-version number changing mini-patch! I began installing it again on all my customer machines and then got hit with the External HD problem! ARGH! One last observation: There is even new quirky behavior in a few Win7 machines with NOD 5.x and MB newest ver. Again, it usually happens right at startup when I sometimes try to terminate mbam service from taking over 100% processor, so i can quickly bring up a video or program, the machine will lock up just like with XP. It feels different and of course it is being brought on by my terminating a running service, but the combo of Eset and MB both eating up startup juice for the first two minutes is sometimes too much to bear. & windows shouldn't totally hose itself from terminating a "non-critical" process. This is just a side note; something to think about in the future... The MAIN problem is XP as outlined above. What other info do you need from me to help you resolve this? NOD & MB used to work harmoniously together. Now between the latest few releases from both companies, this has changed... Please get on the "phone" with Eset and do some testing collaboratively. THANKS- Jayneg