# Scripts Lost In Upgrade to V3.20

**URL:** https://community.mp3tag.de/t/scripts-lost-in-upgrade-to-v3-20/60876
**Category:** Support
**Tags:** installation
**Created:** [May 3, 2023, 3:34pm UTC](https://community.mp3tag.de/t/scripts-lost-in-upgrade-to-v3-20/60876 "2023-05-03T15:34:20Z")
**Posts on this page:** 1
**Showing post:** 4

<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: [May 3, 2023, 5:20pm UTC](https://community.mp3tag.de/t/scripts-lost-in-upgrade-to-v3-20/60876/4 "2023-05-03T17:20:54Z")

</div>

right next to the download link was/is a link to notes that best should be followed:

> [@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 …

You could try to un-install the 64-bit version,  
install the 32-bit-version in the same way you did before you switched to 64-bti,  
check, whether the settings you are now missing, are still there,  
save the configuration in a safe place,  
un-install the 32-bit-version,  
install the 64-bit-version,  
restore the settings from the saved configuration.

---

_[View the full topic](https://community.mp3tag.de/t/scripts-lost-in-upgrade-to-v3-20/60876)._