wijllie

Great news, I was almost gone back to 1.46...

Actualy the log doesn't say anything, I looked it at that time but didn't kept it. A good thing (also for support) would be a more speciffic logfile. So not only "time - updated" but time - sort of update (manual/onboot/...) - nummer of defs downloaded and so on. Shouldn't be that hard to establish. Next time it occurs I can show you 2 logs with "time - updated" so imo not very usefull...

Will we have ever?

Hmmm, had hoped it would clarify the error. Hope someone can help you to get it running...

Post eens wat er achter de "klik hier" staat hier ook...

Amen on that

Oh man, good to know, but now we have to check and do this manual too..! Even more work GGRRRRR... Handling a computer is getting problematic these days. Where are my Dos 6 disks...

I'm curious too, but I never click on a unknown file from a first time user Sometimes I'm faster then MBAM (Could be paranoia-light too...)

even if all dirs and files are excluded in both programs?

True, they are heavier. But I like it heavy and clean instead of light and infected This was actually the reason to run and test MSE on that laptop. If I would have sticked with AVG you would never had heard from me (so blame it on MSE )

Never had that sort of issues with 1.46 so it could be a problem to enviroment AND the new MBAM. But not only enviroment because there hasn't anything changed here. Only MBAM has changed... By the way and for information, the crash today was on a system with NIS2011.

Yes and thanks for that ("long ago" should ring a bell) You made that help because the problem occurs on a regular base with many others. You know, there should be something done to the software to avoid this (after a while...) If such things keep going on I (and others) loose trust in such programs. (You realy get tired of it). It's like taking medicine for your toothpain: it helps at that time but the problem stays and probably gets worse. You can't keep taking medicine, the problem should be cured.

Sorry but that's BS, MSE is the reason why I had a MBR infection and had to install MBAM. Even basic AVG free or Avast free is better. I don't recommend MSE to anyone, (not saying that you do) on the contrary...

If you live in a country with DD/MM/YYYY date format (and use this on your computer) this is a auto-update issue which is known and will be solved with the next program update. If you use the MM/DD/YYYY date format like in the USA, well, it's something else!

SURE it affects updates! They are even sometimes resized to zero! (With a crash which follows...)

Sorry I have to say this but in my opinion there are some things realy getting worse since the 1.50 program update. I stated before that I never had issues on my 6 computers with 1.46 and after updating them to 1.50 (and 1.50.0.1 patch now) there are different errors and different annoyances which I never had in the 1.46 version. This is realy getting frustrating because I bought the previous version because it was so good and stable. Now again on one of my computers (Win XP SP3-NIS2011-MBAM Pro 1.50.0.1) I have a "UtilityReadFile failed with error code 32" which was visible in the log after a few popups: After spending hours to fix MBAM here and there I know now I just have to delete the rules.ref to fix the problem, so I don't have to reinstall and clean MBAM like mostly asked by many support helpers here. Probably that RULES.REF gets a zero filesize because an update error occured. The rules.ref and other important MAMB files and dir's are excluded in NIS2011. I've seen this error sometimes and always on boot, so I guess I better disable the ONBOOT auto-update rule to avoid this. By the way IMO it is used to much this "uninstall, clean and reinstall" message here because that's the easy way to fix for someone who asks, but NEVER for the (novice) user and a real hassle. In many cases the problem comes back even after a reinstall, so please, SUPPORT, debug the program better because it's getting worse... I am on the edge to go back to 1.46 because I spent more on my computers to get mbam better working as something else... I urge support to get those things straighten out because I see more and more users have problems with crashes and failed updates and NOT related to their system. The most errors are about updating (bad http-request / UtilityReadFile error) and there are still some dateformat issues (uncorrect date of database and time format differences). I posted this in other messages in the forum and by email to support but it seems to be forgotten. I received the 1.50.0.1 patch from support after pointing to the dateformat/update errors which solved them partially but the case was "closed" and I couldn't get them to look further, they simply refused. A PM to R.D. is not answered. So I even don't know anymore what to think about support. I don't know if it's the program or a instabillity issue with the update servers, all I can say is my internet connection is superb and tested with tracert by MBAM support. I realy hope those things get sorted out because I like(d) the program a lot. Imo the beta 1.50 was stopped to early, also because of the big program changes which came with it. Server stability (for database updates) should be closely watched. Feedback is not realy needed, problem is solved for now till it happens again some day. If other users have the same error they know now how to fix it simple with deleting the file instead of reinstalling the whole program. That's the reason for posting and to ring the alarm bell Regards, Wijllie

Never heard of Comodo, will give it a try Do you use it on XP or/and 7 ? Any other comments regarding to this program? Since it is an all in one, do you still realy need mbam?

Avast AV free edition, which runs fine along with MBAM and MBAM is excluded and vice versa. After a while the database was sync again but I am 100% sure that there was a delay at a moment between the 2 different operating systems.

Yeah, I hope the developers can add an animated icon soon, shouldn't be that hard to program... And not only for auto scans, also for auto updates. About every program has this feature and you know at least what the program is doing...

Hi Mainard, thanks for your response. 1/ 1.50 Pro on all my home computers. Deleted the log but will post next time the event occurs. But I've looked at the log, all was fine, updates ok only that my Win7 system used a lower number compared to my XP system. Manual update said I had the recent one, no errors in log. 2/ Since XP doesn't ha a delayed service feature my 5 computers with XP start toghetter the AV/Firewall and MBAM at the same time without any problems. So is this delayed startup specially for Win7 or only "to be sure" it doesn't conflict? What I want to know is if I could start it undelayed (and when necessary files of MBAM excluded in the other progs) Thanks

Then I believe it's time the experts on this forum help you to go trough the steps needed to help you with the malware. If you have the Pro version you can also contact support directly with email.

after a Google about 0X001a624b it seems it is malware related after all. (A lot of posts are pointing to it so...) One solution I've seen was RENAMING the .exe of MBAM so it could start. It seems some malware disables MBAM and S&D Spybot. Mostly AV progs run but do nothing (there goes your money..) If you rename the .exe and are able to start MBAM run a full scan and delete possible malware but DON'T forget to rename the .exe of MBAM to it's original name BEFORE it asks you to reboot...

Hmmm all that info sounds like a computer related problem (hardware- disk or memory) try a windows harddisk check for errors or swap memory if possible to test this and rule out... (would I do to pinpoint the problem) Is MBAM the only program which? has problems

Today I saw that for my XP systems the current update was 5256 and when I started my laptop with Windows 7 it was 5251. Strange because the 5251 date is from yesterday. Did try a manual update but no updates found for Win7 although the XP system has a recenter number and datet today... -> Question: are different databases used for different systems? In Windows 7 the startup for MBAM is set to "delayed autorun" in services. Xp doesn't has that delay feature and in Win7 it takes quite long now till MBAM starts. -> Question: is this delayed startup necessary for Win7 or needed for some reasons? Thanks in advance.

I had sortlike problem a year ago with AVG but a short Google pointed me to a quick solution. Ah well, all programs suffer from time to time from errors or other issues, even Kaspersky is not secure from hackers. If MBAM had no issues this forum would be obsolete