Solved MalwareBytes 2.0.1 taking forever to scan

[Layback Bear]

Thanks for the offer of all the help.
During all the things I have done today I have cleaned out the minidump so I will save it the next time so Golden can take a look.

I will try and get the new beta version and see what happens.

 

[Layback Bear]

Malwarebytes beta 2.0.2.1007 will not download properly their for will not install. I have no idea what this means.
No mini dumps to show.

Install Error (at 69:177):
External Exception E06D7363.'

Tried both I.E. 11 and Firefox 28.

Update:
Removed 1.75 and tried to down load and install 1004 and got this.

Internal Error (at 57:177):
External Exception E06D7363,'

 

[AdvancedSetup]

Malwarebytes beta 2.0.2.1007 will not download properly their for will not install. I have no idea what this means.
No mini dumps to show.

Install Error (at 69:177):
External Exception E06D7363.'

Tried both I.E. 11 and Firefox 28.

Update:
Removed 1.75 and tried to down load and install 1004 and got this.

Internal Error (at 57:177):
External Exception E06D7363,'

Rather odd to say or think that nothing is wrong with your computer when thousands of other users can download these files without an issue. I'm not saying your infected but surely something is going on there that is not normal.

1. Please try the following and let me know if this corrects your issue or not. - MBAM Clean Removal Process 2x
2. If that does not correct the issue then please read the following and post back the requested logs. - Diagnostic Logs
3. NOTE: There is an FAQ section with valuable information located here: - Common Questions, Issues, and their Solutions
4. NOTE: I would also highly suggest you try installing the new beta which has corrected some previously reported issues (each of your previous installs were the original build 1004 not 1007 ): - Malwarebytes Anti-Malware 2.0.2 Public Beta

Thank You

 

[Layback Bear]

I have the Malwarebytes I.D. # and Key # on a print out will that do to activate again? It is from cleverbridge.

 

[Layback Bear]

Thanks for your quick reply.
So far so good. Activated again, updated, scanned.
The only changes I did was remove scheduled task.
I always check several times a day for updates and scan very often.

I will not try your 2.0.2 beta.

Update:
So far so good with 2.0.2. Install, updated and reboot.
Doing a scan now with the rootkit included.

 

[AdvancedSetup]

Make sure to reboot the computer again after install to test it out with startup, etc.

 

[Britton30]

Thanks for your quick reply.
So far so good. Activated again, updated, scanned.
The only changes I did was remove scheduled task.
I always check several times a day for updates and scan very often.

I will not try your 2.0.2 beta.

It cut over 3 1/2 hours from my custom scan.

 

[Layback Bear]

AdvancedSetup thanks for the reminder about the reboot. I'm a boot crazy person. I did reboot and Malwarebytes was started and on my Taskbar live and well.
It's located in msconfig Service where it should be and starts at boot.

Much faster and it doesn't stop on the jpg.

 

[AdvancedSetup]

Just a minor technical note about MSCONFIG as I see quite a few users on various sites using it as a Startup Manager. It is a Diagnostic Tool not a Startup Manager. If you're using it as a Startup Manager then you cannot use it as a Diagnostic Tool.

If you want a good free Startup Manager then I would recommend using Autoruns for Windows - TechNet Or if you want something even better (there is a free and paid version) I would recommend WinPatrol by Bill Pytlovany

Either one of those programs can easily manage what starts up. In the latter it can even delay it if wanted. Then that frees up your MSCONFIG program to be used for what it's really meant for as a Diagnostic Tool.

.

 

[Layback Bear]

I have use this before.
Autoruns for Windows - TechNet

I never understood the difference between not allowing something to start at boot with msconfig or the autoruns program.
They both seem to do the same thing in the same way.
With autoruns you can dig deeper into the system if one cares to.

I have read this and it does make things complicated for a very simple task. That is probably because of my lack of knowledge.

Some more good reading.

http://social.technet.microsoft.com...le-and-enable-windows-7-startup-programs.aspx

 

[scr]

Just a minor technical note about MSCONFIG as I see quite a few users on various sites using it as a Startup Manager. It is a Diagnostic Tool not a Startup Manager. If you're using it as a Startup Manager then you cannot use it as a Diagnostic Tool.

If you want a good free Startup Manager then I would recommend using Autoruns for Windows - TechNet Or if you want something even better (there is a free and paid version) I would recommend WinPatrol by Bill Pytlovany

Either one of those programs can easily manage what starts up. In the latter it can even delay it if wanted. Then that frees up your MSCONFIG program to be used for what it's really meant for as a Diagnostic Tool.

.

Another free start up manager with delayer is Startup Delayer Overview | r2 Studios

There is a paid for Premium version and a free Standard version. I've been using the standard version for about a year or so.
Download Startup Delayer | r2 Studios

 

[Britton30]

Yeah Autoruns and WinPatrol do make things more complex than needed.

 

