# Staging Sparse Package failed

**URL:** https://community.mp3tag.de/t/staging-sparse-package-failed/65540
**Category:** Support
**Tags:** installation
**Created:** [August 9, 2024, 8:27pm UTC](https://community.mp3tag.de/t/staging-sparse-package-failed/65540 "2024-08-09T20:27:50Z")
**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 9, 2024, 8:38pm UTC](https://community.mp3tag.de/t/staging-sparse-package-failed/65540/2 "2024-08-09T20:38:50Z")

</div>

Depends if you followed the notes on switching between the bit-versions:

> [@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/staging-sparse-package-failed/65540)._