Installation of 3,16b (64bit) ends with an error message

Tried to install 3.16b over existing 3.16a

  • MP3Tag is installed in "C:\Program Files\Mp3tag\Mp3tag.exe"
  • Started install with "doubleclick" on 64bit installation file
  • Error message "Staging Starse Package..." appears (see attachement)
  • Installation is aborted / 3.16b is not installed

Thanks for caring! :slight_smile:

mp3tagv316b

Can you post the output of

powershell -c "get-appxpackage -name *mp3tag*"

from a command prompt with admin rights?

Also, are you sure that there are no other installations of Mp3tag on your system?

Name : 35795FlorianHeidenreich.Mp3tag.ShellExtension
Publisher : CN=Florian Heidenreich, O=Florian Heidenreich, S=Sachsen, C=DE
Architecture : X64
ResourceId :
Version : 3.16.1.0
PackageFullName : 35795FlorianHeidenreich.Mp3tag.ShellExtension_3.16.1.0_x64__hyhc94k68ebpm
InstallLocation : C:\Program
Files\WindowsApps\35795FlorianHeidenreich.Mp3tag.ShellExtension_3.16.1.0_x64__hyhc94k68ebpm
IsFramework : False
PackageFamilyName : 35795FlorianHeidenreich.Mp3tag.ShellExtension_hyhc94k68ebpm
PublisherId : hyhc94k68ebpm
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : False
NonRemovable : False
IsPartiallyStaged : False
SignatureKind : Developer
Status : Ok

I'm not sure - for I wonder it installs in C:\Program Files instead of C:\Program Files (x86).
But when I see "installed apps" it only shows it in the C:\Program Files path

And no, it is no developer's build of windows 11 but the "regular" one

C:\Program Files is used for 64-bit apps, and C:\Program Files (x86) for 32-bit apps. It's not enforced by the system, but more of a convention.

What happens if you uninstall (keep your settings and create a backup) and re-install?

I'm quite sure, that deinstall and reinstall will fix it - but it's not about me. I see myself as "Beta Tester" (I guess, that's the aim of Beta Software) so I fear many others will get the error.
I installed the 32 bit in "C:\Program Files (x86)" and did only "Update" installations, so at any point it must has been moved to C:\Program Files (but not by me ;-))

Of course I will deinstall and re-install (latest with the next build) - but as said before I am quite sure it will fix this and this would mean, that we have to tell any other user, experiencing this error, to deinstal and reinstall...

OK, while starting the uninstall, I see, what happens:
3.16a still is installed in C:\Program Files (x86) - as there was any MP3Tag built before.
Now 3.16b tries BY DEFAULT not to install in the existing "x86"-Folder but in C:\Program Files - this causes the error.
So if 3.16b is set to install in C:\Program Files by default You maybe might built in a deinstall routine for C:\Program Files (x86) before...
(I will do it manually now)

Done and worked.

But - as expected - "C:\Program Files is set by default though the old installation is in "C:\Program Files (x86)\ ...

OK, glad there is now an explanation for the issue you're experiencing.

I've explained the different folders and the recommended upgrade path in this post, which also mentions prior deinstallation of the 32-bit version.

The 64-bit version also uses a different view on the Windows Registry which is used to remember the previous installation folder.

Yes, I (!) know. But while beta-testing I always have the "normal", not-so-experienced user in mind and he/she won't read our posts but just "cry for help":wink: