Daggerheart

Hello, noticed today that Netflix Party extension was being blocked by the malwarebytes browser extension. I was unable to find additional information as per why that was happening. Was hoping someone could shed some light on this. Cheers

That's interesting, I do have my ipv6 networking configured for DHCP but my router is utilizing cloudflare as the DNS resolver and that's the what is being sent to my devices. I do know the 1.1.1.1 has caused some network shennanigans (not so much at home but at work) but it would be weird if the IPV6 DNS address was causing issues as well. That said did try to change from cloudflare to google's ipv6 dns and the issue persists. DNS Servers . . . . . . . . . . . : 2001:4860:4860::8888 2001:4860:4860::8844 1.1.1.1 1.0.0.1 8.8.8.8 This particular DNS config ping still randomly cuts out. Between 7 and 21 is where I turned on Web Protection $ ping google.com PING google.com(dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e)) 56 data bytes 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=1 ttl=115 time=10.1 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=2 ttl=115 time=9.99 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=3 ttl=115 time=9.82 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=4 ttl=115 time=20.9 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=5 ttl=115 time=9.79 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=6 ttl=115 time=12.2 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=7 ttl=115 time=9.59 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=21 ttl=115 time=9.75 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=22 ttl=115 time=9.87 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=23 ttl=115 time=10.4 ms 64 bytes from dfw28s04-in-x0e.1e100.net (2607:f8b0:4000:815::200e): icmp_seq=24 ttl=115 time=10.0 ms ^C --- google.com ping statistics --- 24 packets transmitted, 11 received, 54.1667% packet loss, time 23031ms rtt min/avg/max/mdev = 9.594/11.123/20.862/3.151 ms So Maurice ipv6 ping works just fine for you on the current stable version of mbam?

Hello Porthos, Please consider me a fly on the wall, I'm perfectly content with you guys coming up with a solution for the original poster and if that does not also fix it for myself I will of course go through the steps you've presented. Feel free to disregard my post about the windows version if it provides no helpful insight, I am still following this issue as there has yet to be a solution to said original post, or are you saying that has been addressed?

I'm just following up with some additional data Maurice, the initial post has a support tool report and this is a continuation of that initial issue which is still no resolved.

Just upgraded windows to version 2004 build 19041.329 and gave this another test running MB 4.1.0.56 and issue is still occurring. Figured I'd post some versions in here.

Just checking in, this still appears to be an issue, any further progress ?

I've been a big fan of mbam for a while, and certainly don't like that I have to disable web protection for ipv6, I certainly hope this gets addressed sooner rather than later, hopefully that priority list is getting closer to addressing this issue.