P2-1: Surface unpackaged WinUI 3 limitations before developers invest time (#6665)

* P2-1: Surface unpackaged WinUI 3 limitations prominently

Key changes:
- unpackage-winui-app.md: Rename to 'Distribute an unpackaged WinUI 3
  app', improve title/description metadata, add prominent IMPORTANT
  callout at the top listing all four limitations before the how-to
  steps (no single-file EXE, runtime dependency, no package identity,
  not Store-eligible). Previously these were buried at the bottom.

- choose-distribution-path.md: Add 'Unpackaged WinUI 3' row to the
  main comparison table. Add full 'Unpackaged WinUI 3' section with
  honest pros/cons and 'for most apps MSIX is better' guidance.

- publish-first-app.md: Fix misleading '(for example, a self-contained
  EXE)' parenthetical — unpackaged WinUI 3 cannot produce single-file
  EXEs. Updated cross-link copy to be accurate.

Addresses P2-1 from Indie Dev Doc Plan Round 2 (04/20/2026).
Source: indie-dev-additional-findings.md finding #10 (SO 3k views).

Co-authored-by: Copilot <[email protected]>

* Address Copilot feedback: fix Store-eligibility, package identity, and MDM claims

- unpackage-winui-app.md: Add 'via package manifest' qualifier to 'No package identity' bullet
  (Win32 registry/shortcut mechanisms still work for unpackaged apps)
- unpackage-winui-app.md: Replace 'Not Store-eligible' with accurate statement:
  no MSIX path, but MSI/EXE installer submission is a separate path that does work
- unpackage-winui-app.md: Fix link text 'MSIX packaging' -> 'packaging your app' (points to overview)
- choose-distribution-path.md: Fix Enterprise MDM column for Unpackaged WinUI 3
  (Win32 Intune/ConfigMgr deployment does work; was incorrectly '❌ No')
- choose-distribution-path.md: Fix Store column for Unpackaged WinUI 3 (same MSI/EXE nuance)
- choose-distribution-path.md: Fix 'Not Store-eligible' in Limitations section
- publish-first-app.md: Add self-contained deployment qualifier to runtime dependency sentence

Co-authored-by: Copilot <[email protected]>

---------

Co-authored-by: Copilot <[email protected]>

Author: GrantMeStrength

hub/apps/package-and-deploy/choose-distribution-path.md

@@ -25,6 +25,7 @@ How you distribute your Windows app affects code signing costs, update mechanics
 | **MSIX sideload (enterprise)** | Internal LOB apps via Intune/ConfigMgr | 💲 Azure Artifact Signing (formerly Trusted Signing) (~$10/mo) or self-signed + Intune cert profile | ✅ Via App Installer file or MDM | ✅ Native | ❌ No |
 | **MSIX direct download (ISV)** | Commercial apps sold from your own site | 💲 CA-trusted cert required ([Azure Artifact Signing (formerly Trusted Signing)](/azure/trusted-signing/) recommended) | ✅ Via `.appinstaller` file | ⚠️ Limited | ❌ No |
 | **Packaging with external location** | Existing apps with own installer needing Windows features | 💲 Same as MSIX direct download | ✅ Your existing mechanism | ⚠️ Limited | ❌ No |
+| **Unpackaged WinUI 3** | Niche: enterprise without MSIX capability, or max install simplicity | 💲 Cert recommended for SmartScreen | ❌ Manual only | ⚠️ Limited (via Intune/ConfigMgr Win32 deployment) | ⚠️ Limited (Store-listed installer submission) |
 
 ## Microsoft Store (recommended)
 
@@ -150,7 +151,31 @@ If you have an existing app with its own installer (WiX, NSIS, InstallShield) an
 
 → [Grant package identity by packaging with external location](../desktop/modernize/grant-identity-to-nonpackaged-apps-overview.md)
 
-## What about other installer formats?
+## Unpackaged WinUI 3
+
+Unpackaged distribution removes MSIX from the picture entirely — the app runs directly from a folder without a package manifest. This is a niche option suited to specific scenarios.
+
+**What you get:**
+- Simpler build output (a folder of files, no MSIX tooling)
+- No MSIX infrastructure required on target machines
+- Works on machines where MSIX sideloading isn't enabled
+
+**Limitations:**
+- **No single-file EXE** — The Windows App SDK runtime must ship as separate files alongside your executable
+- **Runtime deployment** — You must bundle the Windows App SDK runtime installer, or use self-contained deployment (larger output)
+- **No package identity** — No automatic updates, no background tasks, no file type associations via manifest
+- **No MSIX/package-identity Store submission** — This model has no package identity and cannot be submitted to the Store as an MSIX package. A traditional installer (MSI/EXE) can be submitted separately, but that is outside this distribution path.
+- SmartScreen warnings unless signed with a CA-trusted certificate
+
+**When to choose this:**
+- Your target environment can't use MSIX (uncommon; most managed enterprise environments support MSIX)
+- You're building an internal tool where MSIX overhead isn't justified
+
+**For most WinUI 3 apps, MSIX (via Store or direct download) is the better path.** The limitations above often surprise developers who discover them after investing in unpackaged distribution.
+
+→ [Distribute an unpackaged WinUI 3 app](unpackage-winui-app.md) — step-by-step guide with runtime deployment options
+
+
 
 Many Windows apps are distributed using ClickOnce, MSI, WiX, Inno Setup, or similar technologies. These are established and supported options, especially for apps that can't use MSIX or don't need Store distribution. The table below summarizes the common options and their trade-offs.
 

hub/apps/package-and-deploy/publish-first-app.md

@@ -2,7 +2,7 @@
 title: Publish your first Windows app
 description: An end-to-end guide for indie developers — from a built app to users' hands. Covers choosing a distribution path, code signing, packaging, and getting your first users.
 ms.topic: concept-article
-ms.date: 04/17/2026
+ms.date: 04/20/2026
 ms.localizationpriority: high
 ---
 
@@ -46,7 +46,7 @@ How you package your app depends on the app framework you used.
 
 WinUI 3 apps created with the Windows App SDK project templates are **already packaged as MSIX by default**. When you build your solution in Visual Studio, the output is an `.msix` or `.msixbundle` file ready for Store submission or direct distribution.
 
-If you want to distribute an unpackaged WinUI 3 app (for example, a self-contained EXE), see [Unpackage a WinUI app](unpackage-winui-app.md).
+If you want to distribute an unpackaged WinUI 3 app (without MSIX packaging), see [Distribute an unpackaged WinUI 3 app](unpackage-winui-app.md). Note that unpackaged WinUI 3 apps cannot produce a single-file EXE and require the Windows App SDK runtime on the user's machine (either installed separately via the runtime installer, or bundled using self-contained deployment).
 
 ### WPF and WinForms
 

hub/apps/package-and-deploy/unpackage-winui-app.md

@@ -1,17 +1,29 @@
 ---
-title: How to unpackage a WinUI app
-description:  How to unpackage a WinUI app
+title: Distribute an unpackaged WinUI 3 app
+description: Learn how to set WindowsPackageType=None for unpackaged WinUI 3 distribution, understand the runtime deployment options, and review the key limitations before you start.
 ms.topic: how-to
-ms.date: 12/15/2025
-keywords: windows app sdk, winappsdk, winui
+ms.date: 04/20/2026
+keywords: windows app sdk, winappsdk, winui, unpackaged, WindowsPackageType, bootstrapper, self-contained
 ms.localizationpriority: medium
 content-type: how-to
-#Customer intent: As a Windows developer, I want to learn how to create an unpackaged WinUI app.
+#Customer intent: As a Windows developer, I want to distribute my WinUI 3 app without MSIX packaging and understand the limitations and runtime requirements.
 ---
 
-# Unpackage a WinUI 3 app
+# Distribute an unpackaged WinUI 3 app
 
-Packaging is an important part of any Windows App SDK project. For details on your options, see [Advantages and disadvantages of packaging your app](/windows/apps/package-and-deploy/#advantages-and-disadvantages-of-packaging-your-app).
+Unpackaged distribution lets you ship a WinUI 3 app without MSIX — useful for enterprise scenarios where MSIX deployment isn't available, or for developers who prefer a traditional folder-based install.
+
+> [!IMPORTANT]
+> **Review these limitations before you start.** Unpackaged WinUI 3 apps have constraints that affect your distribution strategy:
+>
+> - **No single-file EXE** — The Windows App SDK runtime and WinUI 3 dependencies must exist as separate files. The .NET single-file publish feature (`PublishSingleFile`) cannot bundle them into one executable. You will always distribute a folder of files (or wrap them in a traditional installer such as WiX or Inno Setup).
+> - **Runtime dependency** — The Windows App SDK runtime must be present on the user's machine. You must either bundle the runtime installer with your app, or use self-contained deployment (which significantly increases output size). See [Deploying the Windows App SDK runtime](#deploying-the-windows-app-sdk-runtime) below.
+> - **No package identity** — Without a package manifest, your app cannot use manifest-based Windows features: no automatic updates via App Installer or Store, no background task registration, and no file type associations or Start menu tile customization via package manifest. (Traditional Win32 mechanisms such as installer-written registry entries and shortcuts still work.)
+> - **No MSIX/package-identity Store submission** — This distribution model has no package identity; it is not eligible as an MSIX submission to the Microsoft Store. (You can submit a traditional installer to the Store via the [MSI or EXE installer submission path](../publish/publish-your-app/msi/upload-app-packages.md), but that is a separate workflow from what this article describes.)
+>
+> If these constraints are a concern, consider [packaging your app](index.md) (recommended for most apps) or [packaging with external location](../desktop/modernize/grant-identity-to-nonpackaged-apps-overview.md) to add package identity without a full MSIX conversion.
+
+For details on all packaging options, see [Advantages and disadvantages of packaging your app](/windows/apps/package-and-deploy/#advantages-and-disadvantages-of-packaging-your-app).
 
 If you choose to unpackage a new or existing WinUI app, follow these steps: