Jump to content

DeGraff

Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by DeGraff

  1. BTW, no joy with 3.0.6.1469 2017/01/25 - All computers with this version of MBAM still suffer from this bug, including a brand new client computer that I unboxed and set up last week. As this constitutes a total clean install in every way, it really speaks to the pervasiveness and repeatable nature of this issue. Please fix this issue and the issue of one or more realtime protections occasionally being off at boot time soon! Until these items are fixed, IT and users cannot trust MBAM to always have them protected.
  2. Are you sure? Try this: Under "Scan Schedule" create a "Custom Scan", click "Customize Scan", make sure the bottom four checkboxes are checked including the last one ("Scan for Rootkits"), check one or more drives on the right, click "OK" on "Customize Scan", click "OK" on "Edit Scheduled Scan", then go right back in by clicking "Edit" and "Customize Scan" and you will most likely find that your drive selection(s) that you just made are missing. Furthermore, when this scheduled custom scan runs, it most likely will not create a "Scan Report" in "Reports" nor scan any files on the "selected" drives as evidenced by how quickly it completes (a minute or two instead of an hour plus for most computers I am responsible for), even though the dashboard will show that the scheduled scan ran.
  3. One or more of the protections often are switched off when a computer is booted and can get switched off if the computer is left idle for a long period of time. This seems to be an annoying "feature" of version 3.x including the latest 3.0.6. The only workaround I have found is to make sure the icon is always visible in the system tray (bottom-right), educate your users to vigilantly watch to make sure there are no triangles in that icon, to not do anything on the internet or e-mail while a triangle is present, to always click "Fix Now" on the placard when it comes up, then reboot if the triangle doesn't go away in about 5 minutes after clicking the "Fix Now" button or if they missed the placard. If you can teach them how to check the settings for protection, that will provide the possibility to clicking the sliders if they missed the placard, but usually the sliders will get stuck "enabling", which you should wait about 5 minutes to see if it will enable without rebooting, and reboot if they are still stuck. It can take as many as 3 or 4 reboots with "Fix Now" and/or changing sliders before everything gets fixed, especially if you have received Microsoft updates (manually or automatically). Also, at all times it is advisable during computer bootup to not enter your login password into Windows until the initial flurries of drive activity settle down (this is drivers and other infrastructure stuff loading in the background), which gives you a much more stable run of Windows with all intended background programs running. On most computers there are two or three flurries of intense drive activity with a brief pause between them, solid state drive computers take 30 to 60 seconds normally to settle down, old style rotational 5400rpm hard drives can be as much as an intolerable 5 minutes. The value of this advice is true for all Windows versions XP through 10, prior to XP there was an administrator setting that could be set to cause Windows not to present the login box until this condition was achieved. Pressure from Apple caused Microsoft to change this and to rush to show the desktop or login options before the computer is fully ready, which would work if Windows reliably loaded everything in the background, but "reliably" is sadly not the case. If you have ever noticed that not all of your icons showed up on the right, this is evidence of the problem and a warning.
  4. Once you start using "Custom Scan", you will find the problem escalates: The checkbox for "Scan for Rootkits" will stay checked if you have the latest 3.0.6 clean installed, but the drive selections will not stay checked (Click "Edit", click "Customize Scan", check the desired drives, click "OK" on "Customize Scan", click "OK" on "Edit Scheduled Scan", then go right back into "Edit" and "Customize Scan" and you will find the drives that you had just checked are not checked). This is not just a visual bug, the custom scan will not actually scan the files, and usually will not place a scan report in your history. This happens on all computers I am responsible for that have version 3.x installed. The original topic on this is "Custom Scan Forgets Drive Selection" started by me on January 11. The problem still exists today and is the reason I have not upgraded any more of the hundreds of client computers I am responsible for from 2.x to 3.x. I just setup a brand new client computer a few days ago (i.e., totally clean brand new install of everything) using 3.0.6 and the bug is present on that computer as well. The weekend full in-depth custom scan shows having run on the dashboard, but there is no report and no indication that any files on the drive were actually scanned.
  5. Follow-up: If you do a complete clean removal including manually deleting the "C:\Program Files\MalwareBytes" directory structure after Clean runs, but before clicking its "Reboot" button, the malformed registry entry with the forward slashes gets fixed to a working one with back slashes, though still ugly in "shouting" upper case and missing the technically required surrounding double quotes (technically required because of the space in "Program Files"). The source of the malformed registry entry malady seems to be if Anti-Malware was upgraded from 3.0.4.1269 2016/12/08 to 3.0.5.1299 2016/12/19 without doing a clean removal between them. This error has occurred on several computers, and all were repaired by the clean removal / reinstall procedure.
  6. I have done that many many times on at least 10 different computers suffering from this critical malady, as well as the ultra-critical "forgetting the configuration" malady which is often followed by the "false notification of new version" malady which causes an infinite loop of reinstalling the same 3.0.5.1299 version of the software that almost immediately informs you that "there is a new version" again, and the ultra-critical "forgetting your license" malady that occasionally occurs. Technical details on Operating systems in use, Anti-Malware versions involved, and Clean versions used: Operating systems in use were Windows XP-32 Professional, 7-64 Ultimate, 10-64 Professional. The Anti-Malware versions in question were 3.0.4.1269 2016/12/08 and the newer 3.0.5.1299 2016/12/19. The Clean removers used were 2.1.1.1001 2014/07/03 and eventually the newer 2.3.0.1001 2016/07/07 when it was made available in December. I am very much looking forward to the results today as I attempt to fix 5 computers (1 Windows XP-32 Professional and 4 Windows 10-64 Professional) using the just released Anti-Malware 3.0.6.1469 2017/01/25 version and the still current Clean 2.3.0.1001 2016/07/07 version. I wish there was a specific Clean for 3.x versions that deletes the "C:\Program Files\MalwareBytes" directory structure and its contents so that I don't have to manually follow-up and perform that function before allowing the Clean program to reboot the computer, as well as cleaning up any other 3.x version specific items that I do not know about.
  7. The upgrade to Malwarebytes 3.0.5.1299 introduced a bug not present in 2.x, which I labelled "Custom scan". When you create a "Custom Scan" in "Settings" / "Scan Schedule", "Operation Type" = "Custom Scan", "Schedule Frequency" = "Weekly", "Recurrence" = "1 week", and click "Customize Scan", put checkmarks in "Scan Memory Objects", "Scan Startup and Registry Settings", "Scan within archives", and "Scan for Rootkits", then select one or more drives (e.g., put checkmarks on drive "C:" and "D:"), and click "OK" and "OK" to save the settings; the program promptly forgets the selected drives. You can observe this behavior two ways: 1) just go back into the settings and you will notice the checkmarks missing from the drives that you had just put there moments before, and 2) wait for the scheduled scan to execute - no files will be scanned, and you may not even get a scan report. Some computers get a report showing 0 files scanned, others do not even get a scan report as if the scan never happened, however on all computers the dashboard shows the last scan as having happened when it should have, even if there is no scan report present on that computer. O/S: Windows 10 Professional, all updates and patches. Reproducible: Yes.
  8. The upgrade to Malwarebytes 3.0.5.1299 introduced a bug not present in 3.0.4.1269, which I labelled "Registry". When you turn on "Settings" / "Protection" / "Startup Options" / "Start Malwarebytes at Windows startup" it places an entry in the registry that is malformed: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run Malwarebytes TrayApp C:\PROGRAM FILES/MALWAREBYTES/ANTI-MALWARE\mbamtray.exe Because of both the forward slashes instead of backslashes and the lack of enclosing double-quotes, this entry is bad and will not work. It should be: "C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe" Do not attempt to fix the registry, as Malwarebytes will just overwrite your fix with the bad entry again before the computer is rebooted. If you want to do a work around, turn off "Start Malwarebytes at Windows startup" and create your own task in Task Scheduler, [General] = "Run only when user is logged on", "Highest privileges = No", "Configure for = <your version of Windows>" / [Triggers] = "At log on", "Specific user - <user's account>", "Stop task = No", "Enabled = Yes" / [Actions] = "Start a program", Program/script = "%ProgramFiles%\Malwarebytes\Anti-Malware\mbamtray.exe", Leave "Arguments" and "Start in" blank / [Conditions] = make sure all check boxes are not checked / [Settings] = "Allow run on demand = Yes", "Run missed task ASAP = Yes", "Stop task = No", "Force stop = Yes". Note that you will get the known bug (see Known Bugs forum topic) warning you that "not all of your real time protections are on" each time you boot the computer, but this is a passing condition that will correct itself after a short time which you can check on the "Dashboard". O/S: Windows 10 Professional, all updates and patches. Reproducible: Yes, just be sure to click off the "Run" section and back again in Registry Editor each time you make a change in Malwarebytes to refresh what you see in Registry Editor.
  9. Malwarebytes 3.0.5.1299 has many bugs at this time (Upgrade, Registry, Warning, Custom scan). This one I labelled "Upgrade" - the one of this forum topic, which manifests itself as an infinite loop of 1) claiming there is an update, 2) downloading the same "MB3-Setup-Consumer-3.0.5.1299.Exe" installation file every time, 3) installing the same version again, 4) usually wiping out all of your configuration settings and sometimes including your Premium Lifetime license information, 5) forcing you to reconfigure and set everything the way it should be, 6) only to return to step 1 the next time you look at the main window. The previous version "MB3-Setup-Consumer-3.0.4.1269.Exe" did not have this behavior. Note that in step 2, the software downloaded the same file (I compared it byte by byte). Therefore, there is no hope for an end to the loop until the software downloads a different file (soon I hope). O/S: Windows 10 Professional, all updates and patches. Reproducible: Yes.
  10. If you select this setting, MalwareBytes will still ignore it from time to time. To get rid of the annoying popup (several times a day), 1) make sure "Check for program updates..." is checked, 2) go to "Advanced Settings" and turn off "Enable self-protection early start" and then turn off "Enable self-protection module", 3) go to "C:\ProgramData\Malwarebytes\Malwarebytes Anti-Malware" and delete "mbam-setup.exe" (what triggers the popups), 4) go back to "Advanced Settings" and turn back on "Enable self-protection module" and "Enable self-protection early start" if you wish those protections (I recommend them), and enjoy no more nags for a while until the software chooses to ignore the setting again. As for why I choose to update on my schedule, MalwareBytes ruined my Christmas / New Year's vacation by releasing a fatal update to all of my clients' computers on 2012/12/27 (verison 1.70.1.1100) which rendered all of their computers unable to boot up. Also, the current version (2.1.8.1057 2015/06/29) does not work on many computers (massive crippling delays causing boot times to exceed an hour or not boot at all except Safe Mode) requiring them to continue using 2.1.6.1022 2015/04/21. These reasons are why I always update security software manually after testing the updates on unimportant computers in my lab. I always keep definitions updating constantly (exclusively use the Pro edition) and add an update for 5 minutes after boot to the schedule.
  11. Motherboard based Intel video (DG45ID) running Windows XP 32-Bit Pro SP3.
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.