https://bugs.winehq.org/show_bug.cgi?id=48006
--- Comment #54 from Sophira wine-bugs@theblob.org --- I've done some testing with both wine-proton-7.0.5 and wine-vanilla-8.6 (the version of vanilla I was using before updating; see below). In both cases, the outcomes were the same; the webview always auto-installed regardless of whether the prefix was set to Windows 7 or Windows 10, but only in Windows 7 did the install succeed. In neither case did the launcher actually work after the install, however.
I've also installed wine-vanilla-10.4, but I'm getting some weirdness which I think is caused by the new wow64 feature - which is odd because I did not compile it with that feature - I'm using Gentoo, and the "wow64" USE flag is disabled. (Specifically, I'm seeing weirdnesses like the complete OS listing down to Windows 2.0 showing up in winecfg even for win64 prefixes, amongst other things that probably belong in another bug and not this one.) As such, I'm not sure that my experience with 10.4 will be valid.
That said, my experience with 10.4 is that the auto-install completes with both Windows versions, but what happens next differs based on whether I'm using a premade prefix from an earlier wine version, or a new prefix:
* If I'm using a premade, the launcher runs, but, as before, does not show the webview. * If I've made a new prefix from scratch with 10.4, the launcher is unable to load dxgi.dll from my DXVK install, and thus does not run at all. (If I uninstall DXVK, the launcher runs, but as with the premade, does not show the webview.)
I'm at a bit of a loss. I also can't explain why the webview did not auto-install for you. When you have the launcher running, do you see any 'C:\Program Files (x86)\Microsoft\EdgeWebView\Application\109.0.1518.140\msedgewebview2.exe' processes running at all?