MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: Controller creation fails with 8000FFFF (catastrophic failure) on process with UI Access flag enabled
@ambikakunnath is already working on this.
Since Mar 27, 2025.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
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.
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
- Set UI Access on a user token
- 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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.