The project doesn't know how to run the profile with name 'machine-name' and command 'MsixPackage'

WoodManEXP 80 Reputation points
2026-09-03T19:10:10.0733333+00:00

Hi,

My laptop has just upgraded from an older Windows 10 laptop to a newer Windows 11 laptop. The Visual Studio Community also updated itself to 18.9.2.

Unfortunately, now when attempting to build and debug this UWP C# app (either for the local laptop or for an XBox) VS shows this message when trying to launch the debugger

The project doesn't know how to run the profile with name 'machine-name' and command 'MsixPackage'.

There are references to this condition out there, but my attempts to research and correct this are not finding an answer. Can you point me to ideas to resolve this?

TY!

Developer technologies | Universal Windows Platform (UWP)
0 comments No comments

1 answer

Sort by: Most helpful
  1. Gatlin Le (WICLOUD CORPORATION) 0 Reputation points Microsoft External Staff Moderator
    2026-09-04T03:24:00.75+00:00

    Hi @WoodManEXP ,

    Thank you for reaching out, and thank you for your patience while your question was awaiting a response.

    I understand how frustrating this must be, particularly when the issue appears after changing your development environment. The message indicates that Visual Studio is attempting to use a launch profile with the MsixPackage command that is not currently being handled by the selected project. Before determining the exact cause, I would like to verify the current startup and deployment configuration.

    As an initial check, please try the following:

    1. In Solution Explorer, right-click the UWP application project and select Set as Startup Project.
    2. Select Build > Configuration Manager, and confirm that the Deploy check box is selected for the UWP project under the active configuration and platform.
    3. In the dropdown next to the Start Debugging button, check which deployment target is selected. If Local Machine is available, select it and try launching the debugger again.

    Microsoft describes the available UWP deployment targets in the Picking a deployment target section of Deploying and debugging UWP apps. Please note that Local Machine is only offered when the project's Target Platform Min. Version is less than or equal to the operating system on your development machine, so it would also be helpful to confirm the target and minimum versions configured in your project.

    Since the issue began after Visual Studio was installed or updated on the new computer, please also verify that the required UWP development components are installed. The applicable workloads and components are listed in Change workloads and individual components.

    If the issue persists, please provide the following information:

    • The project currently set as the startup project
    • The option selected in the debug-target dropdown
    • The Target version and Minimum version configured for the project
    • Whether the Deploy check box is selected in Configuration Manager
    • Whether the solution contains a separate packaging project
    • Any related messages shown in the Output or Error List window

    You may provide these details in writing or by sharing a screenshot, whichever is more convenient. If you choose to share a screenshot, please remove or cover any personal or confidential information.

    This information will help me determine whether the next troubleshooting step should focus on the startup project, the deployment configuration, or the UWP components installed with Visual Studio.

    If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance or provide feedback.

    Thank you.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.