# Nach der installation von 3.18 kein Fenster

**URL:** https://community.mp3tag.de/t/nach-der-installation-von-3-18-kein-fenster/58623
**Category:** Allgemein
**Created:** [September 29, 2022, 5:47pm UTC](https://community.mp3tag.de/t/nach-der-installation-von-3-18-kein-fenster/58623 "2022-09-29T17:47:49Z")
**Posts on this page:** 1
**Showing post:** 19

<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: [October 3, 2022, 7:41am UTC](https://community.mp3tag.de/t/nach-der-installation-von-3-18-kein-fenster/58623/19 "2022-10-03T07:41:36Z")

</div>

Nun ist es schwer zu beantworten, ob du vorher eine portable Installation gehabt hast oder eine Standard-Installation.  
Und dann gibt es auch noch diese Hinweise:

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

---

_[View the full topic](https://community.mp3tag.de/t/nach-der-installation-von-3-18-kein-fenster/58623)._