Program 'winget.exe' failed to run: The process has no package identityAt line:1 char:1

[erelado]

Brief description of your issue

To clean my computer, I ran a Windows format using the "Remove everything" option. The App Installer (Winget) command is no longer working since the initial bootup.

Program 'winget.exe' failed to run: The process has no package identityAt line:1 char:1
+ winget
+ ~~~~~~.
At line:1 char:1
+ winget
+ ~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

Steps to reproduce

1. PS> winget

2. Using #1370

3. PATH environment variables:

4. App execution aliases

5. Using PsExec I tried to download the latest release msixbundle v1.3.2091 and to install it using PowerShell command: Add-AppxPackage -Path "C:\Users\$USERPROFILE\Downloads\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle"

6. Read the troubleshooting

7. Get-AppxPackage microsoft.desktopappinstaller

Expected behavior

Winget should work, as expected

Actual behavior

cannot launch Winget

Environment

OS Name	Microsoft Windows 11 Home
Version	10.0.22621 Build 22621

[denelon]

It looks like it might just have happened after "OOBE". It takes about 15 minutes for the registration to be triggered on a "fresh install" of Windows 11. You could likely go to the Microsoft Store to check for an update of the "App Installer.

We are working on the requirements to be provisioned right at boot as well as a simple to follow command to force the registration to happen sooner.

[denelon]

Once it's correctly installed, the App Execution Alias for "winget" should show up in the list.

[erelado]

Once it's correctly installed, the App Execution Alias for "winget" should show up in the list.

It does appear as an alias, under Windows Package Manager Client. It is still an issue.

[JohnMcPMS]

Your step 5 shows trying to register the package from SYSTEM, which is not supported by Windows. Are you also trying to run winget from SYSTEM? If so, that is not supported either.

[erelado]

Your step 5 shows trying to register the package from SYSTEM, which is not supported by Windows. Are you also trying to run winget from SYSTEM? If so, that is not supported either.

I've tried launching it from multiple locations, including $env:USERPROFILE. The problem seems to be solved after I made yet another format after attempting it for too long. However, I have no idea what went wrong.