Change "WebView2 Manager" to app name in Windows 11 Task Manager (Tauri v2)

[wildhart]

I'm new to Tauri. I've seen a few posts on here [1] [#1849] and the net where people post screenshots of their Windows Task Manager, and it shows their app name instead of "WebView2 Manager". I've tried everything, but I just can't get this to work.

Here I've scaffolded a brand new app with npm create tauri-app@latest my-app -- --template vue-ts, then added build.shortDescription. Even after a full build and install, the app name isn't changed. But it seems that other apps, eg MS Teams and Search in this screenshot, can change the app name.

There is also this process, which from what I understand is the Tauri/Rust process.

Is this still possible on v2, on Windows 11?

[starkmarkus]

I think there are two different things being shown here.

The my-app2 process is the actual Tauri/Rust application process, and that one should use your app metadata/name.

The WebView2 Manager entries are child processes created by the Microsoft Edge WebView2 runtime. Those are not normal Tauri processes that directly use shortDescription, so changing build.shortDescription is unlikely to rename them in Task Manager.

From what I understand, Windows Task Manager sometimes groups WebView2 child processes under the parent app name, but that behavior depends on how Windows/WebView2 attributes the child process to the host app. Apps like Teams may also use additional WebView2/Windows integration that a default Tauri app does not expose in the same way.

So I would not expect shortDescription to control this. That field is more about package/installer metadata, not the display name of the WebView2 runtime child processes.

The useful question for Tauri v2 is probably whether Tauri currently exposes any Windows/WebView2 setting that influences Task Manager process attribution/group naming. If not, this may simply be a platform/runtime limitation rather than a missing config value.

So my read is:

• the main Tauri process can be named after the app
• WebView2 child processes may still appear as WebView2 Manager
• shortDescription is probably not the knob for this
• if Windows 11 Task Manager grouping can be influenced, it would likely need a Tauri/WebView2 integration change rather than a bundle metadata change

[starkmarkus]

Thanks for opening the issue and for linking the discussion there.

For future readers, I think the current conclusion is:

• build.shortDescription / bundle metadata does not appear to control the WebView2 Manager child-process group name in Windows Task Manager.
• The main Tauri/Rust process can use the app metadata/name.
• If the WebView2 child-process group name can be influenced on Windows 11, it likely needs a Tauri/WebView2 integration change rather than a normal app metadata setting.
• The follow-up issue is here: [bug] Tauri v2 not able to change "WebView2 Manager" group name in Windows 11 Task Manager: #15567

If that matches your understanding too, marking this discussion as answered would make the conclusion easier for others to find.