XYplorer Beta Club

super stuff. For a moment I was worried to see no change. Then I saw there are new flags to sc update.

High time for adding a default toolbar btn for updating.

Just tried "update 1 + 16 + 128" to update XY from .0116 to .0120 but it didn't work for me.
Made 3 attempts, two as regular user and one as admin, which all failed somehow as the version after restart was still .0116.
Then I tried to update the old, manual way, only to find that this version is one of the few that doesn't stop XYplorer.exe properly before starting the update which results in the following message:
I think it would be nice to fix this old bug (happens every few versions for whatever reason) but even more importantly I would definitely expect a message at the end of the automatic update if something went wrong along the way, even if I chose silent mode.

I'd love to fix this, but I need to understand what's causing it. I never get this here, and ATM I don't see what I could do about it.

When you see this error message, is XYplorer still visible?

guess that would be most proper place to ask: will new Ctrl+Click on Update, update portable version too?

I think so.

BTW, this will run the update even if the current version is up-to-date: It works for portable installations.

admin wrote:When you see this error message, is XYplorer still visible?

No!
I start the installer with right-click, run as admin from XY and then close XY via x-button when the first message from the installer is shown.
It happens with around 1 out of 10 updates, sometimes more often sometimes less but whenever it happens it is consistent with that installer exe, i.e. it happens with every run of that installer (at least that's how it was in the early days when I still ran the installer several times before I gave up and killed the process manually before continuing with the installation.

I just went back to check whether the .0120 installer would kill XYplorer.exe eventually on subsequent runs but even 3 mins. after I closed XY via the x-button the process was still there, see screenshot below:

Weird. Can't explain.

.0200 just contradicted part of my statement, it didn't kill the XYplorer.exe process on the first run but did so on subsequent tests.
Am I really the only one still seeing this, I recall that when we last discussed this I had replies of others reporting the same behavior?

It's a shame because I would have loved to use the new update system.

Maybe some setting. If you send me you INI file I can check.

Thanks. But nothing suspicious found. It remains a mystery.