Merge pull request #6671 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-21 05:00 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "hub/apps/publish/respond-to-customer-reviews.md",
+      "redirect_url": "/windows/apps/publish/analyze-msi-exe/ratings-reviews-performance#respond-to-customer-reviews",
+      "redirect_document_id": false
+    },   
     {
       "source_path": "hub/apps/publish/partner-center/account-types-locations-and-fees.md",
       "redirect_url": "/windows/apps/publish/partner-center/open-a-developer-account",

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

@@ -1,8 +1,8 @@
 ---
 title: Choose a distribution path for your Windows app
-description: Compare the available Windows app distribution paths — Microsoft Store, MSIX sideloading, and direct download — to find the right fit for your app and audience.
+description: Compare the available Windows app distribution paths — Microsoft Store, PWA, MSIX sideloading, and direct download — to find the right fit for your app and audience.
 ms.topic: concept-article
-ms.date: 04/17/2026
+ms.date: 04/20/2026
 ms.localizationpriority: medium
 ---
 
@@ -13,14 +13,19 @@ How you distribute your Windows app affects code signing costs, update mechanics
 > [!TIP]
 > **For most developers, the Microsoft Store is the recommended path.** It provides free code signing, built-in update delivery, broad discoverability, and a trusted install experience — with no infrastructure to manage.
 
+> [!NOTE]
+> **If your app is built on web technologies** (HTML, JavaScript, CSS), a [Progressive Web App (PWA)](#progressive-web-app-pwa) is the fastest path to the Microsoft Store — no native packaging tools required.
+
 ## Distribution paths at a glance
 
 | Path | Best for | Code signing cost | Auto-update | Enterprise MDM | Distributed via Store |
 |---|---|---|---|---|---|
 | **Microsoft Store** | Consumer and business apps, broad reach | ✅ Free (Store signs for you) | ✅ Built-in | ✅ Via Intune with Company Portal | ✅ Yes |
+| **PWA (Progressive Web App)** | Web apps and web-based experiences | ✅ Free (Store signs for you) | ✅ Via Store or browser | ✅ Via Intune with Company Portal | ✅ Yes |
 | **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)
 
@@ -45,6 +50,35 @@ Publishing to the Microsoft Store is the most complete distribution solution for
 
 → [Publish to the Microsoft Store](/windows/apps/publish/publish-your-app/msix/create-app-submission)
 
+## Progressive Web App (PWA)
+
+If your app is a website or built primarily on web technologies, a Progressive Web App is the fastest path to the Microsoft Store — with no native packaging tools or code signing purchase required.
+
+A PWA is a web app that browsers can install as a standalone app. It can run offline, send push notifications, appear in the Start menu and taskbar, and be distributed through the Microsoft Store. Use [PWABuilder](https://www.pwabuilder.com/) to package your site for Store submission in minutes.
+
+**What you get:**
+- Store distribution with free code signing (Store signs the package)
+- Works across any device with a modern browser
+- No manual MSIX, WiX, or installer authoring required — tools like [PWABuilder](https://www.pwabuilder.com/) generate the Store submission package for you
+- Built-in update delivery — users always get your latest web content (hosted content updates without a Store re-submission)
+
+**Requirements:**
+- App must be served over HTTPS
+- A [web app manifest](https://developer.mozilla.org/en-US/docs/Web/Manifest) and [service worker](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API)
+- App must pass [Store certification requirements](/windows/apps/publish/publish-your-app/msix/app-package-requirements)
+
+**Limitations:**
+- Deep native Windows APIs (file system access, hardware integration beyond Web APIs) are not available without additional bridging
+- App logic runs in a web context — not suitable for apps that require native .NET, C++, or WinRT APIs
+
+**When to choose this:**
+- Your app is a web app, SaaS tool, or content site you want to make installable
+- You want the fastest path to the Store with minimal tooling
+- Your feature requirements are satisfied by modern Web APIs
+
+→ [Overview of Progressive Web Apps](/microsoft-edge/progressive-web-apps-chromium/)  
+→ [Publish a PWA to the Microsoft Store with PWABuilder](https://docs.pwabuilder.com/#/builder/windows)
+
 ## MSIX sideloading — enterprise LOB distribution
 
 For internal line-of-business apps that will be deployed to managed devices via Microsoft Intune or Configuration Manager, MSIX sideloading is the recommended path.
@@ -117,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.
 
@@ -158,4 +216,5 @@ Regardless of your packaging format, you can submit a manifest to the [Windows P
 - [SmartScreen reputation for Windows app developers](smartscreen-reputation.md)
 - [Current status of Windows app distribution features](distribution-feature-status.md)
 - [Publish to the Microsoft Store](/windows/apps/publish/)
+- [Progressive Web Apps overview](/microsoft-edge/progressive-web-apps-chromium/)
 - [Azure Artifact Signing (formerly Trusted Signing)](/azure/trusted-signing/)

hub/apps/package-and-deploy/code-signing-options.md

@@ -2,7 +2,7 @@
 title: Code signing options for Windows app developers
 description: Compare code signing options for distributing Windows apps outside the Microsoft Store — including Azure Artifact Signing, OV/EV certificates, and when no signing is needed.
 ms.topic: concept-article
-ms.date: 04/17/2026
+ms.date: 04/20/2026
 ms.localizationpriority: medium
 ---
 
@@ -25,7 +25,7 @@ If you publish your app through the Microsoft Store, code signing is free and ha
 
 Publishing through the Microsoft Store is the recommended distribution path for most Windows apps. Microsoft re-signs your package automatically, meaning users never see a SmartScreen warning and you never need to purchase or renew a certificate.
 
-A one-time $19 developer account fee gives you access to [Partner Center](https://partner.microsoft.com/dashboard), where you submit your app and manage its listing.
+Create a free developer account at [storedeveloper.microsoft.com](https://storedeveloper.microsoft.com). After you register, use [Partner Center](https://partner.microsoft.com/dashboard) to submit your app and manage its listing.
 
 → [Publish your app to the Microsoft Store](/windows/apps/publish/publish-your-app/msix/create-app-submission)
 

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
 ---
 
@@ -19,7 +19,7 @@ Your distribution path determines your code signing costs, update mechanics, how
 
 → [Choose a distribution path for your Windows app](choose-distribution-path.md) has a full comparison. In short:
 
-- **Microsoft Store** — recommended for most apps. Free signing, built-in updates, broad discoverability, and a trusted install experience. Requires a one-time $19 [Partner Center](https://partner.microsoft.com/dashboard) developer account fee.
+- **Microsoft Store** — recommended for most apps. Free signing, built-in updates, broad discoverability, and a trusted install experience. Requires a free developer account — register at [storedeveloper.microsoft.com](https://storedeveloper.microsoft.com).
 - **Direct download** — appropriate for commercial ISVs with their own storefront, enterprise LOB apps, or apps with content the Store doesn't permit. You are responsible for signing, hosting, and updates.
 
 Most new indie apps are a good fit for the Store. If you're unsure, start there.
@@ -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
 
@@ -75,7 +75,7 @@ The Store submission process runs through [Partner Center](https://partner.micro
 
 **Steps at a glance:**
 
-1. **Create a developer account** — One-time $19 fee at [Partner Center](https://partner.microsoft.com/dashboard). The account is permanent.
+1. **Create a developer account** — Free. Register at [storedeveloper.microsoft.com](https://storedeveloper.microsoft.com). The account is permanent.
 2. **Reserve your app name** — Claim your app's name in Partner Center before submission. The name is held for you during development.
 3. **Build and package your app** — Create an MSIX package that meets Store requirements. For Store submissions, MSIX/AppX packages don't need a CA-trusted signature — Microsoft re-signs the package with a Microsoft certificate after certification. If you distribute outside the Store using an MSI or EXE installer, Authenticode signing is recommended and expected by Windows security features.
 4. **Create your submission** — Upload your package, provide store listing details (description, screenshots, categories, age rating), and set pricing.

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: