microsoft / microsoft/msix-packaging
[BUG] Updating MSIX Results in a Stopped Service
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Project
MSIX SDK
Describe the bug
We are working on a VPN app and when testing updating with a VPN connection, we see that the GUI is stopped, the VPN remains connected (as desired), but when the GUI launches, the service remains stopped. An MSIX Update doesn't seem to restart the service?
To Reproduce
Create an MSIX package with another binary as the service. In the package manifest, state that binary as a system service. On update, the service will show "Start" in the services app.
Expected behavior
Auto restart of the service.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform
Windows 11
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the update on Windows 11 with an MSIX package whose manifest declares a separate binary as a system service. Investigate the service state after the update; done means the service is automatically running again while the VPN remains connected.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100