NOT SUPPORTED June 2023 Local drive mounting via WD Discovery for My Cloud Home desktop ends **with Tailscale Fix DIY

This has been mentioned but not posted on its own. It does look like WDC has decided that desktop (Win File Explorer and mac Finder) integration is not something they can keep developing and support given the many changes to the operating system (mainly macOS AFP and SMB security updates). It may be possible that WD Discovery desktop could keep running on 64 bit Windows for many more years with nearly full functionality, but don’t count on it. *

  • CORRECTION, on second read, it does look like desktop network support will stop in June 2023 which means even if WD Discovery is still running, there will be no mounted REMOTE drive and the remote will not show on the desktop, however locally mounted MCH is unaffected.

https://support-en.wd.com/app/answers/detailweb/a_id/34904

  • What does “no longer supported” mean?
    WD Discovery will no longer support My Cloud Home devices. There will also no longer be any new releases or security updates for My Cloud Home on WD Discovery. We will discontinue all development, including critical security updates and technical support. As new versions of operating systems are released, these features might stop working and will not be fixed. WD Discovery will continue to function and be supported for other compatible WD storage products.

  • **When is support ending?**Support will end in June 2023
    How does this affect me?

Local drive mounting via WD Discovery for My Cloud Home desktop app will no longer be supported. If you used the desktop app to access your files stored on your My Cloud Home device, you will now need to access them in one of the following ways:

  • My Cloud Home Mobile App

The My Cloud Home Android and iOS Mobile Apps can be downloaded from the following:
Mobile App on Google Play
Mobile App on App Store

Question, can I remove the hard drive from the mycloud home device and install it into a NAS and still access files remotely?

Before one pulls out the crappy SMR HDD in the MCH and pull out one’s own hair trying to get it to run properly with another NAS, realize that it is easier and cheaper in the long run to just back up the MCH to USB now and recover the data that way for backup and future use in another NAS. The 2TB to 6 TB WD SMR HDDs in most MCHs are unsuitable to be used as NAS HDDs.

Also realize that WD Discovery may continue to work for a while longer and June 2023 is not a drop dead date, it is just a warning the end is near for MCH desktop support.

Finally, to answer the question, if one is smart about NAS remote networking, there is another way. The way to access the MCH remotely without any modification to the MCH itself, no hacking of the MCH is required and it is free and it works.** The only condition is it required another network device that must run the Tailscale subnet as the router (could be a physical router that runs Tailscale or even the client Windows or mac running another Tailscale instance in a virtual machine that functions as the subnet router).

**In an ideal scenario, MCH should be made to run Tailscale under its own Debian OS or using Docker for example, but that is probably not going to happen any time soon with WDC.

Subnet routers and traffic relay nodes

Tailscale works best when the client app is installed directly on every client, server, and VM in your organization. That way, traffic is end-to-end encrypted, and no configuration is needed to move machines between physical locations.

However, in some situations, you can’t or don’t want to install Tailscale on each device:

  • With embedded devices, like printers, which don’t run external software
  • When connecting large quantities of devices, like an entire AWS VPC
  • When incrementally deploying Tailscale (eg. on legacy networks)

In these cases, you can set up a “subnet router” (previously called a relay node or relaynode) to access these devices from Tailscale. Subnet routers act as a gateway, relaying traffic from your Tailscale network onto your physical subnet. Subnet routers respect features like access control policies, which make it easy to migrate a large network to Tailscale without installing the app on every device.

whelp, I took your advice, I just broke down and spent a grand on a synology and a 20TB drive, now I have to figure out what table legs to put the 3 MCH under.

you cannot as access to the account require authentication from WD server using the built in software but they have enabled SMB so you can connect it via windows network drive. The only inconvenient thing is it need a separate local login(different to the one you use online and for app) for each user, this can be setup by going the local IP of the MCH device. Also if you need to login to a different account on the same computer you need to disconnect the current map drive first via command prompt using the “net use * /delete” as there isnt an option on the dropdown.

1 Like

They advertised this device wrong… its not a NAS drive… it should be call a NCS - Network cloud Storage

1 Like

No. WDC knew exactly what they were doing. This is a light duty HOME storage device, not a traditional NAS with all its features. Those who wished to run businesses and heavy duty media serving from the MCH were disappointed in the end because the MCH usually did not last much longer than the 2 year warranty under heavy use, at least using the old firmware. The new firmware removed the old Android OS and its hybrid file system and now allows the HDD to spin down when not in use.

My Cloud™ Home is an easy-to-use personal cloud storage device

