ReadyCloud not compatible with Windows 10 20H1 (2004)?

[beisser]

hi guys,

ever since upgrading to Windows 10 20H1 all upgraded pcs show my ReadyNAS as Online (VPN-Disconnected) while the 1909 Builds show them as Online.

i have tested this on 4 PC's  and even rolled one back to 1909 to verify.

i cant get any of the 20H1 Pc's to connect to any of my ReadyNAS.

I hope this is already beeing looked into.

regards,

beisser

[JohnCM_S · Accepted solution]

Hi all,

You can try this ReadyCLOUD test software on the latest Win 10 update and see if this will work. You can download the installer here.

Regards,

[Tzioufast]

I have the same problem
After upgrading all my machines say same thing
Online vpn disconnected
NETGEAR please help

[Sandshark]

This is why being the first on the block to upgrade is not usually a good idea.  Doing it on four machines is a really bad idea.  Microsoft has found and is fixing bugs in that release, and I suspect Netgear will wait to see if the problem is Microfoft's or Netgear's.

You do have the ability to remove the upgrade.  See here: how-to-uninstall-windows-10s-may-2020-update.

[beisser]

as you can see i already rolled back the update on one machine for testing, so telling me how to roll back/uninstall is kind of redundant 🙂

the way i see it something has changed in windows and netgear will have to adapt their software to make it work on the new version.

i do not expect this to be a fast process, but it will need to be done regardless.

of course it could be some bug in windows, but i suspect that simply some underlying mechanic changed and the software cant cope with it yet.

that is why i am reporting this nonworking state because sooner or later everyone will be autoupgraded to 2004 and then the software should be working properly.

[StephenB]

@JohnCM_S , @Mark_V :  Can you make sure this is escalated?

[Sandshark]

---

@beisser wrote:

as you can see i already rolled back the update on one machine for testing, so telling me how to roll back/uninstall is kind of redundant 🙂

---

Yes, but others read the posts (at least they should, we see lots of duplicates indicated some do not) to potentially find a solution to their problem.

If Microsoft has not released a lits of known bugs and one of them affects this, then I agree that Netgear should address it as a required fix until proven otherwise.

[JohnCM_S]

Hi all,

We have inquired about this issue to the appropriate team. We will provide an update as we get feedback from them.

Regards,

[JohnCM_S]

Hi beisser,

Can you provide the logs of the ReadyCLOUD app? You may get the logs at 'c:\Users\<system loggedin user>\AppData\Local\ReadyCLOUD'. You may provide it to us by uploading to a cloud drive then provide me the download link via private message.

Regards,

[beisser]

i sent you the link.

[Tzioufast]

Can you provide status

[scravatt]

same issue here....VPN disconnected.....rollingback windows.

please fix this ASAP. wasting so much time going forward and back.

[waldbauer_com]

Has anyone a fix for this VPN issue (besides uninstalling 2004) ?

[beisser]

not yet, but you can open a ticket with support (i have one open already).

the more tickets we have the more visibility this gets with support.

[waldbauer_com]

May there is any Readycloud Beta Desktop available ? I read about using only beta client for beta firmware; have currently 1.19 installed.

[JohnCM_S · Accepted solution]

Hi all,

You can try this ReadyCLOUD test software on the latest Win 10 update and see if this will work. You can download the installer here.

Regards,

[jtclark]

I got a few security warnings installing it, but it works.

[waldbauer_com]

This version works for me too. Thank you.

[PPP_Inc]

This worked for me.  However, the version information has not been updated on the test version, so once installed it is identical to the non-working official version 1.19.  Is there a timeline on making this fix official, and available to the general public?

[michaelkenward]

There has been an update to the ReadyCLOUD client.

v 1.20 should offer itself if you check for updates.

No more VPN errors.