I bought one to begin with for doing local backups and it kinda worked, first issue was that its drive letter would change randomly now and then, but at least most of the time it got the same letter assigned on every windows restart.
I got another drive like it to use as a shared storage, now problems really kicked in, because the two drives with obtain each their random drive letter when windows would boot, rendering the drives completely useless when they needed to be accessed by software running on a connected device.
I set up static IPs for them in my ISR as that was the solution WD support gave me, they said that drive letters were assigned corresponding to IP addressâŠwhich turned out to be a lie, they still obtain whatever random letter they please.
So I decided to manually set them up for connection in windows, by navigating to the drives ip in the explorer address bar, then right click the âpublicâ folder on the drive and select âmap network driveâ.
That worked, BUT the annoying WD app still connects them too and that means ive got them connected twiceâŠyeah uninstall WD app would sove that rightâŠguess what, I uninstalled it and now the drives wouldnt connect at all. /meh
On top of that, one of the drives consistently shows up as empty when I navigate to it by its ip address, despite there are indeed files on it.
The other one only shows me the private files and not the public ones, no matter what I do with it.
Bottom line, those drives are complete, utterly S*** in every possible way, with one exception, if you only have ONE small laptop and ONE homecloud drive, where you manually adminster files on the driveâŠand then it begs the question, why not just get a normal USB connected external drive instead?
Had i known those drives were such c***, Id have spent the few xtra bucks and got a NAS instead, because even though that would be twice the cost, it would be more than justified by the fact, that I wouldnt have had to waste an enormous amount of man hours on making the WD drives (somewhat) work.
All I want is, a drive that connects to the network, which I can assign on any computer with any drive letter I want, thats it, really THAT simple, yet WD had to make it overly complicated by adding a public and a private area to it so the user wont be able to access half of his contents.
WD proved very well, that they dont give f*** by lettiing these issues go on and on and on for years, no try to fix it at all at any point.
Support gave me a âsolutionâ that doesnt work and the other issue I had with not being able to acccess my own files on my own drive, they had no idea how to solveâŠexcept ofcourse âtry and initializeâŠâ fu WD, because that means im gonna spend a load of hours backing up the drive, initializing it and most likely just see that it didnt fix it and then youll tell me to take it to the shop where I bought it andâŠpfffffff
NO NO NO!! WD your s*** doesnt work, FIX it!