New
#11
same crash for me; I'll wait for the next release, not in a big hurry to update to a buggy OS..
same crash for me; I'll wait for the next release, not in a big hurry to update to a buggy OS..
Not quite, AV's use kernel integration for low-level protection, if the kernel code changes, the AV's crash.
PS: - or shall I say the AV's crash Windows...
BTW.. just checked https://support.microsoft.com/en-za/...-screen-errors
- very basic corrective issues - ie. either restore or uninstall - no specifics - why "collect some error info" if it's of no use?
I called it quits.
Do away with MBAM and it works.
Last edited by jadinolf; 12 Oct 2016 at 23:32.
Like most here after I set malwarebytes to not load at Win startup (it's in advanced settings, there's a tick box to uncheck that says start with windows automatically) and disabling Avast permanently (until it installs) worked this time. All this time I had exited malwarebytes and disabled Avast but forgot to tick the start at windows in malwarebytes so that's what finally did it for me. I reenabled it afterwards and I have the new build and malwarebytes loads correctly at startup after re ticking the box and avast is turned back on and rebooted a few times and so far so good. Good luck, hope it works for you, it was driving me nuts!! lol. I know it's only for testing and such but mine have been so stable I've been using for production for months each time but I do save early and often and backup anything important to an external I turn off when done backing up also so just know ANYTHING can go wrong and prob will but so far I've never had a lockup yet, knock on wood just filed installs and it just rebooted to the previous one but haven't ever got the frowny BSOD yet, knock on wood).
Faslane
I had success by disabling Malwarebytes from starting at Windows startup and disabling Avast permanently until the update was finished and I could turn all of a vast features back on but I got the blue screen of death :-( when Malwarebytes loaded so my computer rebooted after about 30 seconds and when it rebooted Malwarebytes was disabled so I really believe it and rebooted and it crashed again so I just check the box to say automatically start when Windows starts up and it crashed again so then I uninstall Malwarebytes entirely and now my computer is running perfectly with the update so my conclusion so far is that this version and Malwarebytes are incompatible so I would leave Malwarebytes disabled for now I haven't tried to see if it will run if I launch it manually or not yet though that's going to be my next test. That's what I personally have found so far. Good luck all,
Faslane
The solution I found that works fine, and retains MBAM for scanning purposes.
1. Completely uninstall your MBAM Premium (Revo Uninstaller does a good job Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems
)
2. Download and install the MBAM Free edition. Malwarebytes | Free Anti-Malware & Internet Security Software
3. Do Not activate the MBAM with your key. Leave it as the Free Edition.
The 14942 will install without rolling back at about 75%. And you will still have your on-demand scanner.
It's the MBAM service activated with the Premium that is causing the crash/rollback.
After 14942 install, Do Not activate the MBAM Premium with your key. It will crash the OS as soon as you start a scan.
TC
Actually, they know about it. It's in the release notes for 14946, which most people read after they've downloaded and clicked Restart!
- If you have 3rd party antivirus products such as Bitdefender, Kaspersky Antivirus, F-Secure Antivirus and Malwarebytes installed on your PC – your PC might not be able to complete the update to this build and roll-back to the previous build.
- Larger Windows Store games such as ReCore, Gears of War 4, Forza Horizon 3, Killer Instinct and Rise of the Tomb Raider may fail to launch.
And in Shawn's post...
Insider Announcing Windows 10 Insider Preview Build 14946 for PC and Mobile - Windows 10 Forums