Building app on Visual Studio almost always generates a blank executable.

Describe the bug

Building app on Visual Studio almost always generates a blank executable which does not open. It's process stays on for at least 3 seconds and then it gets killed.

Why is this important?

Any user won't be opening the app without this, i can't share an executable with this problem because my app will not work.

Steps to reproduce the bug

1. Build using any type(unpackaged/packaged and release/debug)
2. When the build is over, go to the path of the project
3. Find the executable and try to execute it.

Actual behavior

The build will fail to work and the process will be killed in moments.

Expected behavior

It should open like in the dev build, which surprisingly works. I tried everything, this is my last resort.

Screenshots

No response

NuGet package version

WinUI 3 - Windows App SDK 1.8.3: 1.8.251106002

Windows version

Windows 11 (24H2): Build 26100

Additional context

I tried in both IoT LTSC and Consumer Version, none works. I tried in VS2022 AND VS2026, nothing worked.

Start by reproducing the issue in Visual Studio with WinUI 3 and Windows App SDK 1.8.3 on Windows 11, checking both the working dev build and the failing executable. Compare packaged and unpackaged release/debug outputs; done means the generated executable opens and remains running.