PC Repair and Driver Updater Recommended for Fixing Issues and Updating Drives on Windows PC. Trusted by Millions.
[Update April 15, 2020] – Starting with Microsoft Edge v84.0.485.0. the issue is fixed by the company. To fix the issue update the Edge browser to latest version.
In case, error message still appears, then close the browser, restart your computer and then again try to update the browser in the background.
Microsoft Edge in Canary channel v84.0.481.0 is unable to update he browser to latest version with and showing Error code 3: 0x80004002.
Majority of the users who’re using Edge browser in canary channel reporting in this thread of Microsoft Tech Community that when they trying to update the Edge browser to latest version, they receive an error message which reads:
An error occurred while checking for updates: We couldn’t create that component (error code 3: 0x80004002).
Accompanied by a Learn more that take you to troubleshooting tips for installing and updating Microsoft Edge.
As of writing this blog post, the reason behind this Edge Update error is unknown. We tried completely uninstalling Edge Canary and reinstalling it but still shows this error on About screen, although the browser is running fine.
Unfortunately, there’s no solution available the moment to fix the issue. But one moderator on Microsoft Techcommunity suggested that its company side error and will be fixed in upcoming update.
The moderator also added that it’s natural with Canary builds as they tend to have these problems and be less stable than Dev and other channels respectively
We will update the post if there is news.
Donate on Paypal or Buy us a coffee or Join Patreon if you find the information shared in this blog post useful. Mention ‘Coffee’ in the Subject. So that I can thank you.
Thanks for the update!
It has been two days now and this still does not work. What gives?
Still not fixed. I will update soon it’s fixed.
It is fixed as of 4-16-20. I think it was repaired as part of the Windows update I did that day.
Thanks for sharing this. I already updated same information the moment company fixed it.