f14tomcat

I wasn't quite sure what to title this, so change as you wish. On the "About" page, the center column and data has a header of "Update Package Version". Time and again, for years now, I and others have had to explain to users and other members of the Forum I am on (Tenforums.com) that this is the Definitions Package, not a software package update. If the heading could be changed to Definitions Package Version or similar, it would eliminate the confusion. An example that just happened recently. _____________________________________________________________________ New updated MBAM ....just got it The component package did change in this example and triggered a restart. But the Update package version was thought to be the cause. Thanks for considering.

I'm showing 4.3.0.98, not 4.3.0.82.

Sorry, got carried away with pics! ☺️

FWIW... now on CP 1.0.1119 (Beta), and Pen Testing is still on separate tab inside Advanced.

https://www.tenforums.com/antivirus-firewalls-system-security/4469-latest-version-malwarebytes-post2084207.html#post2084207

I've left him a message on Tenforums, he's off right now.

Grab from request: mbst-grab-results.zip

Mine is here: Not here: 4.2.3 Beta I and others have this. Still others have it on main Settings screen. 😕

Thanks John for posting all the info and Tetonbob for the update. I've just gone back to non-beta in the interim via the Support Tool. Easy to get back on Beta when a fix is ready.

Same. Either individually or Delete All. Goes thru the motions, sound, confirmations, no delete.

Only had 2 "update" cycles, friend of mine had 4. Had the toast popup twice. Seemed to install ok, but I did a system restart just to be sure.... I have it playing in tandem with Defender and wanted to make sure it still would. Ran scans, all seems ok. Is there any advice from MBAM as to what to do, if anything, if you've already updated to 4.2?

My Beta first updated to 4.0.3 public, with the "Beta" remove from main page. Then a check for updates went to 4.0.4, same component package, "Beata " not on main page.

The following was intentionally done, but I wonder if it could happen naturally also. I started a Defender quick scan, immediately followed by an MBAM threat scan. I was not surprised by the results. All chugged along nicely, until MBAM got to the memory scan. Impossible to know where Defender was at that point. All displays froze, MBAM elapsed still running. A few seconds later, all froze. No mouse, no KB, nothing. Watched the i/o light while it created a multi gig dump file. No BSOD screen. Everything just stopped. 1 tap on the power button did an immediate shutdown. Booted back up fine, with the expected Kernel Power errors. Even though each had exclusions for the other, they are exclusions of the app objects themselves, not what they may have a lock on at the time. I suspect, from past experience with BSOD and MBAM 3.8.3, it was a DPC_WATCHDOG violation.... a timeout of a locked object request or a timed-out IRQ. If Defender was running a scheduled scan, and MBAM started a scheduled scan also, or vice-versa, I suspect this might occur. A system freeze. Unless the scheduling code was smart enough to sense another AV scan had been started, and wait. I don't know those details, so just a S.W.A.G. I did a full MR image prior (just in case......), so I was back up clean in 2 minutes. Just wanted to post my experiment.

@LiquidTension.... Re fonts. It's the size, but it's also, importantly, the font type. The combination of small and low contrast makes it rough to see. Old eyes here, so strain is a factor. Pipe dream hope: Dark theme? 😉

Actually, John, it bumped up a few seconds. I turned off heuristics (called AI now) to test, and time fell back close 3.8.3. Re-enabled and went back up to 1:15+ vs 50-55 seconds. Not a huge difference in the scope of things. Maybe it just takes time to "learn". May have to clean install, to rule all that out, AFTER deactivating license since I understand the Support Tool (formerly MBAM Clean) doesn't work with the beta. Adding the exceptions back is not an issue, a minute or two to do.