SES driver does not work… tried that over and over again…
Anyway, I would like to take the chance to specify and correct my post:
MBL device works properly under Windows 8 Pro , and I am able to do everything just like I used to do in Windows 7.
The only issue is that, under the Device Manager (from the Control Panel) the state of the device appears to be “Unable to start the device (Code 10)”. The driver used is version 126.96.36.199 released on June 8, 2011 by WD.
This is coherent with the fact that the device is listed among the Devices available under “PC Settings” with the message “Driver Error” and consequently it does not appear among the Devices on the Charm Bar.
I believe that it would be a great loss not to integrate WD MBL in the Windows 8 environment, taking advantage of the possibilities given by Charm Bar “Devices” or “Sharing” buttons.
As I said, something similar is happening with WDTV Live, which in the “Devices” page under “PC Settings” appears to be “Not Certified for Windows”, and does not appear when I use the “Devices” button on the Charm Bar to take advantage of the “Play To” function (although, for instance, with “Truelink +” app it does appear among the “Play To” devices, but not on the Charm Bar under “Devices”, and similarly I can use the “Play To” function from Windows Media Player from the Desktop)… since I am also beta tester for WD, I still need to try the new WD TV Live (Gen3) Beta FW to see if there are some improvements.
On the whole, I believe that for both devices there is an issue with their drivers (class drivers perhaps) not up to date for the new OS.
As for the WD app on the Windows 8 Store , I just realized that it is not meant to be neither for WD My Book Live nor for WDTV Live, since both divices are not recognized by the app, and are not even listed as those working with the app… this, of course, makes me very sad, since I was expecting WD to update their apps in view of the arrival of Windows 8.
I really hope someone, using MyBookLive (or WDTV Live) with Windows 8 may confirm or share something more about this, so that we can help WD to address the issue…