I’ve enough.

Last year the automatic updater was rebooting windows without any warning after the uac prompt. The problem continued for months before being fixed

This year I got an update a week. Very annoying to get the same “why u no reboot? I need updates” question every single time I turn on my PC.

Today when updating it kills explorer.exe without any confirmation and doesn’t bring it back to life.

I don’t think that their paid enterprise customers are doing the beta alpha testers like this. Is it really necessary to push nightlies to end users? It can’t be tested casually for a couple of days then pushed?

I disabled the updates check and will update the nextcloud desktop client manually every 5 years if I can remember. Added an exception to Winget so it doesn’t update it. I lost my patience.

  • Moonrise2473@feddit.itOPEnglish
    7·
    8 months ago

    You’re right but if an installer renders a computer inoperable until reboot (tried in another PC, same result, doesn’t only kill explorer.exe because if I run it again via taskmgr, the taskbar is broken and non functional until reboot) it means it has been pushed to the “stable” channel without being tested a single time.

    The problem is present since 2021 and it’s a bit ridiculous now https://github.com/nextcloud/desktop/issues/3551

    In the topic you can see the devs “ok fixed in next release” => next release didn’t fix it (=nobody actually clicked the exe before releasing, it just passed all automated tests), then “ok so next release gonna fix it”, and again again

    It has been said to gracefully restart explorer.exe instead of crashing it, it still chooses violence for a restart. It asks “do you want to reboot” twice.

    I like having the bleeding edge stuff, running nextcloud in docker under the “latest” tag, but those are clearly nightlies

    • mranderson17@infosec.pubEnglish
      2·
      8 months ago

      I think this one https://github.com/nextcloud/desktop/issues/5369 is probably the more relevant, and also open, issue. However even in that issue people claim you can choose not to. The argument is only that it suggests restarting explorer and also rebooting and that this is annoying. So you never get a prompt, it just dies?

      I agree though that the amount of time where it was force rebooting is pretty bad, and it looks like the rollout of the patch was mishandled. I also should probably admit that I’ve never touched the windows client, my environment is entirely Linux and Android. The Linux client even with file manager integration doesn’t require restarts of anything.