# How to deploy side-loaded extensions?

**URL:** <https://discourse.mozilla.org/t/how-to-deploy-side-loaded-extensions/4051>\
**Category:** Add-on Support\
**Created:** [September 14, 2015, 4:15pm UTC](https://discourse.mozilla.org/t/how-to-deploy-side-loaded-extensions/4051 "2015-09-14T16:15:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![w\_steinhour](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/w_steinhour/32/21176_2.png) [@w\_steinhour](https://discourse.mozilla.org/u/w_steinhour)\
**Post date:** [September 14, 2015, 4:15pm UTC](https://discourse.mozilla.org/t/how-to-deploy-side-loaded-extensions/4051/1 "2015-09-14T16:15:07Z")

</div>

I am trying to figure out how to deploy an extension in my application intaller. The new requirement for signing has me a little confused. I just successfully got my extension signed. (Thanks for a quick turnaround, Mozilla!) In the past, we have used the Windows registry [mechanism](https://developer.mozilla.org/en-US/docs/Adding_Extensions_using_the_Windows_Registry), but that only seems to work with unpacked extensions. If I unzip my signed extension, Firefox does not trust it. How can I deploy a signed extension with my application installer?

Wayne

---

<div class="post-metadata">

**Author:** ![w\_steinhour](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/w_steinhour/32/21176_2.png) [@w\_steinhour](https://discourse.mozilla.org/u/w_steinhour)\
**Post date:** [September 15, 2015, 3:39pm UTC](https://discourse.mozilla.org/t/how-to-deploy-side-loaded-extensions/4051/2 "2015-09-15T15:39:20Z")

</div>

I discovered the answer to my own question, so I will post it here in case it may benefit anyone else.

Putting the path to the signed extension in the registry does work, but the path must include the name of the signed xpi file. It cannot just be the path of the folder that contains it (which was the case for unpacked extensions).

I hope this helps someone else.