Skip to content

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

Open
Open
[Problem/Bug]: Mouse cursor stays invisible if it was invisible when the WebView is closed#5687
Assignees
navneetrathi-msft
Labels
bugSomething isn't workingregressionSomething used to work but doesn't anymore

Description

@manuel-p-beko
Manuel (manuel-p-beko)
opened on Sep 2, 2026

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

Activity

  1. Manuel (manuel-p-beko)
    added
    bugSomething isn't working
    on Sep 2, 2026
  2. github-actions
    added
    regressionSomething used to work but doesn't anymore
    on Sep 2, 2026
  3. github-actions
    assigned
    Ambika Kunnath (ambikakunnath)
    on Sep 2, 2026

  4. chetanpandey1266 commented on Sep 2, 2026

    @chetanpandey1266
    Chetan Pandey (chetanpandey1266)
    on Sep 2, 2026
    Contributor
    no.repro.video.mp4

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

  5. manuel-p-beko commented on Sep 2, 2026

    @manuel-p-beko
    Manuel (manuel-p-beko)
    on Sep 2, 2026
    Author

    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.

  6. chetanpandey1266 commented on Sep 2, 2026

    @chetanpandey1266
    Chetan Pandey (chetanpandey1266)
    on Sep 2, 2026
    Contributor

    yeah I'm able to repro now.

  7. andr8928 commented on Sep 3, 2026

    @andr8928
    andr8928
    on Sep 3, 2026

    Also running into this today in my product

  8. TestMV123 commented on Sep 3, 2026

    @TestMV123
    Test (TestMV123)
    on Sep 3, 2026

    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.

  9. bzuillsmith commented on Sep 4, 2026

    @bzuillsmith
    Ben Zuill-Smith (bzuillsmith)
    on Sep 4, 2026

    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.

  10. navneetrathi-msft
    assigned
    navneetrathi-msft
    and unassigned
    Ambika Kunnath (ambikakunnath)
    on Sep 4, 2026

  11. navneetrathi-msft commented on Sep 4, 2026

    @navneetrathi-msft
    navneetrathi-msft
    on Sep 4, 2026

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

  12. mamoreau-devolutions commented on Sep 4, 2026

    @mamoreau-devolutions
    Marc-André Moreau (mamoreau-devolutions)
    on Sep 4, 2026

    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.

  13. andr8928 commented on Sep 4, 2026

    @andr8928
    andr8928
    on Sep 4, 2026

    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.

  14. tedphillips commented on Sep 11, 2026

    @tedphillips
    Ted Phillips (tedphillips)
    on Sep 11, 2026

    updates on fix expectation would be appreciated. (even if it was something like the rollout of 152 had been stopped)

  15. 14 remaining items

  16. bzuillsmith commented on Oct 11, 2026

    @bzuillsmith
    Ben Zuill-Smith (bzuillsmith)
    on Oct 11, 2026

    I checked one of my machines and Edge is on version 155, but the files at C:\Program Files (x86)\Microsoft\EdgeWebView\Application for working with .NET still show only the 154 folder. When are these files supposed to be updated? The issue cannot be resolved until they updated.

  17. navneetrathi-msft commented on Oct 12, 2026

    @navneetrathi-msft
    navneetrathi-msft
    on Oct 12, 2026

    You should be getting the update in a day or two. Updates are rolling out to everyone.

  18. nraju-athenahealth commented on Oct 12, 2026

    @nraju-athenahealth
    nraju-ah (nraju-athenahealth)
    on Oct 12, 2026

    Upgraded WebView2 from Fixed version 153 to 155.0.4283.45 (our application built on .NET 4.8, WPF, some legacy code uses VC++, MFC) but found that issue is not fixed.
    When can we expect the issue to be fixed? also, will there be a patched version of 155 or we need to wait for version 156.

  19. navneetrathi-msft commented on Oct 12, 2026

    @navneetrathi-msft
    navneetrathi-msft
    on Oct 12, 2026

    nraju-ah (@nraju-athenahealth) can you please share a repro for the same?
    Thanks.

  20. hefjo commented on Oct 12, 2026

    @hefjo
    hefjo
    on Oct 12, 2026

    navneetrathi-msft: Just to clarify, it is the EdgeWebView folder that needs to be 155?

    Current versions in our environment is:

    C:\Program Files (x86)\Microsoft\Edge\Application\155.0.4283.45
    C:\Program Files (x86)\Microsoft\EdgeWebView\Application\154.0.4258.62

  21. navneetrathi-msft commented on Oct 13, 2026

    @navneetrathi-msft
    navneetrathi-msft
    on Oct 13, 2026

    Yes. EdgeWebview should be at 155. You should be getting it ina day or two.

  22. nraju-athenahealth commented on Oct 13, 2026

    @nraju-athenahealth
    nraju-ah (nraju-athenahealth)
    on Oct 13, 2026

    25. nraju-ah (@nraju-athenahealth) can you please share a repro for the same?
    Thanks.

    Please find the attached sample application to repro the issue, follow the instructions given below,
    WebView2v155.zip

    1. Extract WebView2v155.zip file
    2. Download Microsoft.WebView2.FixedVersionRuntime.155.0.4283.45.x86.cab file and copy the file to WebView2Cab folder inside extracted folder
    3. Run PowerShell script file Setup-Runtime.ps1
      \WebView2v155> PowerShell -F Setup-Runtime.ps1 -ExecutionPolicy bypass
    4. Open WebView2MouseCursorBug.sln in Visual Studio
    5. Build with platform = x86
    6. Run the application
    7. Follow the on-screen repro steps to trigger the mouse pointer disappear bug

    Thanks

  23. bzuillsmith commented on Oct 14, 2026

    @bzuillsmith
    Ben Zuill-Smith (bzuillsmith)
    on Oct 14, 2026

    155 finally updated for us and the problem seems to be resolved in our case. Thank you.

  24. GunnarWoje commented on Oct 16, 2026

    @GunnarWoje
    GunnarWoje
    on Oct 16, 2026

    Hi,

    We would like to ask for this issue to be reopened and investigated further.

    Our users are still reporting that the mouse pointer becomes invisible in our application, even after updating to Microsoft Edge v155. This is the same behavior described in this issue, so it does not appear to have been resolved by the fix referenced when the issue was closed.

  25. navneetrathi-msft commented on Oct 16, 2026

    @navneetrathi-msft
    navneetrathi-msft
    on Oct 16, 2026

    GunnarWoje can you confirm the WV2 version and not Edge version? Both can be different in their system.
    Thanks.

  26. GunnarWoje commented on Oct 16, 2026

    @GunnarWoje
    GunnarWoje
    on Oct 16, 2026

    The WebView2 version we use is 1.0.3065.39, and we ship this version with our software. We've used it without any problems until the invisible cursor issue appeared with Edge 152.

  27. Michal456578 commented on Oct 17, 2026

    @Michal456578
    Michal456578
    on Oct 17, 2026

    confirm that 155.0.4283.60 has not fixed the problem.

    Summary

    in app I have a winform with webview2, it shows a search page, called from the main. When I type without moving the mouse and the clse the window without moving the mouse the issue presents.

    SDK Version

    1.0.3967.48 (Microsoft.Web.WebView2 NuGet package)

    Framework

    WinForms (.NET Framework 4.8)

    Operating System

    Windows 11

    OS Version

    10.0.22631.6199

    Repro steps

    Setup:

    • Windows "Hide pointer while typing" is on (Mouse settings > Additional mouse settings > Pointer Options).
    • One WinForms process with one UI thread. All WebView2 controls share one CoreWebView2Environment and one user data folder.
    • The main form hosts WebView2 controls that stay alive throughout.
    • A second, modeless form hosts a WebView2 showing a page with a text input.

    Steps:

    1. Open the second form, click in the text input, then leave the mouse still with the pointer over the page.
    2. Type a few characters. The pointer hides, as expected.
    3. Without moving the mouse, close the second form with Alt+F4.
    4. Move the mouse over the main form.

    Expected: the pointer is visible over the main form once the mouse moves.
    Actual: the pointer is invisible over the app's windows, while visible over the taskbar and other apps. Clicks still work. Restarting the app restores it.

    Our users hit the same fault in a second sequence: the user types into a form inside a WebView2 on the main form and submits it, and the app sets that control's Visible to False when the next navigation starts. The pointer then stays hidden over the whole app in the same way.

    Workaround

    Passing --disable-features=HideCursorWhileTyping as an additional browser argument (we set WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS for the process before any environment is created) stops the pointer hiding while typing, and the repro above no longer occurs on 155.0.4283.60. Turning off the Windows setting is also reported to work in #5708. Advising users to dismiss the window using the mouse is advisable - regretfully.

    Possible cause

    The symptom fits the Win32 cursor display count being left below zero for the host's UI thread: the pointer is hidden only over the app's own windows, and nothing in the app brings it back. Chromium main's DesktopWindowTreeHostWin::OnCursorVisibilityChangedNative now skips ::ShowCursor() when HideCursorWhileTyping is enabled, with a comment that the thread-global display counter makes same-thread windows inherit a hidden cursor. That change may not be in 155.0.4283.60.

  28. navneetrathi-msft
    reopened this on Oct 19, 2026

  29. navneetrathi-msft commented on Oct 19, 2026

    @navneetrathi-msft
    navneetrathi-msft
    on Oct 19, 2026

    I have re-opened the issue, let me investigate it further.
    Thanks.

  30. hefjo commented on Oct 19, 2026

    @hefjo
    hefjo
    on Oct 19, 2026

    Just for the record, we can confirm that we still see the issue on WebView version 155.0.4283.45.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingregressionSomething used to work but doesn't anymore

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions