-
Posts
84 -
Joined
-
Last visited
Content Type
Events
Profiles
Forums
Everything posted by f14tomcat
-
Thanks. I did look around before I posted, could not find one.
-
This is minor, a cosmetic request. For years, and currently on 4.6.9, the revision number is displayed on the Title Bar upper left of the UI. i.e. - Malwarebytes 4.6.9. That no longer is there. Same for a hover over the systray icon, used to show there, too. Like I said, minor, but it was one of the very first things I noticed, and some of my friends on forums did also. Thanks for the indulgence. 🙂
-
Thanks! 👍
-
Logs............. mbst-grab-results.zip
-
Every night I run a manual scan just before shutdown. 90% of the time it finds this exact entry, a Spyware.Vidar class of malware. When I look for the file entry, it does not exist. It almost looks like a "one time" entry. I'm forced to clean and reboot. If i choose not to reboot, at SHUTDOWN MBAM will do the clean and RESTART, not SHUTDOWN. What is this odd entry that's being detected as malware and why does MBAM act this way? Thanks. Malwarebytes Scan Report 2024-03-04 013110.txt
-
Easy one first. DXDIAG attached. If I could simply resize vertically that would solve it. MBAM is not respecting space already allocated. DxDiag.txt
-
MBAM 5.0.17.99 UI sizing is too large and not vertically resizable. The bottom of the UI is cutoff by the taskbar and not visible. I have to use 150% scaling due to eyesight issues. MBAM 4.9 is not like this. Windows 22631.3155. Attached- with and without taskbar active.
-
-
latest 4.5.5 out today seems to be a bit confused! 😁 How can I be protected and not and do a great job but be careful? 🤣 Maybe just late in the day and my eyes are tired.
-
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.
-
-
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.
-
Version 4.2.0.82 Component Package 1.0.1017.
f14tomcat replied to RTL434's topic in Malwarebytes 4.x Beta
Same. Either individually or Delete All. Goes thru the motions, sound, confirmations, no delete. -
version 4.2.82 component package 1.0.1015
f14tomcat replied to Firefox's topic in Malwarebytes 4.x Beta
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? -
incomplete update from MB 4.0.3 beta to 4.0.4 final release
f14tomcat replied to Gt-truth's topic in Malwarebytes 4.x Beta
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.- 4 replies
-
- malwarebytes
- update from
-
(and 2 more)
Tagged with:
-
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.