Workaround:
I would highly recommend not using “WD_Discovery” utility’s automated drive mapping to and assigning winOS drive letters to your WDMyCloud HDDs (and user created ‘Shares’). I make this suggestion because this auto-mapping employs the “/persistent:yes” switch in the console shell ‘net use’ command. This causes the drives/shares to be remembered (sticky aka persistent) during subsequent OS boots. Unfortunately, since the “UserName” and “PassWord” do not appear to be added to the console ‘net use’ command (during the initial auto mapping), the subsequent boots cause the dreaded Red-X for each of the mapped drives/shares, in the FileManager.
using the instructions of WD ID 6745: “Error: ‘Unable to reconnect mapped network drives’ occurs when Windows attempts to reconnect a Mapped Network Drive after a reboot” I created a batch (*.bat) file and put it in the WinOS StartUp folder to undo the ‘net use’ command "persistent:yes’ switch first.
You have to follow the directions in ID 6745 to create the batch file named “mapped_drives.bat”
You have to determine the DriveLetter(s) assigned to your WdMyCloudEX2 drives that are showing the dreaded Red-X
You have to determine the IP of the WDMyCloudEX2 first (mine is \192.168.1.64 as shown below in the batch file created.
You have to also find out the exact name of the drive/share that has the dreaded Red-X (disconnected but mapped)
You have to correctly mind the quotation marks and spaces as shown below in the batch file created.
You have to correctly input the “UserName” and “PassWord” that you use to log on to your WDMyCloudEX2 device
My example:
===============================================
@echo off
net use Y: “\192.168.1.64\SmartWare” /user:UserName PassWord /persistent:no
net use Z: “\192.168.1.64\Public” /user:UserName PassWord /persistent:no
===============================================
After the next boot, the batch file [hopefully] will remove the dreaded Red-X from the mapped drives.
This will allow you to delete them, using the console command by entering:
net use Y: /delete
net use Z: /delete
Now you can safely remove the “mapped_drives.bat” from your StartUp folder
And reboot again to confirm that there are no more dreaded Red-X mapped drives/shares in your FileManager.
Finally, you can use the “WD_Discovery” utility to manually assign DriveLetters to the desired drives/shares as you wish them to be mapped.
If you want these drives/shares to be automatically assigned at/during each boot you can change the “net use” command switch to “persistent:yes”. But you must remember to make sure that these local LAN IP addresses are fixed (static) as show in my case/example (i.e. \192.168.1.64)
