Firmware 04.05.00-334 (3/12/19) Discussion

As indicated in the tacked thread: New Release - My Cloud Firmware Version 04.05.00-334 (3/12/19)

There is updated firmware for the first gen v4.x My Clouds. Feel free to discuss the good and or the bad.

Firmware Release 04.05.00-334 (03/12/2019) | Release Notes

Direct link to download:

What’s new!

Security Fixes
    Resolved security vulnerability (CVE-2018-1160) - Netatalk Arbitrary Code Execution Vulnerability.
    Resolved Samba security vulnerability (CVE-2017-7494).
    Resolved multiple command injection vulnerabilities including CVE-2016-10108 and CVE 201610107.
    Resolved multiple cross site request forgery (CSRF) vulnerabilities.
    Improved the security of volume mount options.
Components Updated
    Apache - v2.4.10
    OpenSSL - v1.0.1t
    libupnp - v1.6.25 (CVE-2012-5958)
Other Bug Fixes
    Improved remote host port handling.
    Resolved USB drive unlocking mechanism.
1 Like

After updating a first gen to the new -334 firmware. Upon initial login to the Dashboard got the following message:

" Our Privacy Statement has been updated. By continuing to use this product, you consent to the updated Privacy Statement.

I have 04.05.00-327. When trying to manually update I get “Not enough space on device”. I have used 50% of 4TB, so 2TB free…
Using the “Check for update” I get “Your firmware is up to date”

Update: After downloading another copy directly from the MyCloud support web page it works…

My MyCloud does not see this update - yet?

Downloading manually

EDITED TO ADD: 250kB/s? Really?

And breaking every 1-2 MB - like in the '90s! Oh dear…

EDITED TO ADD: 12 hours later file downloaded smoothly, and installed manually. Initialising as we speak…

Are the sleeping times better?
Is it stable?

At this point I’m afraid to … check. :wink:
Seems stable but dashboard loads slooow.

So far no problems on my end with the 04.05.00-334 firmware. Dashboard is what it is and sometimes is slow to load as it’s always been.

The bottom line with the whole sleep option issue is that it doesn’t work very well. Never has. Only way to get the first gen My Cloud to sleep for long periods of time is to turn off features through the My Cloud Dashboard and stop/disable a number of firmware services through SSH. Then put the My Cloud on it’s own network where it cannot be contacted by any other devices (especially Windows PC’s). In other words render the device fairly unusable for it’s intended purpose.

I’ve given up on having my device sleep for long periods of time even after running all the usual steps discussed many times previously. Between adding a Plex Media Server (in a Raspberry Pi) to the local network and using the My Cloud as the PMS’s media library to Windows 10 samba issue to other chatty devices (my smartphone) on my local network, my My Cloud sleeps about 30% of the time now. Sometimes it sleeps for a few hours, other times its waking up every 5 or 10 minutes.

One way to fix many of the issues with the My Cloud firmware, including years out of date service modules (like Samba) is to roll your own firmware using the GPL firmware files released by WD. That takes time, skills and knowledge most here do not have.

One problem with rolling your own is that the jnl.ko and ufsd.ko will not work with most kernels you would build.
If you look at the dmesg output on the gne1 or gen2 you will see the following:
[ 15.150346] jnl: driver (lke_9.2.0 lke_9.2.0_r256412_b8, LBD=ON) loaded at bf000000
[ 15.284726] ufsd: module license ‘Commercial product’ taints kernel.
[ 15.289843] Disabling lock debugging due to kernel taint
[ 15.301347] ufsd:: trace mask set to 0000000f
[ 15.304438] ufsd: driver (lke_9.2.0 lke_9.2.0_r256412_b8, build_host(“swtest6”), acl, ioctl, bdi, sd2(0), fua, bz, tr, rsrc) loaded at bf020000
NTFS support included
Hfs+/HfsJ support included
optimized: speed

Yes. rolling your own presents potential additional issues from packages that may not work. It’s one of the trade offs unfortunately.

For anyone who want’s to give rolling their own a try the following post/thread has discussion on how to (try) and do so.

Or one could try one of Fox_Exe’s alternate firmwares.
Clean debian:
Open Media Vault:
Or Synology DSM:
But those to present their own issues with the first gen My Cloud. And require additional knowledge (and Linux experience) to install to the My Cloud first gen hard drive.

Download link not working, any thoughts?

The problem is on WD’s side as one cannot download the firmware from their own website ( Try waiting a while then try the link.

That is the GPL source code link for one to build their own firmware for the My Cloud. If one wants the actual firmware link for the DEB file that they would use to manually update their first gen My Cloud, use the link below:

Hello, it is possible that after this update already can not use WD My Cloud to PCs with Windows 10? I need to remotely connect to the cloud. The application now reports “Login not authorized”. I haven’t made any changes to the settings. The program before the update worked. Reinstalling the program on the PC did not help. Thank you for answer.

i have the same problem

@FRANCOSD-60 the following article explains the error message when using the WD My Cloud Desktop App on newer firmware.

My Cloud Desktop App No Longer Works with a My Cloud or Login Not Authorized

Answer ID 25159