- Jul 27, 2015
- 5,458
Much appreciated.The test you linked to had ConfigureDefender on High Settings that is with CFA off.
If I remember correctly CFA was tested and was the only one blocking the ransomware.
I will try to find that test...
Please provide comments and solutions that are helpful to the author of this topic.
Much appreciated.The test you linked to had ConfigureDefender on High Settings that is with CFA off.
If I remember correctly CFA was tested and was the only one blocking the ransomware.
I will try to find that test...
First one I could find from @Solarquest :Much appreciated.
Product: Windows Defender, folder control, default settings + Emsisoft Browser security
Static (On-demand scan): 1 /2
Dynamic (On execution): 1*/1
Total: 2*/2
SUD: all samples missed on static
File encrypted: yes, but not in protected folders (*WD blocked encryption but too late for desktop files)
Final status: System infected-> files encrypted
Abused powershell command from the test link:Yes, didn't you quoted my post with that test link or are you talking/thinking about something else?
Also again, I'm getting confused. Simple Powershell command?
I don't think CFA was used here, only Configure Defender on high settings (mains CFA off).Abused powershell command from the test link:
(MISS) Encryption started
Didn’t Windows 7 teach us not to store files on the desktop? I’ve always hated a cluttered desktop.Quoted from post #42 @Gandalf_The-Grey clipped from the findings of Solarquest: "too late for desktop files)
Final status: System infected-> files encrypted "
Thanks very much, this told me all I needed to know.
You're so very welcome, but I would take another part to quote: yes, but not in protected foldersQuoted from post #42 @Gandalf_The-Grey clipped from the findings of Solarquest: "too late for desktop files)
Final status: System infected-> files encrypted "
Thanks very much, this told me all I needed to know.
Btw, are you referring to this point mainly? In that case, CFA used to have the desktop as protected folders in the past but they removed it from default protected folders almost a year ago at least. I think Solarquest didn't notice that desktop isn't included in the protected folders anymore so he wrote "too late for desktop files". While in reality CFA actually did its job and protected files in the protected folders."too late for desktop files
We need a more recent test on version 2004...Btw, are you referring to this point mainly? In that case, CFA used to have the desktop as protected folders in the past they removed it from default protected folders almost a year ago at least. I think Solarquest didn't notice that desktop isn't included in the protected folders anymore so he wrote "too late for desktop files". While in reality CFA actually did its job and protected files in the protected folders.
Probably removed due to the volume of warnings people got.Btw, are you referring to this point mainly? In that case, CFA used to have the desktop as protected folders in the past but they removed it from default protected folders almost a year ago at least. I think Solarquest didn't notice that desktop isn't included in the protected folders anymore so he wrote "too late for desktop files". While in reality CFA actually did its job and protected files in the protected folders.
Yes, surely that's the reason. It was pretty annoying and I always wanted the ability to remove that.Probably removed due to the volume of warnings people got.
Thanks. I guess I didn't look closely.I don't think CFA was used here, only Configure Defender on high settings (mains CFA off).
desktop shortcuts..Probably removed due to the volume of warnings people got.
Btw, are you referring to this point mainly? In that case, CFA used to have the desktop as protected folders in the past but they removed it from default protected folders almost a year ago at least. I think Solarquest didn't notice that desktop isn't included in the protected folders anymore so he wrote "too late for desktop files". While in reality CFA actually did its job and protected files in the protected folders.
Did you add desktop to protected folder? It's no longer protected by defaultQuick info on my test results: memory doesn't help but luckily my comments in the summary as in the dynamic test report.
As you can see files were not encrypted in protected folders but some were on desktop...so WD detected this sample too late (some files on desktop were encrypted) but CFA worked and protected files in protected folders.
File encrypted: yes, but not in protected folders (*WD blocked encryption but too late for desktop files)
Final status: System infected-> files encrypted
Dynamic test:
fun.bat- files in protected folders were not encrypted, but on desktop.