I decided that I will update the nextcloud (windows) desktop client once or twice a decade - eviltoast

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.

  • computergeek125@lemmy.worldEnglish
    5·
    8 months ago

    Running nextcloud (non docker version) and I don’t see near so many client updates - usually once every few weeks, which would be a reasonable expected pace. Server updates are less frequent.

    On Windows (all of my primary devices), I just install the NC client update and skip the explorer restart, pending full reboot later. Tis the nature of literally anything that deeply integrates with Explorer. I’ve seen explorer “death” during updates from several vendors that have similar explorer plugins, not just NC. Explorer sometimes just decides to nope out even without NC updating.

    Now on one device I hadn’t opened for a while, I saw NC run two updates in a row, but that was my fault for procrastinating the first one.

    Here’s the desktop release history: https://github.com/nextcloud/desktop/releases
    I don’t see a “one every day” within the block of time between Dec 6 and today, unless you had the release candidate builds which may have been more frequent in a few spots.