Apr 09 2020 11:50 AM
An error occurred while checking for updates: We couldn't create that component (error code 3: 0x80040154). Version 84.0.480.0 (Official build) canary (64-bit)
I tried completely uninstalling Edge Canary and reinstalling it. Still shows this Error on About screen, although it seems to run fine.
Apr 14 2020 01:21 AM
SolutionApr 14 2020 07:47 AM
@Rohit YadavNope did not fix for me either.
Apr 14 2020 08:07 AM
Apr 14 2020 08:16 AM
Apr 14 2020 10:30 AM
Version 485 is out and it works.
Apr 14 2020 10:36 AM
Apr 14 2020 10:42 AM
Apr 14 2020 10:47 AM
@tistouGood here as well.
Apr 14 2020 10:53 AM - edited Apr 14 2020 10:57 AM
@thexfile
Thanks for reporting that this has been fixed!
Mine had already been auto-updated by the time that I opened Edge Canary and all is well with the edge://help page again.
Apr 14 2020 10:54 AM
Hi,
Thank you for the update.
Get no error code during update procedure.
Apr 14 2020 10:55 AM - edited Apr 14 2020 10:58 AM
Thank you for this nice update
Apr 14 2020 11:26 AM
Excellent! I'm glad that you all are starting to see this fix. I can confirm that it shipped today!
(If you aren't seeing it yet, please be advised that different machines may update at different times, but we expect everyone on Canary to be good to go by tomorrow!)
Cheers,
Fawkes (they/them)
Project & Community Manager - Microsoft Edge
Apr 14 2020 11:31 AM
Thanks for fixing, can you tell us what the problem was?
Apr 14 2020 11:53 AM
Apr 14 2020 12:24 PM
Apr 14 2020 12:46 PM
Apr 14 2020 01:17 PM
@Dennis5mile
Check a few posts up for a way that works. It basically runs the updater, as is done each day via Task Scheduler, but lets you do it at any time. Yours could be set to run at some specific hour of the day, so it will eventually update on its own. Mine did.
Try closing Edge Canary and running this (I don't know if you actually have to close Edge):
%LOCALAPPDATA%\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe /c
Apr 14 2020 01:57 PM
Apr 15 2020 12:51 AM
The updater worked on its own and I am updated to build 485. Can confirm that the issue is resolved now!
This was a great adventure!