WD Backup has suddenly refused to launch by any means (via system tray or desktop shortcut or from the Windows 10 “All Apps” list). I deleted WD Backup, shut down PC, restarted PC, and reinstalled WD Backup but still nothing happens. The My Passport Ultra drive itself is working – can open files not created by WD Backup, WD Disk Utilities checks are all good, etc – but I can’t run WD Backup to either Restore backed up files or create new backups.
Things were working fine for a number of months until yesterday. PC is a Toshiba Satellite laptop upgraded to Windows 10 Home, 64-bit, in March 2016.
Does anyone have any idea what may be wrong and how to resolve this problem?
What has changed in your computer? A recent Windows 10 system update? When you reinstalled WD Backup, was it the version bundled with your WD Passport Ultra, or did you install the latest version directly from WD’s Site?
I am not aware of any changes that took place in the PC; the last scheduled daily backup that WD Backup successfully made was at 12:02 am on July 19, and the most recent Windows 10 update prior to that was July 17 so the issue does not seem to have been triggered by a Windows update. When I reinstalled WD Backup, it was from a fresh download from the the WDC support site. I am not seeing problems with other programs. I wonder if there is some registry setting for WD Backup that might need tweaking; it had been working fine for months and does not throw any errors, just will not open. BTW, there is plenty of free space left on the Passport Ultra device.
I did also open a support case on this issue with WDC support, and today they suggested using WD Smartware instead. I tried that this evening, and so far it is working and allowed me to do an initial backup. I have scheduled recurring daily backups and will see if they seem to work also. Once I verify that, I can close out this posting since it is my understanding that the WD Smartware system will in effect provide the same functionality for the backups and restores as WD Backup.
Thank you very much for responding to my original posting.
I am glad this has been resolved. I am still curious about the root of the issue, and it could indeed be related to the registry.
