Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
General Security Discussions
The truth about Windows Defender on Windows 10 (Home & Pro).
Message
<blockquote data-quote="ForgottenSeer 72227" data-source="post: 778238"><p>Thanks for the clarification, this was my understanding as well!</p><p></p><p></p><p></p><p>I agree<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up (y)" loading="lazy" data-shortname="(y)" /></p><p></p><p>I gave it a try just to see what it was all about, it didn't slow down my system anymore than what WD does which is great. I think it is a good feature to have in order to help keep the OS more secure from malicious code trying to take advantage of an exploit via WD.</p><p></p><p>However, like you said it's still very experimental at this point and I think Microsoft still has some things to iron out before its ready for prime time. I have since disabled it as I found out (while doing very basic tests via ATMSO and the WD Testing grounds) that some of WD detection capabilities stopped working (on some tests) when the sandbox was enabled. Even though the sandbox should not have any impact whats so ever on WD detection capabilities, currently it seems to be conflicting with some of them (at least for me on 1809). Since disabling the sandbox, WD was able to pass those tests without issue, compared to when it was enabled. Personally I think people should wait until its all ironed out and officially rolled out before using it, just in case it is (unintentionally) affecting WD's protection capabilities negatively.</p></blockquote><p></p>
[QUOTE="ForgottenSeer 72227, post: 778238"] Thanks for the clarification, this was my understanding as well! I agree(y) I gave it a try just to see what it was all about, it didn't slow down my system anymore than what WD does which is great. I think it is a good feature to have in order to help keep the OS more secure from malicious code trying to take advantage of an exploit via WD. However, like you said it's still very experimental at this point and I think Microsoft still has some things to iron out before its ready for prime time. I have since disabled it as I found out (while doing very basic tests via ATMSO and the WD Testing grounds) that some of WD detection capabilities stopped working (on some tests) when the sandbox was enabled. Even though the sandbox should not have any impact whats so ever on WD detection capabilities, currently it seems to be conflicting with some of them (at least for me on 1809). Since disabling the sandbox, WD was able to pass those tests without issue, compared to when it was enabled. Personally I think people should wait until its all ironed out and officially rolled out before using it, just in case it is (unintentionally) affecting WD's protection capabilities negatively. [/QUOTE]
Insert quotes…
Verification
Post reply
Top