New
#1
Is This a FULLY Reliable Method to Recover from Ransomware?
Hello Everyone,
I have lately read several websites that talk about the possible destruction of my computer resulting from a ransomware infection . . . which made me wonder if the method I have long expected to use would Actually be reliable!
So I would really appreciate for any Security Gurus among you to please let me know whether my expectation is based on real-world facts::
So, let's say that the Next Time I boot up my computer (Win10 x64) . . . a message immediately pops onto the screen informing me that ALL key files have been Encrypted, --That I must now pay $850 worth of bitcoins to the posted URL, --And that any attempt to use any recovery tool will result in the immediate wiping of the drives.
"Oh, Shoot!", I think, "The exact thing I was so worried about has happened!, And I haven't even had my coffee yet!"
And then I remember that it has been nearly TWO Weeks since my last image-backup. "Oh well," I console myself, "Better late than never!"
{{ I should mention here that I do save my image backups to a USB hard drive which I only plug in when I'm actually Doing a backup . . . And that my Macrium backup software had assisted me to make my USB drive bootable [<--but that was STILL an error-fraught struggle!]. }}
So ... I shutdown my computer, plug the external drive into the USB port--which boots up to the WinPE version of Macrium;
THEN, I Click the desired Image-File, Click on Restore, the Software warns me that the drives will now be erased . . . and Boom! The Flowers are blooming, the birds are sweetly singing in a nearby tree, and all is right with the world!
Does the described result have a very high (>86%) probability of actually happening? And if Not, please let me know of anything that would improve the reliability of my response! --I have some extremely valuable stuff on this PC, and would Strongly Desire for my recovery plan to have a VERY high chance of actually working!
Thanks a lot for your replies!
- Chuck
Last edited by Chuck7; 10 Dec 2017 at 05:18. Reason: misspelling