

This is more than mysterious, because in my case it neither works with the repro app nor in our production software. Thanks again for the excellent support with this issue! I am currently running Windows 10 version 2004 build 19041.572, and we're not using any Windows jobs. NET version, but I assume that they work the same as the Win32 version? I'll see that I can try the additional parameters you mentioned, though we're using the.

You can find the relevant code for creating desktops here: Once the new desktop is activated, the runtime starts a new process, the client component (also a WPF application), which then runs on the new desktop and creates the WebView2. In SEB, we have the runtime component (which is a WPF application) which handles the creation, activation and closure of new desktops. After building and before executing, you'd need to copy the output of the WindowsFormsApp project into the output folder of the NewDesktopBug project. Excellent, thank you for investigating the issue, it means a lot to us! I have attached a simplified version I used to investigate the issue when I was trying to integrate WebView2 into our software: NewDesktopBug.zip.
