Jump to content

Protection Module Not Starting - Temporary Fix


Recommended Posts

***EDIT***

We just found out that this is an issue with the protection module shutting down because of an issue reading the database. I also just found out that this fix does nothing more than supress the error messages, and make the icon appear in the system tray as if the protection module was working. Do not follow the steps below.

Note that the developer in charge of the protection module is already trying to work through this issue. I can't say when a real fix will come out, but it shouldn't take too long.

***PLEASE NOTE***

I am not a developer, I am merely technical support, and this is just a temporary solution that should fix the problem for most people until the developers get a real fix out there. Check below the instructions for answers to questions I expect people to ask.

Here are the steps:

* Hold down the Windows key and tap the R key (refer to the screenshot below).

post-1983-1237708864_thumb.png

* Type services.msc into the field, and click OK.

* Scroll down until you find MBAMService.

* Right-click on MBAMService, and select Properties.

* Set the Startup Type to Manual, and click OK.

* Close the services list.

* Download and run this utility, which will install the temporary fix. This fix installs in about 2 seconds, so when that black box dissapears it's done.

* Restart your computer. Everything should be working OK now.

Answers to questions I anticipated:

* Will this temporary fix leave me with less protection than an actual fix cooked up by the developers?

- No. You you will get the same level of protection, it's just that I'm using a trick to get the protection module to start when Windows is failing to do it automatically.

* Why can't the developers just use your little trick to fix the problem?

- Because it's sloppy, and should only be a temporary solution.

* You say this trick is sloppy. Will it affect anything else on my computer in ways I wouldn't want it to? Will it do anything bad?

- No. There is the possibility that it might add a fraction of a second to your computer's startup time, but other than that it cannot hurt anything, and mess with anything else.

* How does this sloppy trick work?

- Basically it adds a startup item that calls the command to start MBAMService instead of letting Windows try to do it. Like I said, it's sloppy, but it works, and it will be easy to delete when the real fix comes.

* Why does your sloppy little trick work when Windows can't start the service on it's own?

- I have no idea. The developers need to do some testing, and see if they can figure out what is going on.

Possible Issues

* This temporary fix may not work on Windows Vista when the UAC is enabled. I did not have a 32-bit edition of Vista to test in. If this is an issue, I can add a manifest file to the solve it, but that would mean that you would get a UAC popup on every startup until the developers come up with a real fix, and you delete the temporary one. Please give me feedback on this if it is an issue.

post-1983-1237708864_thumb.png

Link to post
Share on other sites

Thank you.

Another question or two about this temporary fix ...

On the "easy to delete when the real fix comes" part ... if I put this fix on a clients computer will I have to return or hookup remotely later to "delete" this temporary fix when the real fix comes or do you think that part of the real fix will include MBAM being aware of this temporary fix and automatically looking for it and deleting it? The answer will help me decide whether I just use the fix on systems I have frequent contact with only and not to put it on clients systems that I may not have access to for a long time or whether it will be ok to put it on both systems because I won't have to schedule a return visit or service call to remove the temporary fix.

I see under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run both the new entry for the temporary fix as well as the original /starttray entry for mbamgui.exe. Would I be correct in assuming having both of these will be fine for now and the error message won't pop up because the original entry is still there?

Thank you,

- David I

Link to post
Share on other sites

On the "easy to delete when the real fix comes" part ... if I put this fix on a clients computer will I have to return or hookup remotely later to "delete" this temporary fix when the real fix comes or do you think that part of the real fix will include MBAM being aware of this temporary fix and automatically looking for it and deleting it? The answer will help me decide whether I just use the fix on systems I have frequent contact with only and not to put it on clients systems that I may not have access to for a long time or whether it will be ok to put it on both systems because I won't have to schedule a return visit or service call to remove the temporary fix.

Right now I do not know the answer to this question. I will talk to the developers about adding a check to the installer so that if the temporary fix was used, whatever update they come out with will remove it upon install, but I can't speak for them so I don't know if it will happen.

I see under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run both the new entry for the temporary fix as well as the original /starttray entry for mbamgui.exe. Would I be correct in assuming having both of these will be fine for now and the error message won't pop up because the original entry is still there?

mbamgui.exe was not affected by this bug. This is only an issue with MBAMService. So, in short, both of those startup entries are needed for everything to work properly.

Link to post
Share on other sites

Using the latest database update (updating through normal means) seems to be working fine after testing the logout/login to different account test.

What advice might you have regarding someone (myself on a client's system) installing the briefly mentioned and retracted "MBAMService-Fix.exe" that put an entry on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run key?

If I had easy access to that system right now I would remove it but I delivered that system to the client with that temporary fix already in place before I saw it was retracted. (note: even though it wasn't a real fix it was settling to the customer to not see an error message.)

What if I don't get to it today (via remote access or actual visit) or in the next few days ... do you see any problems which should indicate I should really get to that system asap to remove it?

Is there an uninstall for that temp. patch or is it fine to just remove that addition to the registry key?

Thank you,

- David I

Link to post
Share on other sites

What if I don't get to it today (via remote access or actual visit) or in the next few days ... do you see any problems which should indicate I should really get to that system asap to remove it?

No. There's no way it can cause problems. The program MBAMService-Loader.exe that is run on startup just calls the command net start MBAMService and then exits. Your customer's PC will work fine using that method to start the service instead of it starting the traditional way.

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.