Skip to content

Commit

Permalink
Add logic to catch failed app exec alias executions (#11765)
Browse files Browse the repository at this point in the history
  • Loading branch information
OneBlue authored Jul 12, 2024
1 parent 04c3377 commit 12a571d
Showing 1 changed file with 13 additions and 2 deletions.
15 changes: 13 additions & 2 deletions triage/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,13 @@ rules:
field3: Wsl/CallMsi/REGDB_E_CLASSNOTREG
set: msix-bad-install-state

- logline:
provider: Microsoft.Windows.Subsystem.Lxss
task: LxssException
field1: 'onecore\vm\wsl\lxss\wslutil\liftedsupport.cpp'
field5: '0x80070002'
set: msix-bad-app-exec-alias-state

- logline:
provider: Microsoft-Windows-Hyper-V-Chipset
field1:
Expand Down Expand Up @@ -288,9 +295,13 @@ actions:
condition: msix-install-error
debug_message: 'Found evidence of MSIX install error: $error, adding msix tag'
tag: 'msix'


- when:
condition: msix-bad-app-exec-alias-state
debug_message: 'Found evidence of failed app execution alias execution in LiftedSupport'

- when:
condition: msix-bad-install-state
condition: {or: [msix-bad-install-state, msix-bad-app-exec-alias-state]}
user_message: |
Your WSL installation appears to be in a bad state. Can you try running the following command to reinstall WSL (elevated powershell) and see if that solves the issue?
Expand Down

0 comments on commit 12a571d

Please sign in to comment.