brave-browser: x86 Windows machines are not updating

Description

Updates are currently failing on x86 machines. I initially ran into the issue when we were releasing 0.56.14 but no one else had x86 machines that could double check if I was the only one receiving this issue on my VM’s. @GeetaSarvadnya mentioned that she also ran into the issue once on her x64 machine so we thought it was an intermittent issue. However, getting reports from reddit that x86 users are not getting new updates:

https://www.reddit.com/r/brave_browser/comments/9ywwpb/brave_version_05614_now_available_on_release/ea8p9jv

When attempting to update my Win x86 machine, I’m getting the following error under brave://settings/help:

An error occurred while checking for updates: The installer encountered error 255. (error code 7: 0x80040902: 255 -- system level).

Steps to Reproduce

  1. launch a Win x86 VM and install https://github.com/brave/brave-browser/releases/download/v0.56.14/BraveBrowserStandaloneSetup32.exe
  2. once installed, attempt to update Brave via brave://settings/help

Actual result:

When attempting to update an x86 machine, you’ll get the following error and Brave won’t upgrade:

An error occurred while checking for updates: The installer encountered error 255. (error code 7: 0x80040902: 255 -- system level).

Expected result:

x86 machines should be updating to the latest version without any issues.

Reproduces how often:

100% reproducible using the above STR.

Brave version (brave://version info)

Brave 0.56.15 Chromium: 70.0.3538.110 (Official Build) (32-bit)
Revision ca97ba107095b2a88cf04f9135463301e685cbb0-refs/branch-heads/3538@{#1094}
OS Windows
Brave 0.56.14 Chromium: 70.0.3538.102 (Official Build) (32-bit)
Revision 4bbeebac88fdc09c97265e47c205868bbd190497-refs/branch-heads/3538@{#1077}
OS Windows

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?

I’m not 100% sure if the other channels are available as there’s no standalone installers for the previous versions

Additional Information

  • Win 10 x86 - Reproduced
  • Win 8.1 x86 - Reproduced
  • Win 7 x86 - Reproduced

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 22 (15 by maintainers)

Most upvoted comments

Yep, I also can reproduce this with released standalone installer and update trying… (So it’s weird why manually built standalone and update trying works fine). Anyway, I’ll take a look more.

I think the main problem is the update fail on first update trying. Because of that fail, I assume -full isn’t removed from ap. It should be reverted to x86-rel when install completed. But, it wasn’t in our case.(still x86-rel-full) I think not reverted ap caused up to date problem.

So, I think up to date problem would be disappeared after fixing update fail on first trying.