Skip to content

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

Draft
Roy (RDMacLachlan) wants to merge 2 commits into
MicrosoftDocs:mainfrom
RDMacLachlan:users/romaclac/docbug-31941147
Draft

Note that installing an MSIX package with services requires elevation#509
Roy (RDMacLachlan) wants to merge 2 commits into
MicrosoftDocs:mainfrom
RDMacLachlan:users/romaclac/docbug-31941147

Conversation

@RDMacLachlan

Copy link
Copy Markdown
Collaborator

Summary

Adds an install-time elevation note for MSIX packages that contain Windows services, explains why service registration requires administrative rights, and cross-references the deployment guidance.

Related work item

Resolves AB#31941147.

ADO bug: https://dev.azure.com/microsoft/OS/_workitems/edit/31941147

Add an install-time elevation note for MSIX packages that contain Windows services, including why service registration requires administrative rights. Update the related target-devices page to cross-reference the detailed explanation.

References ADO bug 31941147.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 4b5b11f6-6bf8-4401-90b8-68f710728c8e
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 1036ad1:

✅ Validation status: passed

File Status Preview URL Details
msix-src/desktop/managing-your-msix-deployment-targetdevices.md ✅Succeeded
msix-src/packaging-tool/convert-an-installer-with-services.md ✅Succeeded

For more details, please refer to the build report.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds clearer guidance to the MSIX documentation that packages containing Windows services require elevation at install/deploy time, and connects that guidance to deployment planning documentation.

Changes:

  • Added an IMPORTANT note explaining why MSIX packages with Windows services require elevated installation (service registration / SCM).
  • Updated deployment planning guidance to reference the services conversion article for rationale and deployment implications.
  • Refreshed ms.date metadata in both articles.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
msix-src/packaging-tool/convert-an-installer-with-services.md Adds an IMPORTANT elevation note and supporting SCM references; updates ms.date.
msix-src/desktop/managing-your-msix-deployment-targetdevices.md Updates the “Services packaged in MSIX” guidance and adds a reference-style link to the services conversion doc; updates ms.date.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread msix-src/packaging-tool/convert-an-installer-with-services.md Outdated
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@learn-build-service-prod

Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 36b0ea2:

✅ Validation status: passed

File Status Preview URL Details
msix-src/desktop/managing-your-msix-deployment-targetdevices.md ✅Succeeded
msix-src/packaging-tool/convert-an-installer-with-services.md ✅Succeeded

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants