Add logic to catch failed app exec alias executions (#11765)
Blue committed
Jul 12, 2024 at 15:29 UTC
12a571d588b905f14aac3200251466ac07bb9522
1 file changed
+13
-2
triage/config.yml
+13
-2
@@ -99,6 +99,13 @@ rules:
99
field3: Wsl/CallMsi/REGDB_E_CLASSNOTREG
100
set: msix-bad-install-state
101
102
+ - logline:
103
+ provider: Microsoft.Windows.Subsystem.Lxss
104
+ task: LxssException
105
+ field1: 'onecore\vm\wsl\lxss\wslutil\liftedsupport.cpp'
106
+ field5: '0x80070002'
107
+ set: msix-bad-app-exec-alias-state
108
+
109
- logline:
110
provider: Microsoft-Windows-Hyper-V-Chipset
111
field1:
@@ -288,9 +295,13 @@ actions:
295
condition: msix-install-error
296
debug_message: 'Found evidence of MSIX install error: $error, adding msix tag'
297
tag: 'msix'
291
-
298
+
299
+ - when:
300
+ condition: msix-bad-app-exec-alias-state
301
+ debug_message: 'Found evidence of failed app execution alias execution in LiftedSupport'
302
+
303
- when:
293
- condition: msix-bad-install-state
304
+ condition: {or: [msix-bad-install-state, msix-bad-app-exec-alias-state]}
305
user_message: |
306
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?
307