starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Default permissions (ACL) of "Microsoft.WindowsTerminal" folder in "WindowsApps". #17939

New Issue
Closed
opened 2026-01-31 05:59:04 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 05:59:04 +00:00
Owner
Copy Link

Originally created by @Fooughhy on GitHub (Jul 14, 2022).

Windows Terminal version

No response

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

Mess about with "WindowsApps" folder permissions without backing them up before...

Expected Behavior

No response

Actual Behavior

I would like to know if anyone could provide all the default permissions that the "%ProgramFiles%\WindowsApps" folder has, as well as the "Microsoft.WindowsTerminal" folders (I think there are two, right?). I have had an unbelievable amount of issues with Windows Store apps lately (started with only Xbox Games Pass games which stopped working), and as a final resort I tried to mess with the permissions of the folders to be able to check that the "AppxManifest.xml" was there (as there were errors indicating it wasn't, at some point at least). These issues have also prevented me from using RestorePoints which I had made once I actually got into a working state.

But now the Xbox Game Pass games are working, but for some reason there have been multiple UWP apps that doesn't work if they are started from the store (or from the context menu either, actually). And one of them is the Windows Terminal.

I received an error indicating that the "Parameter is incorrect" for "wt.exe". This led me to this thread, amd the answer by Gidsik telling me to run the command "cacls "%programfiles%\WindowsApps" /s:"D:PAI(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;OICIIO;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;OICIIO;GXGR;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;;FA;;;SY)(A;OICIIO;GA;;;SY)(A;CI;0x1200a9;;;BA)(A;OICI;0x1200a9;;;LS)(A;OICI;0x1200a9;;;NS)(A;OICI;0x1200a9;;;RC)(XA;;0x1200a9;;;BU;(Exists WIN://SYSAPPID))"" to set the correct permissions for the "WindowsApps" folder. But as that folder seems to work (other UWP apps work) I decided only to run it on the Terminal folders inside. This now means that I can't open the terminal at all anymore...

So if anyone could provide the ACLs that I can use to run that command again for the WindowsTerminal folder, that'd be hugely appreciated.

Originally created by @Fooughhy on GitHub (Jul 14, 2022). ### Windows Terminal version _No response_ ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce Mess about with "WindowsApps" folder permissions without backing them up before... ### Expected Behavior _No response_ ### Actual Behavior I would like to know if anyone could provide all the default permissions that the "%ProgramFiles%\WindowsApps" folder has, as well as the "Microsoft.WindowsTerminal" folders (I think there are two, right?). I have had an unbelievable amount of issues with Windows Store apps lately (started with only Xbox Games Pass games which stopped working), and as a final resort I tried to mess with the permissions of the folders to be able to check that the "AppxManifest.xml" was there (as there were errors indicating it wasn't, at some point at least). These issues have also prevented me from using RestorePoints which I had made once I actually got into a working state. But now the Xbox Game Pass games are working, but for some reason there have been multiple UWP apps that doesn't work if they are started from the store (or from the context menu either, actually). And one of them is the Windows Terminal. I received an error indicating that the "Parameter is incorrect" for "wt.exe". This led me to [this](https://superuser.com/questions/1288014/reset-default-acls-for-c-program-files-windowsapps) thread, amd the answer by [Gidsik](https://superuser.com/users/1659735/gidsik) telling me to run the command "cacls "%programfiles%\WindowsApps" /s:"D:PAI(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;OICIIO;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;;0x1200a9;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;OICIIO;GXGR;;;S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204)(A;;FA;;;SY)(A;OICIIO;GA;;;SY)(A;CI;0x1200a9;;;BA)(A;OICI;0x1200a9;;;LS)(A;OICI;0x1200a9;;;NS)(A;OICI;0x1200a9;;;RC)(XA;;0x1200a9;;;BU;(Exists WIN://SYSAPPID))"" to set the correct permissions for the "WindowsApps" folder. But as that folder seems to work (other UWP apps work) I decided only to run it on the Terminal folders inside. This now means that I can't open the terminal at all anymore... So if anyone could provide the ACLs that I can use to run that command again for the WindowsTerminal folder, that'd be hugely appreciated.
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 05:59:05 +00:00
claunia commented 2026-01-31 05:59:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 14, 2022):

Mess about with "WindowsApps" folder permissions without backing them up before

y tho

For real, that will fuck your machine up. Don't do that, and if there's something that suggested you do that, I'd love to reach out to the origin and find out WHY.

@zadjii-msft commented on GitHub (Jul 14, 2022): > Mess about with "WindowsApps" folder permissions without backing them up before _y tho_ For real, that will fuck your machine up. Don't do that, and if there's something that suggested you do that, I'd love to reach out to the origin and find out WHY.
claunia commented 2026-01-31 05:59:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 14, 2022):

@DHowett MIGHT have a way to repair this.

@zadjii-msft commented on GitHub (Jul 14, 2022): @DHowett MIGHT have a way to repair this.
claunia commented 2026-01-31 05:59:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 14, 2022):

Unfortunately, there's no general way to un-mess the permissions in that folder. It doesn't exactly have "default" permissions: everything inside is ACLed based on a bunch of different things[1].

There's one script which we do not recommend running on a production system, unless you have no other option called "Windows Apps Unf**er". I won't be providing a link to it.

The best and least destructive way to fix the permissions in that folder is honestly to do an in-place upgrade to the same version of Windows you already have. That is: if you're on "Windows 11 build 22000," grab an ISO file for that same exact build and perform an upgrade that "keeps personal files/settings and apps."

[1]: Packages can share files (they're deduplicated), so sometimes the ACLs for one package include another package's ID; there's this thing called "hosted runtimes"; some packages are hosted outside this folder but have permissions to let those outside applications access this folder, etc.

@DHowett commented on GitHub (Jul 14, 2022): Unfortunately, there's no general way to un-mess the permissions in that folder. It doesn't exactly have "default" permissions: everything inside is ACLed based on a _bunch_ of different things[1]. There's one script _which we do not recommend running on a production system, unless you have no other option_ called "Windows Apps Unf**er". I won't be providing a link to it. The _best and least destructive_ way to fix the permissions in that folder is honestly to do an in-place upgrade to the same version of Windows you already have. That is: if you're on "Windows 11 build 22000," grab an ISO file for that same **exact** build and perform an upgrade that "keeps personal files/settings and apps." [1]: Packages can share files (they're deduplicated), so sometimes the ACLs for one package include another package's ID; there's this thing called "hosted runtimes"; some packages are hosted outside this folder but have permissions to let those outside applications access this folder, etc.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17939
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?