microsoft / microsoft/WindowsAppSDK
[BUG] Updating MSIX Results in a Stopped Service
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.7k
- Forks
- 471
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 28
Description
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?
Steps to reproduce the bug
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
NuGet package version
2.0.1
Packaging type
Packaged (MSIX)
Windows version
No response
IDE
No response
Additional context
I found this old blog post that describes using events to trigger windows services without elevation. There's also this recent blog post
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 with an MSIX package whose manifest declares another binary as a system service, then observe the service in the Services app after the update. Trace the packaged service update behavior and verify that the service is automatically restarted rather than left in the “Start” state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100