WebView2 processes grouped separately from parent app in Windows 11 Task Manager

Description
When a WebView2-based application (e.g. Tauri v2) spawns a WebView2 environment, the child WebView2 processes (browser, GPU, renderer, network, storage, crashpad) appear as a separate "WebView2 Manager" process group in Windows 11 Task Manager, instead of being grouped under the parent application's process.

Expected behavior
WebView2 child processes should be grouped under the parent application in Task Manager, similar to how MS Teams correctly groups its WebView2 processes.

Actual behavior
The WebView2 processes appear as a standalone "WebView2 Manager" group, visually disconnected from the parent app (e.g. "WindOp") that spawned them.

Environment

• Windows 11 (Build 26200.8655)
• WebView2 Runtime: Evergreen (latest stable)
• Framework: Tauri v2.10.3 (uses wry crate for WebView2 integration)
• App: WindOp (com.windop.app)

Steps to reproduce

1. Build and run any Tauri v2 desktop application on Windows 11
2. Open Task Manager
3. Observe the WebView2 processes appear as a separate "WebView2 Manager" group, not under the app's process tree

Additional context

• This was first reported in the Tauri repository: https://github.com/tauri-apps/tauri/issues/15567
• Tauri core team member FabianLars confirmed: "this is not about renaming the processes (which we can't!) but rather about why the task manager does not group the processes together anymore"
• MS Teams (which also uses WebView2) correctly groups its processes under the Teams parent, suggesting the issue is in how the WebView2 environment is created/managed rather than a Windows limitation
• The app already calls SetCurrentProcessExplicitAppUserModelID for taskbar grouping, but this does not affect Task Manager process grouping
• No WebView2 API or configuration was found to control the process group display name in Task Manager

Screenshot
The Task Manager shows:

• Discord (6) — correctly grouped
• WebView2 Manager (6) — WindOp's WebView2 processes appear here as a separate group
• WindOp.exe should be the parent group containing all WebView2 child processes