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
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
Why are we even messing with anything other than WD these days?
Message
<blockquote data-quote="Andy Ful" data-source="post: 889081" data-attributes="member: 32260"><p>We differently understood the term detected by WD. When you see the notification "Actions needed in Windows Defender" it does not mean that WD actually detected something during the current Windows session. It only means that there are some not remediated events, and you can see this notification for a long time without detecting any new malware.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>In your case, the problem occurred because you tried to remediate the event after it was already deleted from the temporary location by the installer. The non-existent file could not be removed or quarantined by WD, but only allowed. It is a kind of WD history bug related to non-existent files that were properly detected but not remediated by WD.<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>The interesting thing is that this installer can drop different DLLs on different computers.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite132" alt=":unsure:" title="Unsure :unsure:" loading="lazy" data-shortname=":unsure:" /></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 889081, member: 32260"] We differently understood the term detected by WD. When you see the notification "Actions needed in Windows Defender" it does not mean that WD actually detected something during the current Windows session. It only means that there are some not remediated events, and you can see this notification for a long time without detecting any new malware.:) In your case, the problem occurred because you tried to remediate the event after it was already deleted from the temporary location by the installer. The non-existent file could not be removed or quarantined by WD, but only allowed. It is a kind of WD history bug related to non-existent files that were properly detected but not remediated by WD.(y) The interesting thing is that this installer can drop different DLLs on different computers.:unsure: [/QUOTE]
Insert quotes…
Verification
Post reply
Top