f14tomcat

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.

Decided to try this out. Installed fine (overlay, not clean). As noted, it's a different UI, takes a little while to figure out what's where, and why! Don't care for the micro-font, old eyes have trouble reading small characters like that. Maybe that's change. Don't care for the animations, toy-like to me. Just IMO. Takes a bit longer to do the same manual scan. All machines will be different, but 3.8.3 normal scan time here was 50-55 seconds. Now 1:10+. Now, the one discovery I made after peeling back every option and it's details. If you have any Exclusions set up in 3.8.3, don't expect to find them in b4.0 where you would normally look. Because that option is not there anymore, not there labeled as "Exclusions" like before. You need to go into Detection History, where all the Quarantined items will be, if any. Your exclusions, the ones you manually made, will be under Allowed List. I guess the assumption at MBAM is exclusions are only after they have been detected, and you choose to allow them anyway. This is not always the case. MBAM themselves recommends in their forum to add Exclusions for Defender, and supplies a complete list. How accurate all that is for this Beta, I do not know. They were retained when I installed b4.0. MBAM link for recommended exclusions: https://forums.malwarebytes.com/topic/200162-exclusions-for-windows-defender-users/ In any case, until and if this is changed, here is where to look. You can still add/remove Exclusions. This is a link to a post I made on Tenforums.com with this same info. A fellow member there suggested I post here, also. https://www.tenforums.com/antivirus-firewalls-system-security/4469-latest-version-malwarebytes-post1708472.html#post1708472 Hope this helps.

Staff said yesterday that by Monday they would have reviewed the Zip files from all of us, and have some answers. It's a weekend. Now be patient and wait for the results. Running the "download" does not in itself fix anything, just an info gathering process.

Just got the second one this morning. Here's the Zip! ☺️ mbst-grab-results.zip

Will post the grab if second occurs. Only had so far about 4:30 today.

Will do! Thanks for quick reply.

Just received this popup after resuming from sleep. What does it mean? I thought it may have been a delayed notification, but when signing into the forum, there were none. Thanks,

I may have been pre-mature in reporting the latest Beta fixed the issue. It's back. I've made no changes that would affect it, other than normal daily use. I, also, had tried all the delayed-auto mods, as posted several weeks ago, and got the same results as Atrus. The issue still persists, even with the latest Beta. FWIW, also has exact same symptoms on any Insider version, current being 18329. And on a second 1809 dual-booted on same machine.

P.S. - I restarted 3 times, just to be sure! 😉

I'm happy to report the latest Beta just installed today has corrected the sign-on lag issue. It was not explicitly stated in the release notes, but I read between the lines. Thanks for your efforts.

Thank you. Still status quo.

@LiquidTension Last chore completed. The clean boot scenario. 1) With all user services disabled except MalwareBytes, and all Task Manager Startup Items disabled, the result was the same.... short 2 second delay for Login Box. After PIN entry, "Welcome", "Waiting on User Profile Service", "Preparing Windows" - 12 seconds to Desktop. 2) As an extra step, after putting everything back to normal, I set the MalwareBytes service to Automatic (Delayed Start), removed the 15 second delay in Protection setting, and rebooted. Instant Login box, and <2 seconds to Desktop. MBAM took forever to initialize (expected), but came up normal. It did seem to mess up the Defender icon in the Task Bar, though. Icon was invisible, but empty space was showing text on hover-over, and was clickable. May be just a fluke this time, though never have seen that before. All exclusions are in both MBAM and Defender. IMO, lot of things pointing to the MBAM service itself. That's just a S.W.A.G. 😉 Hope to hear back..... f14tomcat