Protection Module won't start from xp user account

[Colonel Mortimer]

Hi

I'm running Win XP (SP3) with Panda CAV Free (which I think is excellent IMHO), Win XP firewall (as i'm behind a NAT and all other firewalls tried so far cause horrendous speed problems) and Malwarebytes Pro.

All runs fine from logons that have admin rights, but I cannot get Malwarebytes Pro protection module to open from limited user accounts (I understand that user accounts only have rights over own docs & settings folder but would still like to have protection module running to safeguard limited user accounts.

Each time I attempt to activate protection module I get the following error message "PROGRAM_ERROR_PROTECTION_MODULE (0,0, ProtectionEnable)"

Please see attached screen dump

Is their any way to activate the protection module whilst logged on from a user account or is this only possible via a logon with admin priviledges?

Many thanks in advance.

[AdvancedSetup]

Please do the following:

• Download and run mbam-clean.exe from here
  
• It will ask to restart your computer, please allow it to do so very important
  
• After the computer restarts, temporarily disable your Anti-Virus and install the latest version of Malwarebytes' Anti-Malware from here
  
  • Note: You will need to reactivate the program using the license you were sent via email if using the Pro version
    
  • Launch the program and set the Protection and Registration. Then go to the UPDATE tab if not done during installation and check for updates.
    Restart the computer again and verify that MBAM is in the task tray if using the Pro version. Now setup any file exclusions as may be required in your Anti-Virus/Internet-Security/Firewall applications and restart your Anti-Virus/Internet-Security applications. You may use the guides posted in the FAQ's here or ask and we'll explain how to do it.
    

[Colonel Mortimer]

Thanks for that - all sorted now.

I should add that I was still initially getting the same error message when attempting to start the protection module from a user account. What sorted things out was checking the "start with windows" option.

Thanks again.