private async void CopieWebBitmap()
            MemoryStream ms = new MemoryStream();            
            await webBrowser1.CoreWebView2.CapturePreviewAsync(CoreWebView2CapturePreviewImageFormat.Jpeg, ms);            
            Global.xbrowserImage = new Bitmap(ms);
            ms.Close();
            ms.Dispose();
private void webBrowser1_CoreWebView2InitializationCompleted(object sender, Microsoft.Web.WebView2.Core.CoreWebView2InitializationCompletedEventArgs e)
            CopieWebBitmap();         
Screenshots
Additional context
AB#37874270
          
@Stumec Thanks for the bug report! Does this happen on the CapturePreviewAsync line or somewhere else in the provided code? I wonder if it's related to being called in InitializationCompleted... What happens if you move that call somewhere else, like in response to a button click or NavigationCompleted?
          
CopieWebBitmap is an async call that isn't being awaited, so the InitializationCompleted event is returning right away. If you had code that quickly spun up a WebView2 and then shut it down without waiting for CopieWebBitmap to complete, then that might be why you are seeing it. Do you have such code, or is the WebView2 control created and then kept around for a long time/past the screenshot capture?