{"id":40224,"date":"2026-09-02T00:02:56","date_gmt":"2026-09-01T22:02:56","guid":{"rendered":"https:\/\/borncity.com\/win\/?p=40224"},"modified":"2026-09-01T23:22:38","modified_gmt":"2026-09-01T21:22:38","slug":"edge-webview2-runtime-build-152-0-4191-53-no-mouse-pointer-in-the-veeam-br-console-or-care-center","status":"publish","type":"post","link":"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\/","title":{"rendered":"Edge WebView2 Runtime (Build 152.0.4191.53): No mouse pointer in the Veeam B&R console or Care Center"},"content":{"rendered":"

\"Edge\"[German<\/a>]Microsoft provides the Edge WebView2 runtime for Windows, which is used by applications. A reader informed me that, since installing Build 152.0.4191.53, the mouse pointer is no longer displayed in the Veeam B&R console or in the \"Care Center\" used there. However, there is a workaround.<\/p>\n

<\/p>\n

Edge WebView2 Runtime (Build 152.0.4191.53)<\/h2>\n

\"\"The Microsoft Edge WebView2 Runtime is a Microsoft system component for Windows that enables desktop applications to display and execute web content (such as HTML, CSS, and JavaScript). It serves as a rendering engine (based on Microsoft Edge's Chromium technology) that allows programs to display web pages or web-based user interfaces directly within their own app interface.<\/p>\n

The Microsoft Edge WebView2 Runtime can be downloaded from this Microsoft page<\/a>. The Microsoft Edge WebView2 Runtime Version 152 Update for x64-based editions (Build 152.0.4191.53) has been available for download from the Microsoft Update Catalog since August 27, 2026<\/p>\n

A Reader reported mouse pointer issues<\/h2>\n

Blog reader Bernhard L. works as an IT administrator at Diakonie in Austria and contacted me via email on September 1, 2026, to report a problem. Since installing the \"Microsoft Edge-WebView2 Runtime Version 152 Update for x64 basierte Editionen (Build 152.0.4191.53)<\/em>\" the mouse pointer has stopped working in some applications at his company (e.g., Care-Center = care documentation for care of older people, Veeam Backup & Replication console, version 13.x).<\/p>\n

The mouse pointer simply isn't rendered and shown. Clicking still works, but interacting with GUI elements becomes a matter of chance, since you don't know whether, for example, a button will be selected without a mouse pointer.<\/p>\n

The reader notes that the Microsoft Edge WebView2 Runtime Version 151 Update for x64-based editions (Build 151.0.4129.107) was also installed on a Windows Server. The corresponding GPO, which is intended to ensure that veeam.backup.shell.exe<\/em> and carecenter.exe<\/em> are launched using the Edge WebView 2 Runtime version 151.0.4129.107, is indeed present on the servers but is consistently ignored. No matter what has been tried so far, the Microsoft Edge WebView 2 Runtime version 152.0.4191.53 is always launched.<\/p>\n

Bernhard wrote: \"It would be great if you could post about this issue on your blog. I'm sure there are other admins out there facing the same problem.<\/em>\"<\/p>\n

There is a workaround<\/h2>\n

In a follow-up email, Bernhard got back to us a few hours later and wrote: \"In case you're interested, we've now implemented the following workaround, which allowed us to restore the mouse pointer in Care Center and VBR.<\/em>\" The CAB file for Microsoft Edge WebView2 Runtime version 151 was extracted to this folder.<\/p>\n

c:\\temp\\webview151<\/pre>\n
Then, as shown in the following figure, the value of the relevant system variable, WEBVIEW2_BROWSER_EXECUTABLE_FOLDER, was set to the path of the folder.<\/p>\n
\"WebView2-Environment-Variable\"<\/p>\n
After that, the mouse pointer from the older Edge WebView2 Runtime 151 was visible again during rendering. Maybe this will help someone.<\/p>\n","protected":false},"excerpt":{"rendered":"
[German]Microsoft provides the Edge WebView2 runtime for Windows, which is used by applications. A reader informed me that, since installing Build 152.0.4191.53, the mouse pointer is no longer displayed in the Veeam B&R console or in the \"Care Center\" used … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[872,463],"tags":[320,47,3006],"class_list":["post-40224","post","type-post","status-publish","format-standard","hentry","category-browser","category-issue","tag-edge","tag-issue","tag-webview2"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40224","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=40224"}],"version-history":[{"count":2,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40224\/revisions"}],"predecessor-version":[{"id":40226,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40224\/revisions\/40226"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=40224"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=40224"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=40224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}