Nothing displayed, but Right-Click works. Some computers only.

[TCNOco]

This project of mine, the TcNo Account Switcher is being plagued by an issue that affects... some people.
The WebView2 window works perfectly. A handful of computers display nothing but the form's background, even when the page is changed, and can be interacted with (Both elements on the page, and the Right-Click window for the Inspector).

It affects both Windows 7 - issue #45 and Windows 10 users. Windows 10 I can't link as they contacted via Discord, but it's been 2 or 3 users so far.
Nothing is different in the builds. They work, and on some computers, they don't. I can't recreate it, but I need to solve it.

I tried 'fixes' from #1077, in TCNOco/TcNo-Acc-Switcher@1c085ce. But they came to the same result. Not fixing anything.

Version
SDK: WebView2 1.0.864.35, WebView 2 1.0.902-prerelease. ASP.NET Core + Desktop Runtime 5.0.8.
Runtime: WebView2 Runtime 91.0.864.70 (Latest)
Framework: WinForms
OS: Windows 10 latest, Windows 7 latest.

Repro Steps
I have no steps as nothing is done differently on computers where it works, and where it doesn't. Some just don't display anything, some do. It should open up and display everything as normal, but for some, it just doesn't.

Screenshots
Expected:

Actual, on PCs affected by this bug:

Additional context
You're able to download it yourself, here. The installer installs all required runtimes, so nobody is missing anything causing this issue.

AB#34786782

[champnic]

Hey @TcNobo - thanks for the bug report! A couple of questions:

1. Are you setting the WebView2 to have a transparent background?
2. Is this happening when minimizing and then opening the app?
3. Are you able to find out what GPUs the affected machines are using?

We are currently investigating similar bugs, so I'll link your issue to those investigations. Thanks!

[TCNOco]

1. No.
2. Just when opening the program, and lasts throughout its life.
3. The 2 computers affected:

• Windows 10 Education x64 19042, Polish, Intel(R) HD Graphics 4000 - i5-3570. See Imgur album
• Windows 7 (Maximum?) x64 7601, Russian, Intel HD Graphics - Intel Pentium 2020M. See Can't install TCNOco/TcNo-Acc-Switcher#45 (comment)

I asked users for DXDiag screenshots, so that's what the links are for if you can pull any more useful info out of it.

[champnic]

Thanks for the info! I'm adding this bug to our backlog. We have some similar bugs on our backlog that we're working on and are related to DComp being disabled for certain GPUs, which seems to be the case for the Intel 4000 and OS < Win10.

[TCNOco]

Thanks. Are there any known workarounds that I can use in the meanwhile?

[champnic]

Unfortunately we haven't found workaround yet for folks who find themselves in this state.

[TCNOco]

Have another user with the same exact issue. Same thing, also Intel HD Graphics:

• Windows 7 Ultimate x64 7601, Turkish, Intel i5-4300M (Intel HD Graphics 4600). See Imgur album

[TCNOco]

For now I've worked around this by building in a 'fallback' CEFSharp version. Extra files are downloaded, and the program uses this instead of WebView2.
I much prefer the performance of WebView2 - and the Inspect Element functionality... I do hope this gets patched soon.

[markismail7]

I'm having the same problem with some of our customers. Webview2 won't work on certain computers, i even had the customer upgrade from windows 10 to windows 11 and still didn't fix it. It's 64 bit computer. I have seen this problem more than once now. We use the latest version of Webview2. I hope Microsoft takes care of it as we have no answer for our customers on why certain computers can't load webview2

[champnic]

@markismail7 These issues are tough to repro and track down, but in my experience they are most often tied to GPU driver issues. If you want to, you can try disabling the GPU workarounds that exist for some driver bugs. This is a tradeoff in that you may hit other graphical issues tied to drivers, but may avoid the content being invisible issue. To try this, add these to the browser arguments when initializing the WebView2:
--ignore-gpu-blocklist --disable-gpu-driver-bug-workarounds

[markismail7]

@champnic How do you answer everyone's question so fast. OMG. Microsoft give this person a raise. Thank you i'll try that. I really appreciate your help.

[markismail7]

@champnic
I haven't been able to solve the problem on certain computers where webview2 doesn't load. Its just white blank. However, they can load edge chrome. Can you please help, i have encountered over 50 customers for the past 30 days. Some of them have 2 computers, one can load webview2 the other can't load it.

[champnic]

Are you suddenly seeing a surge of this occurring?

For the machines that are hitting this, do the following browser arguments "fix" the issue and allow WebView2 to load? You can set the following environment variable of those machines and restart the WebView2/app:
WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--ignore-gpu-blocklist --disable-gpu-driver-bug-workarounds

If that fixes the issue, then that confirms that it's due to a gpu issue, and we'll want to gather some more information.