Grendizer

I am available for a remote session if an engineer would like to do some diagnostics...

Here's what I did. - attempted to do a repair of ESET and get the following error: - cancelled the repair then uninstalled MBARW and rebooted - attempted to repair the ESET installation. Same error message as above - attempted to uninstall ESET installation. Same error message as above - Attempted to do a system restore and got the following error: - left the domain and logged in as local administrator, thinking it was a permissions issue. - Rebooted system then performed a system restore as local administrator. This time it worked. - attempted to repair/uninstall ESET, still no dice. MBARW initially deemed ESET to be risky and did *something* to it. What did it do exactly and why has it not been reverted when MBARW was uninstalled?

Hi everyone, This is my first post. I would like to point out that like the others in this thread, I am running ESET NOD32 (I was). After updating MB to latest beta, I noticed that my ESET icon was no longer in the taskbar. I tried launching the application manually but nothing happens. I then proceeded to try and repair the installation. This is where I got insufficient provileges messages for various components and files belonging to ESET. I found this strange but then remembered that MB had tagged ekrn as a risk. It seems that ESET and all components have been blocked. I am now without antivirus, am unable to repair the installation let alone uninstall it and ESET informed me that I need to get in touch with you guys to unlock the files. Fantastic! MB doesn't have anything in the quarantine list, which seems odd considering it has already deemed ekern as a security risk. I tried uninstalling MB but that didn't help. All the ESET files are now locked and can't be used. I need assistance as soon as possible. I will not reformat this machine to get it to work.