Is there a new process hierarchy change after WebView2 runtime version 117.0*? #3848
-
|
Hello- We've been using WebView2 for a while now and after this most recent update, we've noticed that some of our functionality doesn't work. Previously the process hierarchy was rooted in the process that owned the WebView2 control which was very handy, here's a screenshot of what Outlook currently looks like: This is what we want to happen but instead, we're seeing WebView2 rooted in Explorer.exe. Is there any way to use the legacy process hierarchy? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
|
@lflores-ms could you take a look at this? |
Beta Was this translation helpful? Give feedback.
-
|
Hey @tamuseanmiller - It's possible this was due to a change to avoid a bug when DPI compatibility settings were causing launch failures when trying to parent the processes/HWNDs. Instead, the child processes get launched from explorer.exe. You could check if your parent process has a "__COMPAT_LAYER" environment variable set, which could indicate this is happening. I also believe we use explorer.exe as the parent process if the host app is running as admin, as we try to avoid running the WebView2 processes as admin for security. |
Beta Was this translation helpful? Give feedback.
-
|
We generally recommend using PerMonitorV2 DPI awareness. Is that something you can try for your app, if you are already PerMonitor? One of the listed changes between the 2 versions is automatic support for dialogs, which may be relevant to the issue you mentioned seeing: https://learn.microsoft.com/en-us/windows/win32/hidpi/high-dpi-desktop-application-development-on-windows |
Beta Was this translation helpful? Give feedback.
-
|
I assume that this means if we switch to using PerMonitor v2 then this won't interact with your DPI bug fix and we may see the process hierarchy we're looking for? |
Beta Was this translation helpful? Give feedback.
-
|
I believe you would also need to remove the HIGHDPIAWARE registry key value, though with PerMonitorV2 that shouldn't be necessary. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for all your help here, I think I have a possible fix now. We wouldn't have been able to figure this out without your help. Really appreciate it! |
Beta Was this translation helpful? Give feedback.
-
|
Great, glad to hear you have a path forwards! |
Beta Was this translation helpful? Give feedback.
Hey @tamuseanmiller - It's possible this was due to a change to avoid a bug when DPI compatibility settings were causing launch failures when trying to parent the processes/HWNDs. Instead, the child processes get launched from explorer.exe. You could check if your parent process has a "__COMPAT_LAYER" environment variable set, which could indicate this is happening. I also believe we use explorer.exe as the parent process if the host app is running as admin, as we try to avoid running the WebView2 processes as admin for security.