-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebView2 Control doesn't render on one machine. #2567
Comments
Are you still facing this issue? |
Thanks @victorhuangwq for catching up! |
I see, sorry that it's been a while. I'm wondering if there's anything specific / different about the machine that might be different your dev machine that might be a cause of this failure? |
It's hard to say because the affected machine belongs to an Audio-Video professional with all kinds of software and low-level drivers installed. On the other hand, all "usual user fixes," like reinstalling WebView, trying different versions, etc., didn't help. |
Description
I have an issue with a BlazorWebView app, hosted in a WinForms application on one particular machine. We already discussed several loops and did some WinDBG runs together with the MAUI team: See issue on the MAUI-Repo.
But it turned out, a basic Hello World app with just a WebView2 Control shows the same behavior.
When starting the app, the window containing the WebView control stays "system-grey". No exception, no error message. I already tried to install another WebView2 runtime, but no change.
The issue persists just on this one machine.
I wasn't able to see exceptions or issues using WinDBG that aren't there on my machine (where the sample works fine).
Version
SDK: 1.0.1245.22
Runtime: Evergreen installer - 103.0.1264.44
Framework: WinForms, .NET 6, self contained build
OS:
Repro Steps
Minimal WinForm / WebView 2 app.
Screenshots
![image](https://user-images.githubusercontent.com/9912606/176998459-a9412e95-8a1f-47e6-bf65-f590f29fc7dc.png)
Working sample (on my dev machine):
Failing:
![image](https://user-images.githubusercontent.com/9912606/176998489-14f5d12c-5715-4856-8f6c-bc11463bd132.png)
Additional context
WinDBG startup log (failing machine):
WinDBG startup log (working machine):
The text was updated successfully, but these errors were encountered: