# Staging sparse package failed : Win11 no context menu

**URL:** https://community.mp3tag.de/t/staging-sparse-package-failed-win11-no-context-menu/59121
**Category:** Support
**Created:** [November 19, 2022, 9:57pm UTC](https://community.mp3tag.de/t/staging-sparse-package-failed-win11-no-context-menu/59121 "2022-11-19T21:57:37Z")
**Posts on this page:** 1
**Showing post:** 3

<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: [November 20, 2022, 7:15am UTC](https://community.mp3tag.de/t/staging-sparse-package-failed-win11-no-context-menu/59121/3 "2022-11-20T07:15:18Z")

</div>

Have you followed the extra notes when installing the 64 bit version?

> [@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-win11-no-context-menu/59121)._