# Shell Extension install fails. "provisioning sparse package failed" 3.20b-x64 Win 11

**URL:** https://community.mp3tag.de/t/shell-extension-install-fails-provisioning-sparse-package-failed-3-20b-x64-win-11/60857
**Category:** Support
**Tags:** installation
**Created:** [May 2, 2023, 3:17am UTC](https://community.mp3tag.de/t/shell-extension-install-fails-provisioning-sparse-package-failed-3-20b-x64-win-11/60857 "2023-05-02T03:17:37Z")
**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: [May 2, 2023, 5:20am UTC](https://community.mp3tag.de/t/shell-extension-install-fails-provisioning-sparse-package-failed-3-20b-x64-win-11/60857/2 "2023-05-02T05:20:12Z")

</div>

Looks to me like you installed a 64-bit version over a 32-bit version.  
Did you follow the notes when installing a 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/shell-extension-install-fails-provisioning-sparse-package-failed-3-20b-x64-win-11/60857)._