How completely underwhelming that EaseUs cannot be bothered to publish its documentation for a do-it-yourself product. And it took months of back-and-forth e-mail fiddling with (your) support for me to trust that the software would actually do its job.
In your case, please click on Browse to Recover option and choose one full backup file at the target drive, then tick the disk to recover to.”įrom me: “Old version”? This was purchased around a year ago. Sorry, there is no instruction link for the old version at the moment. Here’s the e-mail exchange with them, below ~įrom me: “Please reply with a link to the instructions to recover the system drive and all its contents using the latest disc image. In this troubleshooting process I asked EaseUS if they have a URL to a simple, step-by-step disc image recovery process. Then came yesterday’s unexpected machine freezes, in which software launches and use would take 2 to 7 minutes, if they would work at all. When I pointed this out they gave me the right download link and I installed 13.5. EaseUS first gave me the wrong 13.x download link with the wrong version of the software. That was the opposite of inspiring my confidence in them.Īround two weeks ago, I asked EaseUS for a download link to their long-promoted 13.5 version: I’d been running 13.0, and they have just released 14.x, so I figured I’d want to have a copy of the most recent 13.x version. It took around three months of back-and-forth e-mails with EaseUS to get their software to perform without incident, and to shut itself down. I had purchased a ‘lifetime license’ of EaseUS ToDo Backup 13.x only a year ago (December 2020), as a back-up to my several, redundant back-up strategies.
Yesterday, while I was deciding whether it was Microsoft’s supposedly innocuous monthly update or Bitdefender that was making one of my machines glacially slow, I considered the idea that I might restore the entire system disc from EaseUS ToDo Backup 13.5 (it eventually turned out that removing and reinstalling Bitdefender solved the problems.
0 kommentar(er)
