microsoft / microsoft/WindowsAppSDK

Noisy DeploymentManager exceptions in 1.8 Exp 2

Open
#5,447 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-WinAppSDKDeployment needs-triage
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

Describe the bug

In 1.8 Exp 2, the Deployment Manager is now included in the app by default, rather than requiring developers to manually call it. However, DeploymentManager.Initialize (in DeploymentManagerAutoInitializer.cs) throws a noisy (non-fatal) exception during startup, i.e.

Exception thrown at 0x00007FFF80C56798 in app.exe: Microsoft C++ exception: 
wil::ResultException at memory location 0x0000002D3619B750.

The output window shows:

Exception thrown at 0x00007FFF80C56798 (KernelBase.dll) in app.exe: WinRT originate error - 0x80070057 : 'The parameter is incorrect.'.
C:\__w\1\s\dev\Deployment\DeploymentManager.cpp(312)\Microsoft.WindowsAppRuntime.dll!00007FFE8E3834A8: (caller: 00007FFE8E3834FC) Exception(1) tid(4990) 80070057 The parameter is incorrect.
Steps to reproduce the bug

Install Windows App SDK 1.8 Exp 2, use single-project MSIX mode (EnableMsixTooling=true) and launch the app packaged.

Expected behavior

There shouldn't be exceptions during launch

Screenshots

No response

NuGet package version

Windows App SDK 1.8 Experimental 2: 1.8.250515001-experimental2

Packaging type

Packaged (MSIX)

Windows version

Insider Build (xxxxx)

IDE

Visual Studio 2022-preview

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce with Windows App SDK 1.8 Experimental 2 in a single-project MSIX app using EnableMsixTooling=true. Start with DeploymentManagerAutoInitializer.cs and DeploymentManager.cpp around line 312, then verify that packaged app startup no longer emits the reported non-fatal exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, csharp
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.