boombastik Posted October 10, 2019 ID:1339314 Share Posted October 10, 2019 After i shutdown my machine and then start it, with fast boot from windows 10 enabled the ipv6 fails to connect until i close malware bytes. This problem don't exist with version 3. Windows 10 last stable version 1903. Windows 10 in uefi mode. Intel LAN card I218-V with driver 12.18.9.10 and rss load balancing profile to numascaling. I attached logs and photos: mbst-grab-results.zip Link to post Share on other sites More sharing options...
LiquidTension Posted October 10, 2019 ID:1339327 Share Posted October 10, 2019 Hi @boombastik, Thanks for reporting this. We'll be looking into this further with internal IPv6 tests. To help troubleshoot: If you restart the machine (as opposed to shutting down/powering on), does the issue still occur? If Fast Startup is disabled and you shutdown/power on, does the issue still occur? Could you verify that if Web Protection is disabled in Malwarebytes prior to the shutdown, the issue does not occur when the machine is next powered on. What happens if you disable RSS? https://www.intel.com/content/www/us/en/support/articles/000006703/network-and-i-o/ethernet-products.html If you perform a clean boot (ensuring Malwarebytes Service is left checked/enabled), does the issue still occur? https://support.microsoft.com/en-gb/help/929135/how-to-perform-a-clean-boot-in-windows Link to post Share on other sites More sharing options...
boombastik Posted October 10, 2019 Author ID:1339346 Share Posted October 10, 2019 I removed the version 4 but because i checked the most questions i will answer. -Issue don't occur on restart. -Issue don't occur if fast startup is disabled. -I didn't test it. -Its the same. -My pc boot is at almost clean except a macrium reflect service and a creative sound card and i dont think that them has anything to do with the problem. Link to post Share on other sites More sharing options...
LiquidTension Posted October 11, 2019 ID:1339508 Share Posted October 11, 2019 Thanks very much for the information! Would you be willing to reinstall the Malwarebytes version 4 beta and perform some additional troubleshooting? It's not a problem if you'd prefer to stick with Malwarebytes version 3 for the time being. Link to post Share on other sites More sharing options...
boombastik Posted October 11, 2019 Author ID:1339512 Share Posted October 11, 2019 I will stick with version 3 for the time being and i will retest the next beta. An additional information is that the above logs that i uploaded here is when the problem exist. Link to post Share on other sites More sharing options...
LiquidTension Posted October 14, 2019 ID:1339769 Share Posted October 14, 2019 Okay, no problem. Thanks for the information you provided. Link to post Share on other sites More sharing options...
LiquidTension Posted October 16, 2019 ID:1340116 Share Posted October 16, 2019 We've been able to reproduce this and have a defect filed. Thank you for reporting. Link to post Share on other sites More sharing options...
boombastik Posted October 16, 2019 Author ID:1340122 Share Posted October 16, 2019 Thanks for reporting back! Link to post Share on other sites More sharing options...
the_hamster Posted October 17, 2019 ID:1340303 Share Posted October 17, 2019 Has the IPv6 defect been fixed? I downloaded the 4.0.2.44 version yesterday, and this a.m. performed the tests run by the OP and have in fact full IPv6 connectivity. Link to post Share on other sites More sharing options...
boombastik Posted October 17, 2019 Author ID:1340316 Share Posted October 17, 2019 This is not fixed but they recreated the bug internally. A simple run of test doesn't mean anything. You need to shutdown many times your machine to recreate it. Link to post Share on other sites More sharing options...
the_hamster Posted October 19, 2019 ID:1340489 Share Posted October 19, 2019 I do recall with one of the last 3.8.3.xxxx releases, I reported here on one of the Forums that there was clearly a IPv6 connectivity issue, which was soon fixed by I believe to be the last release version of 3.8.3.xxxx before the transition to 4.0. And despite repeatedly forcing restarts on two Win7 machines, IPv6 connectivity is retained w/ 4.0.2.44...but, YMMV, I do get that. Link to post Share on other sites More sharing options...
the_hamster Posted October 19, 2019 ID:1340490 Share Posted October 19, 2019 6 minutes ago, the_hamster said: I do recall with one of the last 3.8.3.xxxx releases, I reported here on one of the Forums that there was clearly a IPv6 connectivity issue, which was soon fixed by I believe to be the last release version of 3.8.3.xxxx before the transition to 4.0. And despite repeatedly forcing restarts on two Win7 machines, IPv6 connectivity is retained w/ 4.0.2.44...but, YMMV, I do get that. Whoa, let me correct that post by stating that it was in fact version 3.7.1.xxxx that was troublesome, and solved with 3.8.x beta 7 minutes ago, the_hamster said: I do recall with one of the last 3.8.3.xxxx releases, I reported here on one of the Forums that there was clearly a IPv6 connectivity issue, which was soon fixed by I believe to be the last release version of 3.8.3.xxxx before the transition to 4.0. And despite repeatedly forcing restarts on two Win7 machines, IPv6 connectivity is retained w/ 4.0.2.44...but, YMMV, I do get that. Link to post Share on other sites More sharing options...
boombastik Posted October 24, 2019 Author ID:1341391 Share Posted October 24, 2019 This is fixed in beta 4.0.3? If not i will bypass it for now. Link to post Share on other sites More sharing options...
LiquidTension Posted October 25, 2019 ID:1341523 Share Posted October 25, 2019 Hi @boombastik, Not in this beta release. We may release a new component update to beta users that has the fix for this issue. Link to post Share on other sites More sharing options...
boombastik Posted November 6, 2019 Author ID:1343387 Share Posted November 6, 2019 @LiquidTension This is also seems to be fixed. Can u confirm? Link to post Share on other sites More sharing options...
LiquidTension Posted November 6, 2019 ID:1343403 Share Posted November 6, 2019 We've been developing new Web Protection technology, some of which was present in the Malwarebytes version 4 beta, though is not quite ready for release yet and is therefore not present in the recent release. We hope to be able to fully release this in an upcoming update. In the meantime, you shouldn't encounter any issues with IPv6 connectivity. Link to post Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now