I do backups to a password protected share on several different machines and networks. Like about 75 million other people I’ve upgraded a couple machines to Windows 10, both Pro and Home. It broke smartware, along with W10Pro’s built-in backup when used across a network. Using the NAS shares with windows works just fine, either as network shares or mounted drives, Smartware fails to a protected share, but will let me see an unprotected one. I didn’t try a backup, but it’s a last option.
At least the Windows built-in backup will display an error code instead of a blank stare, 0x80070544. A little communing with Dr. Google dug up a fix, and it’s backing up just fine. Pretty obtuse, if somewhat simple to resolve. When supplying the credentials (username/password in non-windows speak) prefix them with the name of the destination device. In the past this defaulted to the name of the current system (and this worked with W7 and W8.1), so if you were going from MyPC to MyBookLive it defaulted to MyPC\username, according to the name displayed under the username/password in the dialog box. Now Windows wants you to use MyBookLive\username.
I dug through the Windows event logs, but couldn’t find an entry for the Smartware failure to see what the error (if there’s indeed a Windows error and this isn’t just Smartware being completely broken)
ToSmartForItsOwnGoodWare forces this name to MyPC\whatyouenter. You can’t enter the destination name it appears (only appears until a successful test proves it) to want, so MyBookLive\username isn’t an option.
WD needs to allow the destination system name to be specified along with the username. This error is pretty common with Samba (which is what WD is using) connections from Windows.
Come on WD, regardless of your opinion of Windows 10 it’s going to be really big, and the 75 million current users M$ is throwing around isn’t too shabby either. Then there was that extended Insider program that could have been used for some testing. Perhaps it’s about time to make Smarware work with protected shares on Windows 10?
Unfortunately Windows 10 is not one of the supported OS’s for WD Smarware. However when you input drivename\username in he smartware prompt for credentials, what does it happen?
You can’t. Smartware forces it to currentpc\name and I can’t find a way to change currentpc to the name of the destination NAS.
It’s pretty obvious that Windows 10 isn’t supported with this gross an issue, if this is indeed the killer bug. It does tend to limit the product’s lifetime if there’s no support for the current operating system with an extremely agressive upgrade program. Guess nearly a year wasn’t enough.
I guess that was some progress, I used upper case this time and it changed the hostname. It may have last time (I had tried prepending the name) and I never noticed. Also tried the same capitalization as the device name without any change (supposedly case insensitive so no surprise there). It backed up for many months with W7Pro, no issues, and I restored a few files in the past to test. I have a MyCloud elsewhere with Windows 8.1 and no issues.
But it still didn’t accept it; I’m not able to get into the backup or restore tabs… Yes, I used the correct ID and password, caps lock was off, no errors were displayed, etc. And no new files in that share, last backup date/time was just before installing the Windows 10 upgrade. It’s (possibly) trickier than just credentials, wonder if it includes the network name before the host (mooselake\mooselakelive\kirk) or j does something else. I don’t have a way to monitor that, or do anything about it if I did so it’s not worth finding something and monitoring the switch port. No alerts or logs on the MyBookLive about login errors so no help there.
So far, as I understand it, their response has been Windows 10 is not supported. I hope somebody deep in the WD software labs is working hard on this. After all, the tech previews were only out the better part of a year for them to get a head start.
Otherwise that;s really going to lmit SmartWare’s market, with the agressive upgrade campain and especially if the billion PC thing works out. I can’t be the only person who want’s their backup files to want the (moderate) protection from password protected shares - think finanancial info for example.
And an update. After my last post I rebooted to install the latest Windows 10 updates (KB3081449 and KB3081448, plus KB3081451 had been installed yesterday). I received the usual error on the reboot (Backup Destination can’t be found),
I followed the support link, went to open a case, and opened SmartWare to confirm the version number. This time it sat there for the better part of a minute, then displayed the file breakdown under the backup device, didn’t even need to go through the click device icon top open, and let me into the backup menu. The destination drive now has backup files for this computer.
Something in one of those 3 updates seems to have fixed it. Maybe a perusal of the patch notes in the KB will show something, but they don’t seem to be showing a lot of info these days (“Fixed an issue in Windows” isn’t very descriptive).
I know there’s others with similar problems, can somebody else having problems backing up W10 machines to protected shares install these updates (probably just the normal Windows Update mechanism) try this and post their results here? Thanks!
WD still needs to do something about that devicename\ID issue since it’s beyond something a normal user would know (almost retired after over, gulp, 45 years worth of computer support experience, from OS/360 to PCs) , and saying Windows 10 isn’t supported (after how many months of Insider previews?) is still a major issue.
Call this login problem tenatively solved by a Microsoft update. With a little confirmation might be time to queue a small happy dance!
