[Problem/Bug]: Controller creation fails with 8000FFFF (catastrophic failure) on process with UI Access flag enabled

[mhdshameel]

What happened?

What happened? Webview2 controller creation stopped working after Windows 11 upgrade in one machine. HRESULT is 8000FFFF (catastrophic failure). From procmon I can see the webview child processes getting crashed. Issue started occurring after updated from 23H2 to 24H2. Note without the UI Access flag webview is working fine. I have attached the crash dumps of the webview process here as well.

dump file.zip

Managed to reproduce the issue with the webview sample as well. Pls see repro steps for details.

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

134.0.3124.51

SDK Version

1.0.2088.41

Framework

Win32

Operating System

Windows 11

OS Version

26120.3380

Repro steps

1. Set UI Access on a user token
2. Use the token to CreateProcess on the Win32_GettingStarted sample

Attached the code which I used on the getting started sample here: WVAppLauncher.zip

Note: the launcher has to be run with LocalSystem to be able to set UI Access.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

No response

[github-actions[bot]]

Hi, @mhdshameel!

It seems that your issue contains the word "crash". If you have not already, could you attach a crash dump as a comment?

WV2 crash dumps are located in a subfolder of the app's user data folder (UDF): <UDF>\EBWebView\Crashpad\reports\. By default, the user data folder is created in the app's folder with a name like <App Exe Name>.exe.WebView2. Refer to Crash Diagnostics for more information.

Thank you for your cooperation!

[mhdshameel]

Note: Issue regressed after Windows 11 updated from 23H2 to 24H2.

Dump files are already attached above

[mhdshameel]

Hi, any updates on this issue?

[ambikakunnath]

The issue is tracked via internal bug

[Bernie-Mason]

Hey all, our company is also experiencing this issue on Win 11.

I reported the same problem on Win 10 last year in this report. This was eventually fixed this update. Update KB50446613.

Our configuration is

• WPF Windows desktop app with a webview2 component
• UI access enabled
• Signed and installed in Program files

We also observe that if the application is run by an administrator then there is no issue with the webview2 component. Only when run by an non-administrative user do we observe the bug. An interesting note from the Win 10 fix of this issue: "If you have the Procmon monitoring tool installed in your device, you will observe that the application runs with the wrong integrity level, Integrity:Low instead of the expected Integrity:Medium. You are less likely to encounter this issue if you are running the application as an administrator."

I also have a fork of the webview2samples app that demonstrates this with minimal changes. See my report above for STR.

Thank you for reporting @mhdshameel.

[Badhri]

This seems to be a regression in Windows. This is tracked internally and worked upon by the team. Updates will be shared here once the fix is made available. Thanks !