Problembericht für Microsoft (WebView2 + Access)

The missing Microsoft.Web.WebView2 registry entry is not Microsoft's documented test for whether the WebView2 Runtime is installed. Its deployment guidance checks the EdgeUpdate Clients version value or the supported runtime-version API instead. In Access, the supported feature is the built-in Edge Browser Control, added from a form's Controls group, not a control you establish by manually registering that ProgID. Microsoft's Access guidance lists Microsoft 365 build 16.0.16327.20214 or later, so your reported build is above that baseline. Test a blank database and form, open Layout View, and inspect the full Controls gallery for Edge Browser Control. Verify the installed Access product and runtime using those documented checks. Since repairs have already failed, provide Microsoft support with the build, bitness, product license, and blank-database result. The evidence does not establish a Store-versus-desktop runtime conflict, and forcing registry entries would not be a supported resolution.