Skip to content

Note that installing an MSIX package with services requires elevation #509

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Roy (RDMacLachlan) wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Note that installing an MSIX package with services requires elevation #509

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1036ad1
Note that installing an MSIX package with services requires elevation
RDMacLachlan Aug 25, 2026
36b0ea2
Clarify service installation access
RDMacLachlan Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions msix-src/desktop/managing-your-msix-deployment-targetdevices.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
description: This article provides details that need to be considered when deploying your MSIX packages on Windows devices in an enterprise environment. This article is targeted at enterprise and IT Pros.
title: Plan for your deployment.
ms.date: 02/16/2021
ms.date: 08/25/2026
ms.topic: article
keywords: windows 10, deployment, msix
ms.assetid:
Expand All @@ -17,7 +17,12 @@ All developers also need to know the minimum supported operating system they wan
MSIX was introduced to Windows 10 version 1709 (10.0.16299.0) and greater. This means if you are using the basic MSIX functionality and targeting Windows 10 version 1709 or greater, it will just work. For a complete list of supporting operating systems and supporting features, see [Supported Platforms.](../supported-platforms.md)

## Services packaged in MSIX
The ability to package services in MSIX were introduced in Windows 10 Client 2004 (10.0.19041.0) and greater. Therefore if your application is using services packaged in MSIX it is limited to deployment on those operating systems. Admin privileges are required for installation due to the fact that a service may start in the background and make changes to the machine. To learn more about using MSIX Package Services in MSIX, see [Convert an installer that includes services.](../packaging-tool/convert-an-installer-with-services.md)

The ability to package services in MSIX was introduced in Windows 10 Client 2004
(10.0.19041.0) and later. If your MSIX package contains a Windows service, limit
package deployment to those operating systems. Installing the package requires
administrator privileges; for the reason and deployment consequences, see
[Convert an installer that includes services][convert-services].

## Server support for MSIX Packages
MSIX is not built into Windows Server. MSIX is however supported on Window 10 Server with Desktop Experience builds 1709 and greater when [AppInstaller application](https://www.microsoft.com/p/app-installer/9nblggh4nns1) is installed. If you are targeting earlier builds of the server, you must also install MSIX Core. For information on MSIX Core, see [MSIX Core.](../msix-core/msixcore.md)
Expand Down Expand Up @@ -66,3 +71,5 @@ Also, consider adding code to your packaged application that accomplishes these

For more information and examples, see [Transition users to your app](/windows/apps/desktop/modernize/desktop-to-uwp-distribute#transition-users-to-your-packaged-app).

[convert-services]: ../packaging-tool/convert-an-installer-with-services.md

16 changes: 14 additions & 2 deletions msix-src/packaging-tool/convert-an-installer-with-services.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,23 @@
---
title: Converting an installer with services
description: This article explains how to convert an existing installer with services to MSIX using the MSIX Packaging Tool
ms.date: 12/19/2019
ms.date: 08/25/2026
ms.topic: concept-article
keywords: windows 10, MSIX, MSIX Packaging Tool, services
---

# Convert an installer that includes services

Windows 10, version 2004, introduces support for running an MSIX package that includes services. You can use the MSIX Packaging Tool to take an existing installer with services and convert it to MSIX. This support is as of the January 2020 release of the [MSIX Packaging Tool](tool-overview.md)(1.2019.1220.0). Once you have a packaged MSIX with a service, it will require admin privileges to install on a machine.
Windows 10, version 2004, introduces support for running an MSIX package that includes services. You can use the MSIX Packaging Tool to take an existing installer with services and convert it to MSIX. This support is as of the January 2020 release of the [MSIX Packaging Tool](tool-overview.md)(1.2019.1220.0).

> [!IMPORTANT]
> When an MSIX package that contains a Windows service is installed, Windows registers
> the service in the [Service Control Manager (SCM) database][scm-database]. Creating
> a service requires `SC_MANAGER_CREATE_SERVICE` access to the SCM. By default, the
> [SCM security descriptor][scm-access-rights] grants this access to administrators.
> The SCM security descriptor governs access and can be modified, so administrator
> privileges aren't an absolute requirement. With the default SCM security
> descriptor, however, installing the package requires elevation.

## Instructions

Expand Down Expand Up @@ -40,3 +49,6 @@ We currently do not support services with dependencies outside the package.
## Add a service manually using your manifest

If you are manually adding a service to your application, you will need to [add a service](/uwp/schemas/appxpackage/uapmanifestschema/element-desktop6-service) to your app manifest. This does require a [restricted capability](/windows/uwp/packaging/app-capability-declarations#restricted-capabilities) to add to your application.

[scm-access-rights]: /windows/win32/services/service-security-and-access-rights
[scm-database]: /windows/win32/services/database-of-installed-services