Jump to content

Anti-Malware Encountered Problem Needs to Close


Recommended Posts

Running Windows XP (SP3 & lastest updates), Norton Internet Security

 

I am having a problem with Anti-Malware that started several weeks ago.  I would try to update the definitions and I would get a Windows error dialog box.

 

"Malwarebytes Anti-Malware has encountered a problem and needs to close.  We are sorry for the inconvenience"

 

I was out of town on a trip and I have finally got some time to work on the problem.

 

Using an admin user account, I tried to uninstall Anti-Malware and reinstall with version 2.0.2.1012.

 

I used the MBMA Clean Removal Tool on several occassions with a clean reinstall each time, but I continued to get the error.

 

I used Revo Uninstaller Pro to remove Anti-Malware using the Advanced Scan option, and then did a clean reinstall. 

 

I added the 4 Anti-Walware files to my Norton Internet Security Firewall (mbam.exe was already explicitly listed).

 

I clicked to scan the system, the definition files were updated, but then the error again.  Now I get the error when I try to update the file.

 

Thank you in advance for your help.

Link to post
Share on other sites

Hello JoeSouthFla and :welcome:

Please do the clean re-install again and if your issue remains, please attach the requested diagnostic logs.

Please let us know, in a reply to this thread, if the above steps have helped you with your issue.

Thank You. :)

Link to post
Share on other sites

1PW, thank you for your response.

 

I removed and reinstalled Anti-Malware as suggested

  • I ran the mbma-clean tool to uninstall Anti-Malware
  • Rebooted the system
  • Installed the current version 2.0.2.1012
  • Rebooted the system
  • Tried to run Anti-Malware, got the same error again.

 

I created the diagnostic logs using (the logs are attached)

  • Farbar
  • mbam-check

 

Thank you again for your assistance

FRST.txt

Addition.txt

CheckResults.txt

Link to post
Share on other sites

  • 3 weeks later...

Is someone able to help me with this problem?

 

I have been out of town for several days and I just rechecked the forum.  I posted my logs on 2nd June and I have not seen any responses.

 

Do I need to provide any additional information and try to take some other action?

 

Thank you in advance for your assistance.

Link to post
Share on other sites

Hello JoeSouthFla:

 

Please allow me to sincerely apologize for my inexcusable oversight and delay in replying to your topic.

First, (but only if the program is running) please shutdown the realtime Malwarebytes Anti-Malware application: Go to the desktop Taskbar. Locate the blue-colored MBAM icon in the notification area.
Do a Right-click on it with your mouse, and select Exit.

I have attached a zip file (Netconf-batch-file.zip) which you need to Save to your system.

Once saved, unzip it to extract all contents, which will be 2 files.
Next, double-click on the net_replacement.bat file.
It should run fairly quickly in a command-prompt window.

I would suggest then a Logoff >> Shutdown >> Restart so that your computer is then in a new Windows session.

Once that is done, if not already done, restart Malwarebytes Anti-Malware and let me know if it works normally.

Thank you for your understanding and patience.

Netconf-batch-file.zip

Link to post
Share on other sites

1PW,

Thank you for the quick response and the link to Netconf-batch-file.zip

The good news is that I was able to get Anti-Malware working again.

However I had a problem with the bat file.  I looked at the bat file in a text editor to see what it was trying to change and I was able to manually rename the existing net.conf file and copy the new net.conf file.  

When I ran the bat file, it could not find the existing net.conf file in the defined directory structure, nor could the bat copy the new net.conf file into the defined directory structure.  I selected the "D" option on the last step.  I did not retry running the bat with the "F" option once I realized what the bat was trying to accomplish.

See the attached 140623_Malwarebytes_NetConfBatch_01.pdf file.

 The bat file was looking for the following directory structure:
 
 C:\Documents and Settings\All Users\Malwarebytes\Malwarebytes Anti-Malware\Configuration\net.conf
 
 The directory structure on my XP installations has an additional "Application Data" folder as an "All Users" subfolder :
 
 C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malware Anti-Malware\Configuration\net.conf
 
 See the attached files:
 140623_Malwarebytes_NetConfBatch_02.pdf
 140623_Malwarebytes_NetConfBatch_03.pdf
 
 I have run Anti-Malware update and scan 3 different times, so I think it is OK.
 
 Out of curosity, why did the old net.conf file cause a problem on a clean reinstall, and what chnaged with the new net.conf file?
 
 Thank you again for your assistance, it was very helpful in geting the application running again.

140623_Malwarebytes_NetconfBatch_03.pdf

140623_Malwarebytes_NetconfBatch_01.pdf

140623_Malwarebytes_NetconfBatch_02.pdf

Link to post
Share on other sites

Hello JoeSouthFla:

Thank you for the good news feedback that your issue is resolved.

Malwarebytes' staffers are now getting their heads around a very obscure set of circumstances that effects a tiny fraction of MBAM users. Each new occurrence brings us new data points. Yet I suspect we will have a new release that will solve this issue soon.

Compounding the issue is not many of us are running XP like you and me.

Please let us know if we can help further. :)

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
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.