We support three methods:
- Automatic detection of the default Edge version (installed through Windows updates)
- Evergreen runtime (separate installer - bootstrap available)
- BETA, DEV & CANARY builds (non-stable) (separate installer)
All three methods require the DLLs to be shipped. more info can be found at
According to the first post, you were using option 1) of the above three options. The issue we detected yesterday is that the copy instruction of the default Edge Chromium version had issues. A solution to this is to remove the Microsoft Edge folder with the specific version number from the Windows temp directory on your system, or the system of the user and then restart the application. The alternative option of installing the Evergreen runtime is a better option on the long run. When the runtime is detected, option 1) is skipped, at it no longers copies the default stable version from the system the application is running on.
Microsoft documentation states that (for now) the evergreen runtime installer option 2) is required in order to successfully run applications. To offer a better "out-of-the-box solution" to our customers, we implemented a manual copy.
The following link explains what is needed to use option 2).
When reading through the documentation, you will also note that Microsoft plans on shipping the runtime with Windows, which means that we should no longer have to install a runtime ourselves. When that is going to happen is unclear. It also mentions what you need to do in order to detect if Edge Chromium is available on the system or not (see chapters "Online" & "Offline").