Jump to content

f14tomcat

Members
  • Content Count

    64
  • Joined

  • Last visited

Community Reputation

1 Neutral

About f14tomcat

  • Rank
    Regular Member

Recent Profile Visitors

997 profile views
  1. 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.
  2. Same. Either individually or Delete All. Goes thru the motions, sound, confirmations, no delete.
  3. 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?
  4. 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.
  5. 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,
  6. @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? 😉
  7. 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.
  8. 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, do
  9. 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,
  10. 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.
  11. 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.
  12. @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. M
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.