-
Notifications
You must be signed in to change notification settings - Fork 54
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
Nothing displayed, but Right-Click works. Some computers only. #1539
Comments
Hey @TcNobo - thanks for the bug report! A couple of questions:
We are currently investigating similar bugs, so I'll link your issue to those investigations. Thanks! |
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. |
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. |
Thanks. Are there any known workarounds that I can use in the meanwhile? |
Unfortunately we haven't found workaround yet for folks who find themselves in this state. |
Have another user with the same exact issue. Same thing, also Intel HD Graphics:
|
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'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 |
@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: |
@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. |
@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: 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. |
Yes, they told me it was working before |
I'm working with a customer right now, i'm trying to find the error. I'll post it soon |
Here is the error that comes up when initializing WEbview2: |
I'm using the lastest version of webview2 production, it seems like the for some computer the webview2 runtime is not matching |
@champnic I had to downgrade webview2 from : 1.0.1185.39 to 1.0.1020.30 . Please let me if i'm suppose to download runtime from somewhere else or the runtime on this link needs to be updated it. Thanks Mark |
Thanks for digging in @markismail7 - sounds like this is a different issue than the main thread here (which has nothing getting displayed, but the WebView2 is loading fine). ICoreWebView2Controller2 is an old interface (1.5 yrs) supported by runtimes 89.0.774.45+. What runtime did the user have on their machine? In theory the evergreen runtime should be keeping itself up to date (though there is a group policy that IT admins can use to block updating). Did downgrading the SDK but keeping the same old runtime workaround the issue? |
@champnic |
Can you get version info of the SDK and Runtimes for machines where you are and aren't seeing this? |
I will get it. |
@champnic |
Just to confirm - that is the version combination that you are seeing it fail due to the ICoreWebView2Controller2? |
Yes, keep in mind. This only happens on certain computers. So it doesn't make any sense. Another thing i found out, if you have webview2 runtime older version installed, and you try to install the new version from https://developer.microsoft.com/en-us/microsoft-edge/webview2/ It will say, you already have webview2 installed. It doesn't force to update. You need to un install and re- install to have the latest version. I know it suppose to update automatically though. |
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
The text was updated successfully, but these errors were encountered: