Failed to remove the MSIX package

[Morrigan-Ship]

Windows Version

26217

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Distro Version

ubuntu

Actual Behavior

WSL also cannot be started
and cannot be reinstalled

when try to reinstall wsl via wsl releases in github
i downloaded x64 msi version 2.2.4

Failed to remove the MSIX package (error: The deployment operation was blocked because Special profile deployment is not allowed. Please try logging into an account that is not a Special profile. You can try logging out and logging back into the current account, or try logging into a different account. ).

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• WSL 2 update error 0x80070643, WSL 2 cannot be deleted (#7287), similarity score: 0.73
• wsl.2.1.3.0.x64.msi package does not install or update windows Subsystem for Linux. (#11190), similarity score: 0.72
• WSL uninstall error (#7256), similarity score: 0.71
• Can't update WSL2 (#10527), similarity score: 0.71
• Cannot install latest WSL version from Microsoft Store or Github repo (#10640), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Morrigan-Ship]

WslLogs-2024-06-06_19-38-08.zip
This is log file of WSL

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Detected appx version: 2.2.4.0
Found no WSL traces in the logs

[Morrigan-Ship]

The log file doesn't contain any WSL traces

:/

[OneBlue]

Thank you @Morrigan-Ship. Just to double check, do you see the same issue with the 2.1.5 MSI ?

Also, which type of Windows user account are you using for this ?

[Morrigan-Ship]

Also, which type of Windows user account are you using for this

no its normal and default profile windows

I researched this issue and found that Windows in the background has changed my Windows user type from local to temporary for reasons I don't know.
This happened automatically by Windows
And this incident caused all uwp programs to crash
The solution should probably be changed from the registry from this path under the values ​​of flags, state

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

I tested it and it didn't work, but there are several types of user profiles in Windows:
temporary profile
special profile
roaming profile
mandatory profile
system profile that can be set via flags in the registry
Default User Profile

you can search:
https://www.google.com/search?q=windows+problem+%22special+profile%22+temporary

also you can read this topic feedback that i was created, and microsoft never fixed it :/

https://feedbackportal.microsoft.com/feedback/idea/b32e1a59-4015-ef11-989a-6045bd796e5a

system properties > Advanced > User Profiles > when i click on User Profiles button it will take many time to start new windows form about it and when it open:
User Status is: Temporary

Another evidence that proves that I am right is this:

[Morrigan-Ship]

Just to double check, do you see the same issue with the 2.1.5 MSI

same error

[zcobol]

@Morrigan-Ship in an elevated shell run Remove-AppxPackage --AllUsers --Package your_package_name and force uninstalling the MSIX for all users.

[Morrigan-Ship]

Remove-AppxPackage --AllUsers --Package your_package_name

command runned as Administrator:
Remove-AppxPackage -AllUsers -Package MicrosoftCorporationII.WindowsSubsystemForLinux_2.2.4.0_x64__8wekyb3d8bbwe

error:

Remove-AppxPackage : The deployment operation was blocked because Special profile deployment is not allowed. Please try logging into an account that is not a Special profile. You can try
logging out and logging back into the current account, or try logging into a different account.
The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy.
At line:1 char:1
 Remove-AppxPackage -AllUsers -Package MicrosoftCorporationII.WindowsS ...
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Remove-AppxPackage], COMException
    + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.Windows.Appx.PackageManager.Commands.RemoveAppxPackageCommand

[Morrigan-Ship]

wsl wslinfo --wsl-version
The specified user does not have a valid profile.

[elsaco]

Open the Group Policy editor (gpedit.msc) and check Allow deployment in special profiles setting:

[Morrigan-Ship]

Open the Group Policy editor (gpedit.msc) and check Allow deployment in special profiles setting:

not fixed !
i was report this problem last month to microsoft.
its windows core problem.

[johannesprinz]

Workaround:
Run your commands from a Command Prompt or Windows PowerShell terminal. For me wsl --uninstall Ubuntu-24.04 was failing from a PowerShell Core terminal but works from the other two. I got the hint of the issue when adding the --force flag which lead me to this post and thank you @Morrigan-Ship on your comment. Made me try the same command from another shell. Defo a PowerShell core issue!.

[Morrigan-Ship]

Workaround:
Run your commands from a Command Prompt or Windows PowerShell terminal

its not related to WSL
this problem is 'Windows User State'
its special temporary problem its a bug that changed my user state
i changed my password and restart and fixed

when user in special mode or temporary mode or state no uwp apps will not work even Settings.
WSL is an UWP app