Jump to content
John L. Galt

Micr$oft Edge & Insider Preview Build WIN10

Recommended Posts

You're welcome!  Believe me, I fell into the same trap -- not scrolling far enough.  Maurice showed me what to do. 

Share this post


Link to post
Share on other sites
1 hour ago, Maurice Naggar said:

Hi Brandonspopo.    See my post at this link

F.Y.I.   Running Insider Preview build 15025  with Malwarebytes v 3.0.6.1469  & its doing well.

 

Having similar experience with this build of windows 10 as well and MBAM working very well.

Share this post


Link to post
Share on other sites

Just got build 15058.0

All is well.  This seems very nearly the release or near-release Redstone 2.   There is no watermark on the desktop and no expiration date when looking at Winver.

Running with Malwarebytes 3.0.6.1469  with component update package 1.0.75.

Share this post


Link to post
Share on other sites
18 hours ago, Maurice Naggar said:

Just got build 15058.0

All is well.  This seems very nearly the release or near-release Redstone 2.   There is no watermark on the desktop and no expiration date when looking at Winver.

Running with Malwarebytes 3.0.6.1469  with component update package 1.0.75.

Insider build 15060 is out today.

Noticing that MB protections don't turn on sometimes on a boot.

Share this post


Link to post
Share on other sites

Hi Soozy,

Tell me, please, does this system have any antivirus other than Windows 10' Windows Defender ?  If so, which ?

Share this post


Link to post
Share on other sites

Just do a LOGOFF  ( from  the Start menu) and then click the power icon.   Then Restart.   This all just takes a few minutes.

This is a one time procedure suggestion.  Then lets see how it goes on this box.

I've rarely had issues issues while having Windows Defender.   I am assuming your box has no other security-type-add-on monitor.   (other than Win Defender).

Share this post


Link to post
Share on other sites

That's good to hear.

By the way, I got preview build 15060.0   yesterday.   Doing fine.   suprisingly the MS watermark is back , as is the May 15 expiration for the preview.

Share this post


Link to post
Share on other sites

Yes they are, but the 1607 changed to 1703 last build.

So a good sign we are getting close to RTM for Insiders.

Share this post


Link to post
Share on other sites

The Anniversary Update was version 1607 (YrMo) and rolled out in August.  Rumor has it that Microsoft will begin roll-out of Version 1703 on April 11, which is also the EoL date for Windows Vista.

Share this post


Link to post
Share on other sites
4 hours ago, Maurice Naggar said:

That's good to hear.

By the way, I got preview build 15060.0   yesterday.   Doing fine.   suprisingly the MS watermark is back , as is the May 15 expiration for the preview.

After getting build 15061 on the 1st boot it popped up that Real Time Protection was off.

Seems to only do it when we get a new build of Win 10.

Share this post


Link to post
Share on other sites

Soozy,   Wasn't there a Restart at the very end of the "update run"?

Has the issue re-appeared since the machine was last rebooted?

and if so, is there any non-default option set in the Settings of MB3 ?

Share this post


Link to post
Share on other sites

It does it at the very end of the Updating (3 phases) when you 1st log on and get your desktop.

It hasn't done it since then.

Share this post


Link to post
Share on other sites

I haven't had any issues recently with MB 3 and Edge at all.

Currently on Build 15061 (released yesterday).  No issues discernible.

Share this post


Link to post
Share on other sites

Thanks for that confirmation, John.

Same here on mine.   I have not had issues in Edge since a long ways back,  several previews back.   The Edge thing is a thing of long ago, imho.

 

To Soozy,

I would tend to think what you observed is a one-off, since it is only after a new preview build finishes.  I wonder also, if maybe yours has the Malwarebytes icon on taskbar, and perhaps that is where you noticed some visual cue.   What follows is just a suggestion for you to consider.

 

Windows Defender in Windows 10, it does have ability to add an exclusion.  There it allows for choices as to whether by file, or folder, or process.
Start Windows Defender.  Click Settings icon on upper right near top bar.
That brings up a Settings page displayed for it.  Scroll down to EXCLUSIONS. Click the Add exclusions.
Select "Exclude a folder"
Then use the GUI control to navigate to  ( and select) the folder
C:\Program Files\Malwarebytes\Anti-Malware
 

Edited by Maurice Naggar

Share this post


Link to post
Share on other sites

Maurice, my MB icon is hidden, but it is the pop up in the bottom right corner that I see.

I tried your suggestion, not sure it will make a difference since in the last several

builds the new Defender now sees MB as my AV. They used to both coexist. LOL

Share this post


Link to post
Share on other sites

I just installed MB on 15061 and it causes Defender to turn off with the default settings.  Should not happen without permission.

Share this post


Link to post
Share on other sites

That's been for several builds. Defender is now seeing MB as the primary AV.

You can set Defender to do periodic scans or scan manually.

Share this post


Link to post
Share on other sites
4 minutes ago, Soozy said:

That's been for several builds. Defender is now seeing MB as the primary AV.

You can set Defender to do periodic scans or scan manually.

Yes, but there is no indication that Defender has been turned off unless you actually open it up and have a look.  In my case I want Defender on so I have changed the setting in MB and turned Defender back on again. 

MB should ask permission to do this, not just hijack the AV. 

Share this post


Link to post
Share on other sites

MB is not hijacking anything, Defender has changed with the way it interacts with other software.  This change is programmed by Microsoft, not Malwarebytes.

Furthermore, if you were to install MB 3 on a clean system running build 15048 or newer (and maybe older, might be as far back as 15025) it would ask you about disabling Defender - but when you already have MB 3 installed, it doesn't ask, it just disabled, and that is due to Microsoft's coding, not any (new or old) coding in MB 3. 

This is a relatively recent change, and if you want I can find the exact Insider Preview build that it started happening on over at tenforums.com

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×

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.