# Cannot upgrade to v3.22 from v3.20

**URL:** https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987
**Category:** Support
**Tags:** installation
**Created:** [August 30, 2023, 2:35pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987 "2023-08-30T14:35:45Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![CeHa](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/3e96dc/32.png) [@CeHa](https://community.mp3tag.de/u/CeHa)
#### Post date: [August 30, 2023, 2:35pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/1 "2023-08-30T14:35:45Z")

</div>

![bild](https://community.mp3tag.de/uploads/default/original/2X/c/c02ed1a305f78d73f255996b9101443788de0b65.png)  
My current version is a confirmed 32-bit v3.20 in C:\Program Files (x86)\Mp3tag.  
When running the new mp3tagv322setup.exe the process halts claiming it has found a 64-bit installation in that folder, but a thorough search in the standard and (x86) program files shows no other occurance of an Mp3tag related exe file. Throughout the Registry the only path mentioned is C:\Program Files (x86)\Mp3tag. It's possible to Uninstall Mp3tag neither from Windows settings nor directly with Mp3tagUninstall.exe. I'm stuck with v3.20.  
Fully updated 64-bit Win10.

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [August 30, 2023, 2:41pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/2 "2023-08-30T14:41:39Z")

</div>

See here for further notes on how to switch from 32- to 64-bit

> [@Notes on the 64-bit version of Mp3tag](https://community.mp3tag.de/t/notes-on-the-64-bit-version-of-mp3tag/57250):
>
> I've released a [64-bit version of Mp3tag](https://community.mp3tag.de/t/455) a few days ago and received a few questions about differences between the 32-bit version and the 64-bit version. To make it short, there should not be any noticeable differences except for two things: The 64-bit version uses 64-bits to address memory and is no longer limited to 2 GB per application. While the [Library](https://docs.mp3tag.de/customization/options/library) feature of Mp3tag is already a very viable solution for large libraries, loosening the memory restriction is one of the key benefits of …

If you can, install the old 3.20 in 32-bit,  
save the configuration,  
unistall the 32-bit version  
then install the 64-bit version.  
Restore the configuration.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 30, 2023, 2:43pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/3 "2023-08-30T14:43:18Z")

</div>

> [@Found existing installation error](https://community.mp3tag.de/t/found-existing-installation-error/61078/13):
>
> This happens if both the 32-bit and the 64-bit version are installed. In this case, the easiest solution is to just uninstall the "active" version via Windows Settings → Apps & Features and then run the installer again. If it still complains, you need to install the version with the different architecture. Deleting the installation files manually (including the uninstaller, which is not recommended) added the extra difficulty in this case.

---

<div class="post-metadata">

### Author: ![CeHa](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/3e96dc/32.png) [@CeHa](https://community.mp3tag.de/u/CeHa)
#### Post date: [August 30, 2023, 2:45pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/4 "2023-08-30T14:45:01Z")

</div>

Unfortunately installing the old v3.20 doesn't work either!

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 30, 2023, 2:51pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/5 "2023-08-30T14:51:42Z")

</div>

Not sure, but have you seen the post I've linked to above and tried to follow the instructions?

---

<div class="post-metadata">

### Author: ![CeHa](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/3e96dc/32.png) [@CeHa](https://community.mp3tag.de/u/CeHa)
#### Post date: [August 30, 2023, 3:01pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/6 "2023-08-30T15:01:41Z")

</div>

Yes, as I said uninstalling from Windows Settings doesn't work. The only Mp3tag item there refers to a 64-bit v3.17 that has no uninstall exe. I have installed 32-bit v3.18, v3.19 and v3.20 after that without any issues. There isn't any 64-bit Mp3tag on the PC.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 30, 2023, 3:16pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/7 "2023-08-30T15:16:50Z")

</div>

> [@CeHa](#):
>
> Yes, as I said uninstalling from Windows Settings doesn't work. The only Mp3tag item there refers to a 64-bit v3.17 that has no uninstall exe

OK, then this version was probably uninstalled by deleting the files, leaving traces in the system that are now causing the trouble. The 64-bit branch of the Windows registry still has entries that are now detected by the installer as an installed 64-bit version.

Can you install this version again and uninstall it via the Windows Settings? Here is the [download for mp3tagv317-x64-setup.exe](https://download.mp3tag.de/versions/mp3tagv317-x64-setup.exe), in case you need it.

---

<div class="post-metadata">

### Author: ![CeHa](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/3e96dc/32.png) [@CeHa](https://community.mp3tag.de/u/CeHa)
#### Post date: [August 30, 2023, 3:31pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/8 "2023-08-30T15:31:01Z")

</div>

Installed v3.17 and then tried to uninstall it from Windows settings, but it complained that this file is not associated with any app.

---

<div class="post-metadata">

### Author: ![CeHa](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/3e96dc/32.png) [@CeHa](https://community.mp3tag.de/u/CeHa)
#### Post date: [August 30, 2023, 3:52pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/9 "2023-08-30T15:52:40Z")

</div>

Interesting: tried to install v3.21, but same trouble. However. v3.20 installed just fine, but not present in Windows settings. Still v.3.17 there.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 30, 2023, 4:28pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/10 "2023-08-30T16:28:07Z")

</div>

OK, this seems to be more chaotic than I assumed. You probably installed the "current" v3.17 to a different folder than what's referenced in Windows settings.

Please try the route which was successful in the referenced case and remove the entries manually via RegEdit.exe

> [@Found existing installation error](https://community.mp3tag.de/t/found-existing-installation-error/61078/12):
>
> Ok thanks, i searched and removed every "mp3tag" entry in my RegEdit manually. ...It worked! Installation was successful, program is running and I'm tagging again wink

Also, I'm moving this from #Bug Reports to #Support .

---

<div class="post-metadata">

### Author: ![CeHa](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/3e96dc/32.png) [@CeHa](https://community.mp3tag.de/u/CeHa)
#### Post date: [August 30, 2023, 4:54pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/11 "2023-08-30T16:54:30Z")

</div>

Thanks for your patient assistance - it's appreciated! I'll go ahead with Reg cleaning when I have the time.

---

<div class="post-metadata">

### Author: ![CeHa](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/3e96dc/32.png) [@CeHa](https://community.mp3tag.de/u/CeHa)
#### Post date: [August 30, 2023, 5:58pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/12 "2023-08-30T17:58:08Z")

</div>

Did it with tung in cheek, and now v3.22 is running and v3.17 is replaced by v.3.22 in Windows Settings. Excellent support Florian for this great app.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 30, 2023, 6:11pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/13 "2023-08-30T18:11:33Z")

</div>

Perfect! Happy it's back working and thanks for letting us know 🙌

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [September 29, 2023, 6:12pm UTC](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987/14 "2023-09-29T18:12:07Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
