MuseScore
MuseScore copied to clipboard
musescore
[MU4 Issue] [Windows Installer] MuseScore udpate via MuseHub doesn't uninstall the previous build properly on Windows
To Reproduce
- Install MuseScore build from https://github.com/musescore/MuseScore/actions/runs/3675193217
- Install Release build via MuseHub
But if to close the window by clicking OK the installation of the latest build is fine.
Only leads to this:
You should uninstall MU previous build from that menu to live only one MU4 item
Occurs if to update MuseScore via MuseHub (doesn't occur if to update manually)
Platform information Windows10
I've experienced this too. What info do you need?
@DaffodilAura If you also reproduced that so no more info is needed I guess. Thanks!
Today I got the 4.0.1 update on Windows and now I have 4.0.0 and 4.0.1 listed in windows apps listing:
First install was direct from the Muse Hub, update installed from the notification received when I started MuseScore. Seems as if the Muse Hub installed version is not "recognized" as being the same software. Now got two icons for MS4 on my desktop. Both launch 4.0.1. Also when I launch MS from the Muse Hub, the 4.0.1 version is launched.
If this is a different issue, please let me know and I will create a new github issue.
Update on my previous comment, Muse Hub has now detected there is a newer version of Muse Score available. This resulted in another download and install. One icon removed from the desktop after this, so only 1 left and only 1 MuseScore 4 listed in the apps section.
So seems to recover by itself once the Muse Hub update kicks in. Just annoying it performs another download and install.
@DmitryArefiev @zacjansheski this issue is relatively old now. Can it please be re-tested for relevancy?
The issue also exist when updating using the application instead of via the musehub. The recent 4.3.1 update did not download using the musehub, so when the application detected there was an update available, I completed the upgrade. Once done, I had two versions of MuseScore in the application list in Windows. Musehub also kept reporting a newer version was available. I manually removed the 4.3 0 version using the apps functionality in Windows. Happy to report this as a separate issue if that would be better. Please let me know what you think.
I think what might be happening here is the MuseScore inbuilt updater is updating as a user install, but Hub is updating / installing as a machine wide install. But not 100% sure.
@DmitryArefiev @zacjansheski this issue is relatively old now. Can it please be re-tested for relevancy?
@bkunda The issue still here. But the problem occurs if update installation is made from a different source: e.g. 4.3.1 msi file -> 4.3.2 via MuseHub (and I think vice versa too)
Narrowed down to Machine Installs vs User Installs. Hub gets confused between the two. Working on the best way forward here.
EDIT:
I've got a few patches built for Muse Hub.
- For version checking we'll use the latest installed version of MuseScore Studio if there are multiple (this prevents some weird issues in V2 where launching MuseScore Studio would instead attempt to update it).
- The uninstall loop some people were in won't apply to V2, as the uninstall process has changed.
- When updating MuseScore Studio, Muse Hub will now take into account if the previous install was a per-user install or machine wide install, and update as expected (this should fix V1 migration issues and any conflicts between the MuseScore Studio updater).
If you have ended up with two MuseScores, Hub will eventually handle this and maybe automatically uninstall the machine wide version? I haven't implemented this yet (as it's not super blocking). But these patches should prevent getting into this state in the first place.