MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: We are facing an issue in webview2 while opening the side panel from the compose window from outlook

Open
#5,548 3 comments 0 reactions 1 assignee View on GitHub

@ambikakunnath is already working on this.

Since Mar 26, 2026.

bug regression
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

We are using the outlook com add-in from last 4 years we didn't change any code, after updating the webview2 version we are facing the issue (compose window side panel is opening as black page).

webview Old Version - 136.X.XXX.XX (While using this version the side panel of compose window has opened correctly, we didn't face any issue in the old version)
webview New Version - 137.X.XXX.XX (While using this version the side panel of compose window is not loaded it is showing the Blank screen)
Below is the exception we are facing while running the outlook com add-in.

[class]:<InitializeWebView2Async>d__2 [method]:MoveNext [message]:The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F) [Stack]: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.Web.WebView2.Core.CoreWebView2Environment.<CreateCoreWebView2ControllerAsync>d__15.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.WebView2.WinForms.WebView2.<InitCoreWebView2Async>d__25.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.GetResult() at PrismSTOutlookAddin.SidePanel2.<InitializeWebView2Async>d__2.MoveNext()

Sample code we are using for com add-in:

public string APPDATA_FOLDER_WEBVIEW_PATH = Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) + @"\Datazoic"; var env = await CoreWebView2Environment.CreateAsync(null, Globals.ThisAddIn.APPDATA_FOLDER_WEBVIEW_PATH,); - **This is the line we are getting above exception.** await this.webBrowser2.EnsureCoreWebView2Async(); this.webBrowser2.CoreWebView2.Navigate(Globals.ThisAddIn.baseURL + "outlook_smartsend.html?rnum=" + DateTime.Now.Ticks.ToString());

More information regarding the issue.
We are opening side panel from inbox and compose window. While opening outlook inbox side panel opens correctly and no issues. After that when we open compose window then open side panel the above exception is throwing. Previously same set of code working on older version of webview2 runtime, but after upgrade webview 2 runtime from (136.X.XXX.XX) to (137.X.XXX.XX) side panel is not opening in compose window. This is more important issue bcoz we have lot of clients are using this plugin and they start compiling last 2 week frequently after updated webview2 runtime. Please take this immediate solution and make sure new upgrade should not break any existing functionality.
APPDATA_FOLDER_WEBVIEW_PATH this is the directory we are using for both side panel.

Image
Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

.net V4.7.2

SDK Version

No response

Framework

----Please select----

Operating System

Windows 11

OS Version

No response

Repro steps
  1. Com add-in plugin opening side panel from inbox and compose window.
  2. After updating the webview2 runtime version open the outlook inbox side panel is opening.
  3. Then go to compose window open side panel the page is not loading it is showing blank
Repros in Edge Browser

Yes, issue can be reproduced in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

136.X.XXX.XX

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.