Yup, it is technically a mistake on their end and it’s an easy fix. Unfortunately since the device has been EOL’d, there’s nothing they’re going to do.
Why ? because it affects the New 2014 WDTV Media Player … which is not EOL’d
Seriously on this one. WD isn’t even going to bother addressing this even though they’re one “/” away from fixing it?
They broke it, but they won’t acknowledge that they caused it, and won’t do anything about it fully well knowing they’ve had loyal customers sticking by them on their WDTV live box through the years which started out as a buggy, slow and a train wreck of an U.I device to its current state which is pretty stable and passable on a performance level, but now they’ve abandoned it expecting us to upgrade to the latest model which currently has the same problem and is a less useful product if you’re a Netflix customer.
Seems to me that the customer service and marketing team at WD are phoning it in when it comes to concerns towards keeping customer loyalty.
Same issue for me past weeks, Info is there but no thumbs.
I have fought with this **bleep** for a long time and the lack of support is a joke.
At one time you got slated by a few WD plants here for anything negative said but no its at stage even a few of them agree.
I have had my eye on the Amazon box a while but it lacks some featutre some of which have been added by updates but still no Network Shares or and some other file type/codec misisng due to Android not supporting it yet (cannot remember for now).