Now getting this when I try to update Nightly, so I guess this means they are doing something on the update channel:
@paulri youâre right in that it finally got the update, but the number youâre seeing is wrong. Should be as mine just received (for Nightly):
Thanks for keeping us posted.
After reading your post, I went ahead and updated to 1.73.48.
OK well looks like this issue is resolved!
Just a heads up that after a few hours of debugging, weâve figured out the issue and applied a fix server side. Users on Nightly should now be able to retrieve/update to 1.73.48 without any issues/error messages.
@Saoiray because youâre one of the affected users that ended up getting 1.73.x on the release channel, would you mind doing the following and reporting back on Monday if youâve noticed any issues with your profile during the weekend? Would really appreciate the help/feedback.
Quick note: This could cause serious issues/blow up your profile so please make sure you backup/create a copy of your release profile.
- uninstall the current
Releaseversion (DONâT REMOVE YOUR PROFILE) - re-install the
Releaseversion from Brave viabrave.com - this should install
1.71.118(latest build withC130) and re-launch - it should launch and use your
releaseprofile
Use it during the weekend and see if you run into any bad regression. For example, missing/screwed up bookmarks, cookies or history. Issues with Brave Wallet or Rewards. We basically need to know if users who ended up on 1.73.x can revert back to 1.71.118 without any issues. Or if we need to find/look for other solutions for those affected users. We think the % is small but weâll know more on Monday.
Weâll have a better update for the community on Monday when we have a post-mortem and look into why this happened and put safe guards so it doesnât happen again.
I have already installed the Nightly build version 1.73.48 and it is working correctly. Many thanks to the team for fixing the problem @shivan @kamil @mattches
I have a question for @shivan @kamil and wewere if these problems of updates that are not updated correctly well stable, beta, nightly If in any case the error code of any of the 3 channels in future updates came out if you could get rid of if you could get rid of The error code that he shared that says the following: there was an error when looking for updates: the installer detected an error 8. (Error code 7: 0x80040902: 8).
@kamil it seems to have worked just fine. I was worried was going to be starting back with nothing. But uninstalled, making sure not to check the box to delete browsing data, and then installed again from brave.com/download
Near as I can tell, I still have passwords, sync, bookmarks, profiles, Wallet, etc. So didnât have to import/export anything. Info from brave://version is as follows:
| Brave | 1.71.118 Chromium: 130.0.6723.70 (Official Build) (64-bit) |
|---|---|
| Revision | d29310b051bde8ba041cd7b4edcb41ce951be12c |
| OS | Windows 11 Version 23H2 (Build 22631.4391) |
| JavaScript | V8 13.0.245.18 |
| User Agent | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 |
| Command Line | C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe --from-installer --disable-domain-reliability --enable-dom-distiller --enable-distillability-service --origin-trial-public-key=bYUKPJoPnCxeNvu72j4EmPuK7tr1PAC7SHh8ld9Mw3E=,fMS4mpO6buLQ/QMd+zJmxzty/VQ6B1EUZqoCU04zoRU= --lso-url=https://no-thanks.invalid --sync-url=https://sync-v2.brave.com/v2 --variations-server-url=https://variations.brave.com/seed --variations-insecure-server-url=https://variations.brave.com/seed --flag-switches-begin --enable-features=BraveAdblockCosmeticFiltering,CustomNotificationAds,WebAppUniversalInstall --flag-switches-end --component-updater=url-source=https://go-updater.brave.com/extensions |
| Executable Path | C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe |
| Profile Path | C:\Users\saoir\AppData\Local\BraveSoftware\Brave-Browser\User Data\Default |
awesome, thanks for the info/help @Saoiray. 
Hello @shivan @kamil @mattches I have a problem with the update in nightly that does not update correctly well. A while ago I also posted about this same problem but the update keeps failing both in stable, beta, Nightly and the updates are not successful in Windows 11 and they keep failing. I need someone to guide me to this problem to get me out of the weight of the top of these update failures. and that I can enjoy the updates and be able to update correctly well and without failure.
@Chocolate I believe that the team is looking into this right now.
In the meantime, you can redownload the installer(s) for Beta and Nightly from the website and run the installer â doing this, the installer will detect that there is already a version of these builds on your machine and will then simply fetch and apply the latest updates.
That should ensure that your browsers are fully updated as we wait for the team to push a fix.
Thank you very much @mattches I hope there is a solution to these problems to get out of all these errors and the 3 channels can be successfully updated from now on
Hello @mattches I still get the error again in the Nightly channel when updating Version 1.75.6 to 1.75.9. You told me that your colleagues were going to fix it but they havenât fixed it at all. Is there another way to fix the error in Windows 11 by going to registry editor/HKEY_LOCAL_MACHINE/SOFTWARE/WOW6432Node/BraveSoftware/Update?
What do you recommend to fix this error in the 3 stable, beta, and Nightly channels? Any recommendations for registry editors as I mentioned?
@Chocolate thanks for reporting - maybe you can try something for me
When the original problem happened, Release channel accidentally went to version 1.73.48. This only affected folks on Windows who were running Nightly and the scheduled task ran before we fixed the issue.
Can you check add/remove programs (Windows + R, appwiz.cpl, enter) and see if you have Release channel Brave installed? If you do, you can remove it. If you actually use Release channel, you can reinstall it from https://brave.com/download so that it picks up the correct version.
Please give that a shot. Itâs possible some of the values which got written to Release channel are breaking the update
@Chocolate another thing you can do is try to run the background updater. Quit out of Brave completely and open up Task Scheduler (Windows + R, taskschd.msc, enter). There you can find the entry BraveSoftwareUpdateTaskMachineUA and then run that manually (right click, Run).
That should pick up the updates even if the way in about screen (inside Brave Nightly, the brave://settings/help page) doesnât work.
@clifton Nope, I just got stuck on version 1.73.48 at 50% when I was updating. but then I had to uninstall. but when I wanted to reinstall it told me the image of the monkey that appears in the image in my first post it told me (This computer already has a newer version of Brave. If the software does not work, uninstall Brave and try again) and I got an error code An error occurred while checking for updates: The installer detected an error 8. (error code 7: 0x80040902: 8). as shown in the image above that I shared in the capture
@clifton I donât know the truth because I previously also posted this same problem and @mattches answered me and told me that this is a problem for all Chromium-based browsers and the truth is that the updates are hopelessly broken. I donât know what to do. The truth is that this is a headache every day and Iâm thinking of changing to Firefox. And I know that this problem will never be solved. Itâs frustrating.
Itâs still annoying to go windows + R taskchd.msc, enter and right click and run every time thereâs a new version. But the best thing is easier to go to Brave/settings/about Brave and run it. For me, the update is better and as I said, itâs much easier. But as I said in my previous answer, they may never fix it with updates and this is a serious problem, but the best thing Iâm going to do is abandon Brave until they fix it one day, so thank you very much for everything and good luck with Leon and Iâm going to go back to Mozilla Firefox because Iâve never had a problem with updates.
Thanks for responding, @Chocolate - Iâm actually a developer at Brave and I can assure you that we want to fix this once and for all. I work with @Mattches and heâs asked if I had some ideas as this is not a regular issue. The information youâre sharing is definitely helping narrow down the problem.
The error on the about screen you see is NOT a regular behavior for Chromium browsers. Visiting the help page should absolutely work. If everything is good (clean install of Windows, fresh install of Brave), that error should never happen. There might be cases where it happens when someone is not the administrator group for the machine. Also, it can happen if someone made the update URL non-routable inside the /etc/hosts file - on Windows this is C:\Windows\System32\drivers\etc\hosts. I donât think you touched this file - just sharing in case you know what this is. Some folks using Brave add an entry here so that Brave doesnât update on purpose (they want to choose when update happens).
We had a mistake recently and I think you are affected. This mistake caused 1.73.48 to get released on Release channel. This was not intentional and weâve adjusted our product version numbers to account for this mistake. Weâll be having a release this week with a higher version number which should get fix things up. We have a release candidate which you can try out - would you be open to installing this and seeing if it repairs things? Installing should fix the registry and hopefully get things into a good state again:
https://github.com/brave/brave-browser/releases/download/v1.73.88/BraveBrowserStandaloneSetup.exe
You should be able to download and double click it. For the scheduled task, itâs important to share this runs automatically 
The step where I asked you to try opening manually was just to see if itâs successful (did it update?). I am curious if that update worked. Basically, this background updater runs every 5 hours.
Please let me know if you can try the release candidate above. Then you can go back to Nightly and check for updates.
@clifton No, I have not touched anything at all in windows:system32/drivers/etc/hosts I have the recorded video of the capture
Yes of course, I want to make sure before processing it is necessary to uninstall Brave and then delete everything on the local disk c: program files/BraveSoftware and leave everything clean and then install what the link just sent me
@Chocolate you shouldnât need to delete things from the c: program files/BraveSoftware; simply uninstalling from the add/remove programs should do the trick. But it canât hurt to delete from program files - your profile data is not stored there.
I would try to install the release candidate (linked above; 1.73.88) and that should fix you up.
If that does not fix you up, then I am curious about the registry. If you are comfortable using regedit.exe, I should be able to help you find the problem.
ONLY READ BELOW THIS POINT IF THE ABOVE 1.73.88 INSTALLER DOES NOT FIX THE ISSUE
The updater uses these registry keys for which âchannelâ the build is on:
- Release channel uses
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BraveSoftware\Update\ClientState\{AFE6A462-C574-4B8A-AF43-4CC60DF4563B}- specifically you can look at theapkey (it should berelease). - Nightly channel uses
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BraveSoftware\Update\ClientState\{C6CB981E-DB30-4876-8639-109F8933582C}- specifically theapkey should benightly.
The mistake we made could have affected these registry keys. Hopefully not. Installing the release candidate above should fix you up without having to do this crazy step.
Please let us know!