[Problem/Bug]: Mouse cursor stays invisible if it was invisible when the WebView is closed

[manuel-p-beko]

What happened?

The update to runtime version 152 added a new feature to the WebView2. The Windows setting "Hide pointer while typing" is now supported. This is fine by itself, but there is a big problem:
If the window that contains the WebView2 control is closed while the mouse cursor is invisible, then the cursor will stay invisible for the whole application. Moving the mouse outside the application window shows the cursor, moving it inside hides it. The application is still fully functional, but it has an invisible cursor.
But it looks like this only happens if at least one other WebView2 control is active. If it was the only WebView2 control in the process, then the bug does not happen.

Edge 152 also added this "hide pointer" feature, but I can't reproduce the bug in Edge.

Here is a similar error report that I found: https://borncity.com/win/2026/09/02/edge-webview2-runtime-build-152-0-4191-53-no-mouse-pointer-in-the-veeam-br-console-or-care-center/
That doesn't specify that they close a windows while the cursor is invisible, so maybe there are more cases for when this bug happens.
I can confirm that the workaround mentioned there (forcing runtime version 151) also fixes the bug for me (because the cursor is never hidden while typing with runtim 151).

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

152.0.4191.53

SDK Version

1.0.4129.50 and 1.0.4191.47

Framework

WPF

Operating System

Windows 11

OS Version

26200.9106

Repro steps

1. Open an application that shows a WebView2 control.
2. Open a separate window in the application that also contains a WebView2 control.
3. Type something in the WebView2 control so that the cursor is hidden.
4. Close the window without moving the mouse - e.g. with Alt+F4.
   Important: Make sure that the mouse cursor stays outside the area of the WebView2 control from step 1. Entering that area will show it again.
5. Notice that the mouse cursor stays hidden in the whole application area.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

Runtime 151.0.4129.107

[chetanpandey1266]

no.repro.video.mp4

I can't repro it. Do you have a repro which you can share?

[manuel-p-beko]

I missed one point in my initial report: The mouse cursor is shown again when it enters the area of a WebView2 control. So you need to make sure that the WebView2 control in the background is not the full windows size, and is not below the area where the mouse cursor was last.
I've added this in the initial description repro steps.

Could you please try it again with this information? I can provide a sample if it still doesn't reproduce for you with that additional information.

[chetanpandey1266]

yeah I'm able to repro now.

[andr8928]

Also running into this today in my product

[TestMV123]

We are seeing the same behavior in a WPF application with WebView2 Runtime 152.0.4191.53, reported by both internal teams and enterprise customers since 9/2/2026. Customer impact is significant, and we'd appreciate an update on investigation status and ETA for a fix.

[bzuillsmith]

We've had dozens of frustrated and confused users because of this issue. We open a window with webview2 for initial sign-in to our desktop app. This version must have just started rolling out to users because we started getting reports 2 days ago. We only just now started to suspect WebView2 was the source of it.

[navneetrathi-msft]

We are working on this, will update once we have a fix.
Thank you for your patience.

[mamoreau-devolutions]

We're also hit by this hard at Devolutions in Remote Desktop Manager, we've already got over 20 customer cases related to this. Support has been chasing all kinds of red herrings before finding the latest WebView2 update is probably the cause. Please fix quickly, and in the meantime, I'm looking for quick workarounds, we need something to tell our customers.

[andr8928]

We're also hit by this hard at Devolutions in Remote Desktop Manager, we've already got over 20 customer cases related to this. Support has been chasing all kinds of red herrings before finding the latest WebView2 update is probably the cause. Please fix quickly, and in the meantime, I'm looking for quick workarounds, we need something to tell our customers.

One workaround is to disable "Hide pointer while typing" in Windows mouse settings.
Bluetooth & Devices -> Mouse -> Additional mouse settings -> Pointer Options

But it would be your clients that need to do it.
That will of course disable hiding the mouse in other situations on the OS though.