there seem to be multiple subprocesses having different names, depending on type of installer and platform.the actual installation continues in background and takes some time to finish.the main setup.exe exits IMMEDIATELY, leaving no chance for the caller to wait for the finished webview2 installation.so the parent process can simply wait for main setup.exe to complete.the main setup.exe exits AFTER the installation is complete.check when the installer exits in cmd.exe.check with process explorer / task manager to see when the installation finishes.run the installer, XXX.exe /silent /install.start a cmd.exe, (admin or not -> same behaviour).start a VM/physical Windows 10 machine without any webview2 components installed.Public Installer Versions avaiable as of 01-June-2021 from If we manually install WebView2 to ensure the installation finishes before the Consuming Application (Outlook.exe) starts, then everything works fine. We do not want to deploy fixed versions along with our application since that would be too difficult/inappropriate. We must support Windows 7 to Windows 10, so we expect that we will always need to include WebView2 in our installer. Our Installer starts the WebView2 Consuming Application (Outlook.exe) immediately after the installation, causing Outlook.exe to have Access Violations and this even corrupts WebView2/Edge Data directories sometimes.
There is no easy way for a parent installer to correctly wait until the installation finishes. The WebView2 Installers (Bootstrapper+Standalone) exit too early, when run with /silent /install from another installer.
0 kommentar(er)