A few questions on this imminent change using a Mac and Local Network Access:

  1. Will desktop sync still work? Currently, with WD Discovery, certain folders can be synced with the Mac (a green checkmark is added next to the synced folders/filenames).

  2. With WD Discovery, even when outside the local network, changes to the desktop synced folders would be reflected on the MCH. Will this still happen without the WD Discovery?

  3. When enabling Local Network Access, does the local user name need to be something specific/linked to the overall setup of the MCH, or can this name be anything not previously used?

Thank you for clarifying (I could not find answers to the above in the help files provided on the WD help files).

1 Like

These are not imminent changes as I read it (WD link first post). WDC is just posting that they no longer wish to expend resources in updating WD Discovery to work with new versions of desktops, whether newer macOS or Windows after June 2023. So presumably if macOS stayed at Ventura and Windows at the current build of Windows 11, there will be no loss of functionality and WD Discovery desktop sync and remote sync should still work. If future OS file system changed, it will likely break WD Discovery as we have seen this frequently with macOS updates.

**** CORRECTION, on second read, it does look like desktop network support will stop in June 2023 which means even if WD Discovery is running, there will be no mounted REMOTE drive and it will not show on the desktop, however locally mounted MCH is unaffected.

As a desktop user of this WDD feature, your best bet in replacement may be to install Tailscale which is free for personal single user (log in) use, 20 device limit.


WDDiscovery desktop notification warning end of support and utility in June 2023

As to #3, once local access is enabled, the local user name and password can be anything that is acceptable to the OS SMB authentication and can be changed as often as necessary through the wed app or alternatively directly via ip address as shown here:

Desktop sync is an essential element of MCH for me. MacOS will most most certainly be update like clockwork in Oct 2023. Considering that every macOS update has “broken” the existing WD Discovery, this will most likely happen again with the next macOS version. As such, WD Discovery’s like will end by October for users who update their computers in a timely fashion.

And this the question: what replaces desktop sync functionality which is a major part of MCH? I was told by a WD rep tonight that WD is “working” on something, but couldn’t confirm whether desktop sync works with Local Access Network …

Any ideas?

1 Like

Please read the original and the third post, this remote networking technology has existed for a few years now and it is free for personal use and it is called Tailscale. The post link below shows Tailscale in action in a mobile app, but it works as well or better with any desktop (Linux, macOS, Windows).

The WDC MCH development team could make this easier by supporting Tailscale natively as a Debian client but the mesh VPN network functionality already works right now with a Tailscale subnet router. Many Synology and other NAS already support Tailscale.

Copying entire folder remotely from Android phone to My Cloud Home private space (Public space and two way copying and sync also possible) with Tailscale and third party Android file manager, without the use of My Cloud Home mobile app. Tailscale supports Linux, macOS, Windows, iOS and Android.

There is now a suggestion thread on running Tailscale natively in the My Cloud Home over in the ‘ideas’ subforum. Please go over to that thread and voice your support if you think this is a useful feature.

However, you don’t have to wait for Western Digital, you can run a subnet router right now with only a few steps and you will be able to access your My Cloud Home remotely with third party software without the use of MCH specific software or WD relay servers **

Thanks to Posted by rednessw4rrior for the following:

Here is the how-to-configure TailScale Subnet Router for Windows Machine

The Windows installer places a tailscale.exe command in %PATH%. You set Windows up as a subnet router using a cmd.exe shell with the same command as Linux:

tailscale up --advertise-routes=…

So, if the home router IP Range is 192.168.1.1,

you’d likely want to use the following on CMD:

tailscale up --advertise-routes=192.168.1.0/24

OPTIONALif you have another set of subnet, remember to add rightaway after the first one, otherwise you will have to reset everything and do it again but with all the subnet you want to add.

example of multiple subnets cmd : tailscale up --advertise-routes=192.168.1.0/24,10.8.0.0/24

then, go to Tailscale

click Edit Route Setting on that Windows Machine.Turn on the Subnet Route , all done!

that’s it! :slightly_smiling_face:

** Tailscale Subnet routing performs best with a Linux machine (physical or virtual router running Linux such as OpenWRT for example), but performance is acceptable with recent Tailscale development since version 1.26 and higher on Windows.

Wow that so much worst since yesterday 9.4 update !
Now the SMB file has completely disappeared from my local network.
I reboot MCH twice but local configuration page still saying “internal access error”

By the way, the update started automatically when backing up a 1TB directory and MCH rebooted, ended the transfert.
And I don’t know why, but after switching files on the device, I lost a lot a free space, while it should stay the same.

Bad day …