# 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:** 1
**Showing post:** 2

<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.

---

_[View the full topic](https://community.mp3tag.de/t/cannot-upgrade-to-v3-22-from-v3-20/61987)._