[andrew129260]

I always use ccleaner as a way to manage/delete my startup entries.

The problem with msconfig is just like advanced setup stated. It is meant as a troubleshooting tool, not a permanent way of managing your startup programs. I believe the reason is when you disable things in msconfig, it grows a huge list of items that are disabled or enabled. As that list grows bigger and bigger, it slows down windows at boot due to the fact it has to look at that list to decide what to start up. I have seen some systems that were "fixed" by an IT guy and msconfig had a massive 2 or 3 page list of startup entries that were disabled, but due to the fact windows had to look at that long list at boot, it still slowed down the boot time. And some of them reappeared anyway.

I go into ccleaner under tools and startup and delete any disabled ones there, meaning the list is cut down from 100 random items down to 3 or 4 depending on the system. So even though msconfig might disable them, it is not meant as a permanent solution.

Another thing I want to add: It is always safer to uncheck the program that is launching at boot in the programs settings if the option is available.

From wiki:

"MSConfig is a troubleshooting tool. The main function of MSConfig is to temporarily disable or re-enable software, device drivers or Windows services that run during startup process to help user decide the cause of problem."


http://en.wikipedia.org/wiki/MSConfig

 

[UsernameIssues]

I always use ccleaner as a way to manage/delete my startup entries.
~~~
...it slows down windows at boot due to the fact it has to look at that list to decide what to start up.
~~~

No, a large list of startup items that are disabled via msconfig does not slow down the boot process.

And that part of CCleaner is sort of an interface to msconfig. Look at msconfig, then disable something via CCLeaner, then look at msconfig again.



msconfig works exactly* like CCleaner and Autoruns.

*within the context of disabling startup items in the registry.

Removing a check by a line item in any of the 3 apps mentioned above - removes the entry from the areas where Windows looks for start up items in the registry. The app then stores that disabled entry in an area of the registry that is not parsed during boot.

CCleaner and msconfig BOTH move startup registry items to here:
HKLM\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupreg

Autorun moves startup registry items to here:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\AutorunsDisabled\

If updating or re-installing an app adds the startup item back, then disabling it again using msconfig or Autoruns will add another entry in the area where these apps keep such lists. (CCleaner tries to manage/remove the duplicates. CCLeaner does not always get it right - so duplicates can still appear.) These "disabled duplicates" from all 3 of these apps can be manually cleaned from the registry.


If the startup item being disabled happens to be a shortcut/file in an OS startup folder, then that shortcut/file is moved to a folder that is not evaluated during boot. msconfig moves these items to here: ...\Windows\pss


There are reasons why one should not use msconfig (or even Autoruns) to permanently disable stuff, but slowing down the boot time is not one of them.


caveat: the statements above are generalizations. They are true for most cases - but not in every single case. This post was not meant to be a white paper on how these 3 apps handle disabling startup items.

edit: to quote a wise forum member

And sorry if I came across as rude. Was not my intention in any shape or form.

 

[andrew129260]

@usernameissues

I specified delete in ccleaner, not disable. So does that still hold true?

 

[UsernameIssues]

Deleting a registry based startup item using CCleaner or Autoruns does just that: deletes the registry entry. The entry is not moved elsewhere in the registry.

 

[Layback Bear]

I now have Malwarebytes 1007 on both computers and they do work well at this time.

 

[andrew129260]

Deleting a registry based startup item using CCleaner or Autoruns does just that: deletes the registry entry. The entry is not moved elsewhere in the registry.

So deleting a startup entry is better then disabling it correct? I always delete instead of disable when a user has a ton of unnecessary startup items.

You were just correcting the fact that having a long list of disabled items does not slow down the boot? That has been my experience anyway, but I enjoyed the added info

 

[UsernameIssues]

Since this is a public forum and all level of users might read this, then I'll say:
Deleting might not be the best for some users.
They might not know how to put stuff back...
...if things don't work as desired.

For those that you support, they know to come back to you if things are not to their liking... so, yes, you can delete as long as you know how to restore the startup item if they wish that. e.g. maybe they wanted the laptop's glide pad to do the extra stuff (likes flicks & zooms) that only works if an extra app is running at startup.

I can not see how having tons of msconfig disabled startup entries could slow boot time. Unfortunately, when folks like us clean a computer, we usually fix/clean lots of stuff & then reboot... so it is hard to say which cleanup helped the reboot time. I'll play with it more later.

You could always check your reboot times with this tiny tool...
http://www.sevenforums.com/tutorials/720-restart-time.html
...after removing only those msconfig entries.

 

[ThrashZone]

All I know for sure is any Adobe product on startup is a pain,
Creative cloud especially,
I'm not syncing anything it still bogs down startup,
The only slight trick is to enable the buggers before opening it to check for updates otherwise if there's a new version it will re-add the cc entry and Adobe updater,
Same goes for Flash I believe,
Cheers.