-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The application has failed to start because its side-by-side configuration is incorrect #1444
Comments
You need to download Even though the zip file contains executable its not the one you need to run the browser. |
I gather there is no portable version then. So the zip file is there because...? |
The zip file is for debug symbols. There is no portable version available now but there is an issue open for creating portable version you can track it here (#694) |
OK, thanks. Just in my opinion having generically named zip among releases is misleading |
I totally agree with @comodoro on the naming. I also downloaded thinking this is a portable version. And the error does not make any sense either. |
Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
Yes
Description
Brave downladed as zip archive fails to start on my Windows 10 with the above error message
Steps to Reproduce
Actual result:
Error dialog The application has failed to start because its side-by-side configuration is incorrect is shown
Expected result:
Brave should start
Reproduces how often:
Easily reproduced
Brave version (chrome://version info)
Brave 0.56.2
Brave 0.55.11
Reproducible on current release:
Yes/Yes
Cannot find browser-laptop Windows zipped executable binary
Website problems only:
N/A
Additional Information
System event log:
No other applications behave this way on my system. To theorize, might this be a dependency issue fixable by installing some redistributable libraries? In any case, an average user should not have to do that
OS is Win10 Pro 1809 build 17763.1
The text was updated successfully, but these errors were encountered: