I noticed that I had v3.18 and v3.24 installed on my Windows 10 Pro machine (64-bit). I'm not real sure how that happened, so I attempted uninstalling v3.18, which resulted in both versions being uninstalled. I now have the same problem once again that I had back in September, which is being unable to get mp3tag installed. There are no remnants left from the double uninstallation, and there are no registry entries for mp3tag anywhere in the registry that I've been able to find. I'm not well-versed in trying to find out what the installer is doing, except for not letting me install. I've tried my hardest to figure it out, but my tech skills only go so far. Some help would really be appreciated.
Do you get any error messages? And if so, which?
No error messages. Haven't seen a single one.
Have you tried to install a portable version (instead of the standard installation which seems to stop according to your thread from September)?
Unfortunately you did not let us know how you solved it back in September...
If you download the newest available Beta-Version from here:
what exactly do you see after you have double-clicked the installer file called
mp3tagv324a-x64-setup.exe
What do you see if you copy & paste this path
%appdata%\Mp3tag
into your Windows File Explorer address bar?
I didn't solve it in September. I just kept v.3.18.
I see the same thing when dowloading the beta as I do when trying to download the released v3.24...I get as far as the agreement showing up, and everything disappears.
Here's what I see when I pasted the path:
====================================================================
Mp3tag v3.24 - 15.02.2024 - 15:50:47
--------------------------------------------------------------------------------
OS-Version: Windows 10 (build 19045), 64-bit
--------------------------------------------------------------------------------
Build: Jan 26 2024 15:03:10 (32-bit)
--------------------------------------------------------------------------------
AppPath: 23.214.817.280 Bytes frei (C:\Program Files (x86)\Mp3tag\)
DataPath: 23.214.817.280 Bytes frei (C:\Users\19033\AppData\Roaming\Mp3tag\data\)
TempPath: 23.214.817.280 Bytes frei (C:\Users\19033\AppData\Local\Temp\Mp3tag v3.24\)
====================================================================
Which version did you try to install this time?
Right now you seem to have installed 3.24 in 32-bit as standard installation.
Also, I am fairly puzzled that if you paste
to the address bar that you get a text file as that address points to a folder.
I don't know anything about a portable version.
... is an option during the installation.
- Standard
- Portable
If you have problems with the standard installation and you don't need the shell extension, then try to install MP3tag as portable.
At the risk of sounding dumb...how do I do that?
Start the installation again.
Acknowledge the licence conditions and click "Continue".
Select "Portable" in the next dialogue.
It doesn't allow me to get to the license conditions before it disappears.
Could it be that you had installed a version from the MS Store previously and also a 32-bit and 64-bit?
Your statement
but you see
So I would suggest the following:
Install a 32-bit version as this seems to be the last one.
Then uninstall it.
If that also fails, delete anything from MP3tag in the program files folder and the %appdata%\MP3tag folder and see if that helps.
Okay, will do. At this point I'm willing to try anything.
Please repeat your uninstallations until this Powershell command
Get-Package | where name -like Mp3tag* | Select-Object -Property Name, Version, FastPackageReference
does NOT show any information like this anymore:
Also the Powershell command
Get-AppxPackage -name *mp3tag*
should not return any information anymore.
Please double check your registry with this two CMD line commands:
reg query HKLM /s /f Mp3tag
and
reg query HKCU /s /f Mp3tag
there should be shown no information anymore.
Suggestion for Florian?
Considering the grief and confusion reported for so long and in so many posts here, I suspect that 32-bit installations on 64-bit machines should simply be blocked. The 32-bit installer could refuse to install or at the least should show a severe warning message before installation proceeds.
Of course such a block would not affect older 32-bit versions that the user may have retained, but even so I think that it might be beneficial.
I can't think of a compelling reason to install the wrong version on the current hardware. Does anyone know of one?
Actually, the problem is not that a 32-bit MP3tag is installed on a 64-bit OS but that for an already installed MP3tag version the attempt is made to install a different bit-architecture over the existing one. Or even mix the MS Store version with a downloaded version.
AFAIK you do get a warning that you try to do one of the above. If you ignore them, then you are in trouble.
The upper command brought forth 19 items. Sure looks like a lot to delete. The lower command brought forth nothing.
Thanks for the clarifcation. Since the warning is sometimes ignored, it might be better to abort such an install rather than to simply warn of trouble ahead....