Installation blocked by AppLocker #8077

Closed
opened 2026-01-31 01:20:10 +00:00 by claunia · 6 comments
Owner

Originally created by @jasonnutter on GitHub (May 11, 2020).

Environment

Windows build number: 10.0.19041.263 (internal MSFT ring)
Windows Terminal version (if applicable): 0.11.1251.0

Any other software?

Steps to reproduce

When I started work today, Microsoft Terminal would simply not open, so I decided to uninstall and reinstall. When attempting to install via the msixbundle, installation failed with the following error:

Annotation 2020-05-11 103856

App installation failed with error message: error 0xD0E90002: Deployment of package Microsoft.WindowsTerminal_0.11.1251.0_x64__8wekyb3d8bbwe was blocked by AppLocker. (0xd0e90002)

Installing via the Windows Store results in this error:

Annotation 2020-05-11 104554

Expected behavior

Installation completes successfully.

Actual behavior

Unable to install via msixbundle on Github or via Microsoft Store app.

Originally created by @jasonnutter on GitHub (May 11, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19041.263 (internal MSFT ring) Windows Terminal version (if applicable): 0.11.1251.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> When I started work today, Microsoft Terminal would simply not open, so I decided to uninstall and reinstall. When attempting to install via the [msixbundle](https://github.com/microsoft/terminal/releases/download/v0.11.1251.0/Microsoft.WindowsTerminal_0.11.1251.0_8wekyb3d8bbwe.msixbundle), installation failed with the following error: <img width="489" alt="Annotation 2020-05-11 103856" src="https://user-images.githubusercontent.com/443409/81593568-81b78980-9374-11ea-8aa2-b9519fff87e4.png"> > App installation failed with error message: error 0xD0E90002: Deployment of package Microsoft.WindowsTerminal_0.11.1251.0_x64__8wekyb3d8bbwe was blocked by AppLocker. (0xd0e90002) Installing via the Windows Store results in this error: <img width="405" alt="Annotation 2020-05-11 104554" src="https://user-images.githubusercontent.com/443409/81593833-da872200-9374-11ea-978a-6c2bf96614dc.png"> # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Installation completes successfully. # Actual behavior <!-- What's actually happening? --> Unable to install via msixbundle on Github or via Microsoft Store app.
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixTracking-External labels 2026-01-31 01:20:10 +00:00
Author
Owner

@zadjii-msft commented on GitHub (May 11, 2020):

Oh I hit this this morning too. There's a bug that's going around the tree, see MSFT:26335608. There's a workaround in that work item. Fortunately, this should only be an internal bug 🤞

@zadjii-msft commented on GitHub (May 11, 2020): Oh I hit this this morning too. There's a bug that's going around the tree, see MSFT:26335608. There's a workaround in that work item. Fortunately, this _should_ only be an internal bug 🤞
Author
Owner

@jasonnutter commented on GitHub (May 11, 2020):

@zadjii-msft Great, thanks for the info! I was unable to reproduce the failed installation on my personal Windows 10 machine, so seems like it may be internal only.

@jasonnutter commented on GitHub (May 11, 2020): @zadjii-msft Great, thanks for the info! I was unable to reproduce the failed installation on my personal Windows 10 machine, so seems like it may be internal only.
Author
Owner

@jasonnutter commented on GitHub (May 11, 2020):

Workaround linked above appears to have fixed it, thanks again!

@jasonnutter commented on GitHub (May 11, 2020): Workaround linked above appears to have fixed it, thanks again!
Author
Owner

@abhi-msft commented on GitHub (May 15, 2020):

We are seeing the same issue with one of our apps. Do you mind sharing the resolution/workaround?

@abhi-msft commented on GitHub (May 15, 2020): We are seeing the same issue with one of our apps. Do you mind sharing the resolution/workaround?
Author
Owner

@DHowett-MSFT commented on GitHub (May 16, 2020):

(Handling offline.)

@DHowett-MSFT commented on GitHub (May 16, 2020): (Handling offline.)
Author
Owner

@Ar5ham commented on GitHub (May 20, 2020):

I am hitting this issue as well and the workaround mentioned above doesn't seem to apply in my case. I don't have anything under the directory mentioned in the bug above. I think there are multiple issues (or different variation of the same issue) causing the same error message here.

@Ar5ham commented on GitHub (May 20, 2020): I am hitting this issue as well and the workaround mentioned above doesn't seem to apply in my case. I don't have anything under the directory mentioned in the bug above. I think there are multiple issues (or different variation of the same issue) causing the same error message here.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8077