--- title: External Location | daily.dev description: MSIX External Location lets an existing installer add package identity and Windows integration without fully migrating to MSIX. Windows still stages the... canonical: https://daily.dev/posts/external-location-psdksr8zs twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: External Location | daily.dev og:description: MSIX External Location lets an existing installer add package identity and Windows integration without fully migrating to MSIX. Windows still stages the... og:url: https://daily.dev/posts/external-location-psdksr8zs og:image: https://api.daily.dev/og/posts/pSDKsR8Zs.png og:image:alt: External Location og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # External Location **[DevBlogs](https://daily.dev/sources/devblogs)** · 4 min read · 0 upvotes · 0 comments ## Summary MSIX External Location lets an existing installer add package identity and Windows integration without fully migrating to MSIX. Windows still stages the package's manifest and footprint files at the normal install path, but looks for payload files like the executable at a separate location you specify at install time. You enable this with `uap10:AllowExternalContent` set to true in `AppxManifest.xml`, and the `-ExternalLocation` parameter on `Add-AppxPackage`. MSIX then doesn't own, repair, secure or uninstall those external files; it just knows where to find them, a pattern informally called 'Bring Your Own Installer'. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I add MSIX package identity to an app without replacing my existing installer? Use MSIX External Location: set uap10:AllowExternalContent to true in AppxManifest.xml, then install with Add-AppxPackage using the -ExternalLocation parameter pointing to where your existing installer placed the app's files, for example D:\MyApps\Contoso. Windows stages the manifest at the normal install path but activates the executable from the external location, so your installer keeps managing the payload files. _Teams weighing a full MSIX migration against incremental adoption can compare approaches like this on daily.dev._ ### What is the difference between a package's install location and its External Location in MSIX? The install location always holds the AppxManifest.xml, AppxBlockMap.xml and other footprint files, such as C:\Program Files\WindowsApps\Contoso.Invoice_4.1.2023.0_x64__eh4htm4n7tdre. The External Location is a separate, additional path specified at install time where Windows looks for payload files like the executable, icons or data files referenced in the manifest; it supplements rather than replaces the install location. _Developers mapping out MSIX packaging decisions can track details like this on daily.dev._ ### Why is AllowExternalContent required even though it sounds optional in MSIX manifests? AllowExternalContent true must be declared in AppxManifest.xml to install a package with an External Location, and conversely a package must be installed with an External Location if its manifest sets AllowExternalContent true. The element name is considered a misnomer, since it functions more like a required 'RequireExternalContent' flag rather than a true opt-in allowance. _Developers debugging MSIX manifest quirks can keep facts like this handy via daily.dev._ ## Similar posts on daily.dev - [MSIX PackageVolume: How Package Storage Works](https://daily.dev/posts/msix-packagevolume-how-package-storage-works-zf6hqlo1t) · DevBlogs · 0 upvotes · 0 comments - [Packaging and Package Identity for .NET apps with WinApp CLI on Windows](https://daily.dev/posts/packaging-and-package-identity-for-net-apps-with-winapp-cli-on-windows-x0qqcad7l) · .NET Blog · 1 upvotes · 0 comments - [Package Integrity and Enforcement](https://daily.dev/posts/package-integrity-and-enforcement-sghfrytts) · DevBlogs · 0 upvotes · 0 comments - [I rebuilt my Windows PC from one YAML file, and I'm never clicking through installers again](https://daily.dev/posts/i-rebuilt-my-windows-pc-from-one-yaml-file-and-i-m-never-clicking-through-installers-again-y9nblapti) · XDA Developers · 0 upvotes · 0 comments - [Microsoft now lets admins choose pre-installed Store apps to uninstall](https://daily.dev/posts/microsoft-now-lets-admins-choose-pre-installed-store-apps-to-uninstall-udekprfgo) · BleepingComputer · 0 upvotes · 0 comments --- Tags: [#windows](https://daily.dev/tags/windows) [View this post on daily.dev](https://daily.dev/posts/external-location-psdksr8zs) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"External Location","url":"https://daily.dev/posts/external-location-psdksr8zs","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/external-location-psdksr8zs"},"datePublished":"2026-10-27T16:02:07.577Z","dateModified":"2026-10-27T16:10:52.281Z","description":"MSIX External Location lets an existing installer add package identity and Windows integration without fully migrating to MSIX. Windows still stages the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cc43ae795c3bd4683451b398b46358e1?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/cc43ae795c3bd4683451b398b46358e1?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"DevBlogs","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"DevBlogs","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8f68b453325f482ebeb73fb780092713","url":"https://daily.dev/sources/devblogs"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/external-location-psdksr8zs","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"windows","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DevBlogs","item":"https://daily.dev/sources/devblogs"},{"@type":"ListItem","position":3,"name":"External Location"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/external-location-psdksr8zs#faq","mainEntity":[{"@type":"Question","name":"How do I add MSIX package identity to an app without replacing my existing installer?","acceptedAnswer":{"@type":"Answer","text":"Use MSIX External Location: set uap10:AllowExternalContent to true in AppxManifest.xml, then install with Add-AppxPackage using the -ExternalLocation parameter pointing to where your existing installer placed the app's files, for example D:\\MyApps\\Contoso. Windows stages the manifest at the normal install path but activates the executable from the external location, so your installer keeps managing the payload files. Teams weighing a full MSIX migration against incremental adoption can compare approaches like this on daily.dev."}},{"@type":"Question","name":"What is the difference between a package's install location and its External Location in MSIX?","acceptedAnswer":{"@type":"Answer","text":"The install location always holds the AppxManifest.xml, AppxBlockMap.xml and other footprint files, such as C:\\Program Files\\WindowsApps\\Contoso.Invoice_4.1.2023.0_x64__eh4htm4n7tdre. The External Location is a separate, additional path specified at install time where Windows looks for payload files like the executable, icons or data files referenced in the manifest; it supplements rather than replaces the install location. Developers mapping out MSIX packaging decisions can track details like this on daily.dev."}},{"@type":"Question","name":"Why is AllowExternalContent required even though it sounds optional in MSIX manifests?","acceptedAnswer":{"@type":"Answer","text":"AllowExternalContent true must be declared in AppxManifest.xml to install a package with an External Location, and conversely a package must be installed with an External Location if its manifest sets AllowExternalContent true. The element name is considered a misnomer, since it functions more like a required 'RequireExternalContent' flag rather than a true opt-in allowance. Developers debugging MSIX manifest quirks can keep facts like this handy via daily.dev."}}]} ```