Windows 10: Microsoft is taking my files hostage

Wrote a document on my computer, I cant edit it anymore, therefore dont have access to my own. Absolutely reprehensible. How can I get access to my own work? What a joke.

:)

 

Your files held hostage

IOL reports, that hackers have found a way to hold files on your computer hostage.
After a break-in, 15 different file types on your computer will be encrypted and an email will be left, telling you, that you can get your data back for $200.

 

Recent File List

Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file1

Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file2
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file3
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file4
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file5
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file6
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file7
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file8
Remove-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion
\Applets\Paint\Recent File List" -name file9
...

you get the idea. ( too lazy to put it in a for loop and test it.

or just open regedit and remove all the fileX from that key.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.