Timeline for Windows Defender made all my documents "corrupt and unreadable" (0x80070570)
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 3, 2018 at 1:47 | answer | added | Robert Sprowl | timeline score: 0 | |
| Jan 23, 2018 at 17:49 | comment | added | Marc Gabrek | @FosseWay Hi, thanks for responding. I think the program is clean, a guy who knows way more about this stuff than I do recommended it to me and I trust him. That said, you bring up a valid point, but I don't think the program itself is what's causing the problem. | |
| Jan 23, 2018 at 17:45 | comment | added | FosseWay | This may or may not apply in this specific case, but just because you found something on GitHub doesn't mean it's automatically trustworthy. GitHub is a legitimate site where all sorts of code is hosted, mostly good/useful/harmless, but some not. A quick Google shows that this project has prompted [hopefully] false Windows Defender malware warnings before. In the Windows Defender GUI, what does the History tab show you? Lastly, it's usually a good idea to give software its own folder to run in. Most likely, Windows Defender decided to lock down the entire directory: My Documents! | |
| Jan 23, 2018 at 17:35 | review | First posts | |||
| Jan 23, 2018 at 19:14 | |||||
| Jan 23, 2018 at 17:33 | history | asked | Marc Gabrek | CC BY-SA 3.0 |