Hi Helmut,
Very clear description. Highly appreciated. I'm just wondering about the situation shortly after boot time when there's no user context (potential) GPO settings available. Assuming only system/machine context at that time. Now, what if some component is trying to make use of WebView2 right before a user wants to login? Will WebView2 rely on the very same set of Windows Registry keys as MS Edge? Is there a different behavior regarding machine and user context? Looking into some WebView2 documentation and also Chromium Sources documentation I get some gut feeling about deprecated (or at least unsupported) command line switches and environment variables that might tweak proxy server discovery algorithms. So what is the recommended way to deal with proxy server and PAC script settings when using WebView2? Many thanks. :-)