Document which services MSIX supports and doesn't support - #483
Open
RDMacLachlan wants to merge 1 commit into
Open
Document which services MSIX supports and doesn't support#483RDMacLachlan wants to merge 1 commit into
RDMacLachlan wants to merge 1 commit into
Conversation
Partner feedback (AppConsult/Lenovo) asked for guidance on what kinds of Windows services can and can't be included in an MSIX package. The services conversion topic explained the tool workflow but never gave an explicit supported-vs-unsupported list. Add a "Supported and unsupported services" section based on the desktop6:Service manifest extension and the MSIX Packaging Tool: - Supported: user-mode Win32 services; Local System / Local Service / Network Service accounts; Automatic / Manual / Disabled startup (plus Delayed in the tool); in-package service dependencies and trigger events. - Not supported: kernel-mode services and device drivers (INF-based driver install); custom/arbitrary user accounts; dependencies on services outside the package. - Requirements: Windows 10, version 2004+ to run; packagedServices or localSystemServices restricted capability; admin to install. Also name the specific restricted capability (packagedServices / localSystemServices) on the manual manifest-edit step, which previously referred only to "a restricted capability". Bump ms.date. Resolves AB#25952010 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Learn Build status updates of commit 13fdf2a: ✅ Validation status: passed
For more details, please refer to the build report. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves partner feedback (AppConsult / Lenovo) asking for guidance on what kinds of Windows services MSIX supports and doesn't support (AB#25952010).
Problem
convert-an-installer-with-services.mddocumented the MSIX Packaging Tool workflow but never gave an explicit supported vs. unsupported list — the exact ask.Fix
Add a "Supported and unsupported services" section, sourced from the
desktop6:Servicemanifest schema and the MSIX Packaging Tool:packagedServicesorlocalSystemServicesrestricted capability; admin privileges to install.Also names the specific restricted capability on the manual manifest-edit step (previously just "a restricted capability").
ms.datebumped.All values verified against the current
desktop6:Serviceschema reference; the "no drivers" statement matches existing repo guidance indesktop-to-uwp-prepare.md,know-your-installer.md, andtool-known-issues.md.