Jump to content

Louiscar

Honorary Members
  • Posts

    40
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Good news. Thanks for the update. Looking forward to 1.42.
  2. Excellent! It's been a journey but I'm glad that finally I've got Malwarebytes up and running again.
  3. Great! This is exactly the problem I've been having and had given up. So had the guys here. http://www.malwarebytes.org/forums/index.p...19088&st=20 The problem is just the one file: .sys This makes a great deal of sense now because the error was a VB error and it's obvious that VB didn't like an extension with no name being passed to it. FIW. There is no need to dip out of windows or go into safe mode, just delete or rename the file and Mbam runs again. Perhaps this is worth a sticky as the developers didn't track this one down and others may be having this problem. thanks for your post.
  4. Interesting. Can you elaborate on that? I'd be interested to know : 1) What the 'issue' is 2) Why prevents the repair. Since I've been unable to establish any evidence of an infection it may be possible that I am suffering from the same thing so any infomation you can provide or point me to would be helpful. thanks
  5. Not sure if this is any help but to confirm that this is a problem on my computer which seems not to be related to a virus (if it is certainly no one has been able to identify it here). http://www.malwarebytes.org/forums/index.p...19088&st=20
  6. Sorry to correct you on this but the OP was referring to the VB error 5 not the system error 5 (which means access denied). The VB trapable error is indeed "invalid procedure or call" and it is a problem that I have been trying to sort out for some months now without any luck: http://www.malwarebytes.org/forums/index.p...19088&st=20 In my case this happens in ALL verisons including the latest v1.41
  7. Thanks for the heads up. Results are exactly the same. 11 seconds into the scan and 5742 objects the error appeared. Looks like I'm stuck with this one.
  8. I guess I'm stumped in that case since any newer version is unlikely to be different given that all previous versions ran perfectly at one time and now don't. It's unlikley to shed any more light on this strange problem. I'll of course try it but I'm not holding my breath.
  9. Thanks Ron, I've already installed that sp and it does nothing for the situation. I'll hang on for 1.41 however if this has a 'fix' for the right click mechanism then that's also unlikely to help as the right click is the only way I can scan files sucessfully. It's the menu system that is failing. This wouldn't be so bad but of course it means that I can't have memory, processes and registry scanned if that is indeed what mbam does before it gets to looking at files on the HDD. I presume the developers have not been able to get any clues from my last report? It seem fairly obvious this is a VB problem but the error is not that specific. Is there any possibilty that they have a debug version that would isolate the actual cause of the error?
  10. Thanks It'd be good to find out why this is happening. I've just got hold of a laptop the other day running xp pro. Mbam runs ok on that .. needless to say. I hope the info I last reported will give the developers a clue.
  11. Yes I've tried the fixes. The HJK thread - see the link, was aborted because as I say, Ron had to stop due to 'circumstances out of his control'. What has been done is in the thread and we leave it at a result [Post #24] (significant I think) which needs to continue from there. To recap that here: Mbam fails with this error when run via the menu. It will complete any scans successfully when you right click on a folder and choose 'scan with Malwarebytes". Even though the failure via the menu happens when it is in the process of scanning a file on the disk this is not the primary reason for the failure as those files can be scanned the other way without problems. This leads me to assume that some of the previous operations done via the menu are causing the problem which appears to build up since more often than not it's threshold is around 5700 'objects' before it errors.
  12. Hi, It's been suggested to start a new thread on an existing problem because (Ron Lewis) who's been helping me has had to stop due to circumstances out of his control. The problem: Mbam will stop after scannning around 5700 objects with a VB error. "Error 5, Invalid procedure or call" Basically I've tried a number of things suggested none of which have worked. The last finding is in post #24 which hasn't been addressed yet so if someone can pickup from here I'd be grateful. The pertinent finding seems to be that I can right-click and scan any set of files / folders without a problem. The problem arises when I try to do a 'quick scan' or 'full scan' directly from the menu. That appears to be some kind of clue. Here is the thread where you can see what has or hasn't been investigated: http://www.malwarebytes.org/forums/index.p...19088&st=22 Hope someone can take over on this.
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.