Always crashes with 0xc0000022

[alancnet]

Environment

Windows build number: Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Windows Terminal version (if applicable): 1.6.10571.0

Any other software? WSL2

Steps to reproduce

1. Install Windows Terminal
2. Run Windows Terminal
   

Expected behavior

I am expecting Windows Terminal to launch

Actual behavior

Windows Terminal always fails with

---------------------------
wt.exe - Application Error
---------------------------
The application was unable to start correctly (0xc0000022). Click OK to close the application. 
---------------------------
OK   
---------------------------

This happens regardless of the version I install, or the method I use to install, including Microsoft Store, chocolatey, or Github Releases.
I've also cleared out my user settings to no avail.

[alancnet]

I continued to investigate this issue, and used Process Explorer to see what was going on. I got Access Denied on vcruntime140.dll in C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.6.10571.0_x64__8wekyb3d8bbwe. Notably, Users lacked the execution privilege, so I took ownership of the file (previously owned by SYSTEM) and added Full Control to users. This resolved the issue.. but it is still a mystery to me how this could happen.

[zadjii-msft]

@DHowett is this another one of those deployment issues we've been seeing?

Taking full permission of something in .../WindowsApps is probably not the best long term solution, but it's certainly weird that this was happening at all

[sungvzer]

I'd like to add that, while running WindowsTerminal.exe or wt.exe from explorer results in a failure, running it from the Search Bar or an already running instance of wt or pwsh makes it run properly.

If I try to edit my permissions in Explorer, I get an "Access control entry is corrupt" kind of error.

[DHowett]

This points to a permissions issue on WindowsApps itself -- not the Terminal directory.

Can you share the output of ...

icacls "\Program Files\WindowsApps"

?

From an admin shell, of course.

Mine are:

\Program Files\WindowsApps NT SERVICE\TrustedInstaller:(F)
                           NT SERVICE\TrustedInstaller:(OI)(CI)(IO)(F)
                           S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(RX)
                           S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(OI)(CI)(IO)(GR,GE)
                           NT AUTHORITY\SYSTEM:(F)
                           NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
                           BUILTIN\Administrators:(CI)(RX)
                           NT AUTHORITY\LOCAL SERVICE:(OI)(CI)(RX)
                           NT AUTHORITY\NETWORK SERVICE:(OI)(CI)(RX)
                           NT AUTHORITY\RESTRICTED:(OI)(CI)(RX)
                           BUILTIN\Users:(Rc,S,RD,REA,X,RA)

These are the expected permissions. Anything else somewhat contravenes expectations and can cause all sorts of app activation issues.

[sungvzer]

There it is!

C:\Program Files\WindowsApps\ NT SERVICE\TrustedInstaller:(F)
                              NT SERVICE\TrustedInstaller:(OI)(CI)(IO)(F)
                              S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(RX)
                              S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(OI)(CI)(IO)(RX)
                              NT AUTHORITY\SYSTEM:(F)
                              NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
                              BUILTIN\Administrators:(CI)(RX)
                              NT AUTHORITY\SERVIZIO LOCALE:(OI)(CI)(RX)
                              NT AUTHORITY\SERVIZIO DI RETE:(OI)(CI)(RX)
                              NT AUTHORITY\RESTRIZIONI:(OI)(CI)(RX)
                              BUILTIN\Users:(Rc,S,RD,REA,X,RA)
                              SALVIO\Salvio:(OI)(CI)(F)

[DHowett]

If you remove SALVIO\Salvio (icacls "C:\Program Files\WindowsApps" /remove SALVIO\Salvio), does the issue go away?

[DHowett]

I'm gonna close this one out in favor of /dup #9452 -- please follow up there with the permissions discussion. I'd love to know if that helps, because if it does we can put together a FAQ document.

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

[TheWhatis]

Just create file wte.bat (or other filename.bat), write in it
@echo off
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps\wt.exe
write a path your file in variable the PATH and open terminal from "run" with command wte (or other filename). ( Sorry for my English, I'm just starting to learn it XD )