Error code: 703 (0,5)

[Flapjack]

Unfortunately again today I have received the error code 703(0,5) when I tried to update MBAM. I tried deleting the rules.ref file as Exile 360 suggested when I had the same problem on Monday. However, when it came to reloading the database, the same error code flashed up again.

(I also had the error code yesterday but re-downloading the rules.ref file worked then.)

Please can you advise me how to resolve this problem? Is it something I am doing or my computer is doing that keeps making this error code appear? Your help and advice will again be appreciated.

[GT500]

Do you use AVG for anti-virus? If so, what version of Windows does your computer have?

[Flapjack]

Thanks for your swift reply.

Yes I do have AVG AntiVirus - I have the AVG Free version 9.0.698.

My Windows system is Windows XP Home Edition SP3.

[FireKMJ]

I am also having the same problem with updating MWB. I didn't notice the problem until I upgraded from AVG 8.5 to AVG 9.0. That was when I started to have the problem. And I am also running Windows XP home.

[GT500]

OK, both of you need to add the following file to the exclusions list in AVG:

C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref

[FireKMJ]

OK, I don't want to sound inept but I don't see anything in AVG to allow me to do that.

[Amethyst]

I'm using AVG 8.5, so I don't know if it will look the same in AVG 9, but I'll take a try with it anyway.

You can highlight and copy this:

C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref

Open up the AVG user interface. Go to Tools, then Advanced Settings. In the left window you should see Resident Shield, and under that click on Exceptions. A window will open up where you can add exceptions. The easiest way would be to click on the Add List Button. Inside the Resident Shield-Directory Exclude List window that opens up, paste the text you've copied from the post. Click on OK to close that window. The path to the rules.ref file will be in the Resident Shield window now. Click on Apply and OK, and you can close out of there.

I hope that helps. As I said, version 9 might look different, but if that's the case, you should be able to find some place to put this in an advanced settings window.

[Flapjack]

I'm using AVG 8.5, so I don't know if it will look the same in AVG 9, but I'll take a try with it anyway.

You can highlight and copy this:

C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref

Open up the AVG user interface. Go to Tools, then Advanced Settings. In the left window you should see Resident Shield, and under that click on Exceptions. A window will open up where you can add exceptions. The easiest way would be to click on the Add List Button. Inside the Resident Shield-Directory Exclude List window that opens up, paste the text you've copied from the post. Click on OK to close that window. The path to the rules.ref file will be in the Resident Shield window now. Click on Apply and OK, and you can close out of there.

I hope that helps. As I said, version 9 might look different, but if that's the case, you should be able to find some place to put this in an advanced settings window.

Hi there Amethyst.

You are right - it does look very similar in AVG 9 - but unfortunately adding this file to the Excludes for the Resident Shield still does not allow MBAM to work. I made this change and then rebooted but was still unable to use MBAM - the same error code popped up.

I am going to try excluding the whole MBAM folder to see if that works.

[exile360]

Greetings

If that does not work, try deleting rules.ref from C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware and try to update again. It's possible the file got corrupted by AVG before the exclusion was made and it simply needs to be replaced.

[Flapjack]

Hi there Amethyst.

You are right - it does look very similar in AVG 9 - but unfortunately adding this file to the Excludes for the Resident Shield still does not allow MBAM to work. I made this change and then rebooted but was still unable to use MBAM - the same error code popped up.

I am going to try excluding the whole MBAM folder to see if that works.

Ah well - it was worth a try - but didn't work. Still no MBAM

Can anyone suggest any other solutions to this problem?

[Flapjack]

Hi there Exile360.

I will try that now.

[exile360]

Alright, hopefully it will work. Good luck .

[Flapjack]

Greetings

If that does not work, try deleting rules.ref from C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware and try to update again. It's possible the file got corrupted by AVG before the exclusion was made and it simply needs to be replaced.

Thank you - that seems to have done the trick. I have been able to reload the database and am now starting a quickscan - definitely a hopeful sign.

Thanks again for your help.

[exile360]

You're welcome . Hopefully it stays fixed this time and I also hope that AVG soon corrects the problem. It seems they've had a lot of issues with MBAM this year .

[Flapjack]

I was just wondering if it is worth MBAM adding to the Sticky which was posted on this subject by GT500 to point out to other people with this problem that they need to replace their copy of rules.ref AFTER they have added the file to their AVG Resident Shield excluded files list ...

or is it just me who wouldn't have thought of it

[exile360]

I think it's a good idea to do so, as I'm certain this problem and its solution isn't isolated. I've had to post those very instructions to many users thus far to correct the problem. If GT doesn't see this post and add to it after a day or so I'll ask him about it and I'm sure that he'll add it .

As a side note, you might also contact AVG support (or post in their forum if you're using the free version) and let them know that you've had this issue. I believe they've been made aware of it, but the more users that let them know that they've had this problem the more likely they are to correct it sooner rather than later.

Thanks

[Flapjack]

Good point about contacting AVG - I will certainly do this.

[FireKMJ]

Greetings

If that does not work, try deleting rules.ref from C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware and try to update again. It's possible the file got corrupted by AVG before the exclusion was made and it simply needs to be replaced.

That did the trick...Thanks for the help everyone.

[TeMerc]

To add files to AVG:

Right-click the AVG icon in the system tray.

On the shortcut menu select Launch Control Center.

Click the 'Tools' tab, select Advanced settings...'

Scroll down or select 'Excluded files'

Click 'Add List' and copy and paste the following list of files:

C:\Documents and Settings\All Users\Application Data\Malwarebytes\Malwarebytes' Anti-Malware\rules.ref

C:\WINDOWS\system32\drivers\mbam.sys

C:\WINDOWS\system32\drivers\mbamswissarmy.sys

C:\Program Files\Malwarebytes' Anti-Malware\mbam.exe

C:\Program Files\Malwarebytes' Anti-Malware\mbamgui.exe

C:\Program Files\Malwarebytes' Anti-Malware\mbamservice.exe

Do the same for 'Directory Excludes'

Click OK 3 times.

Reboot your PC.

[GT500]

... If GT doesn't see this post and add to it after a day or so I'll ask him about it and I'm sure that he'll add it .

I've already updated the sticky with a possibly more permanent fix. There is the possibility that AVG may be corrupting our database by interfering with zlib.dll while MBAM is using it to write to the database (such as on an update).