Forum Discussion
Canary Update
Anyone seeing this error on Edge Canary?
I did a repair, didn't help.
I uninstalled and re downloaded and the Version #
changed from .3967 yesterday to .3968 today.
So it is updating, but what's this error?
48 Replies
I reinstall every two days—the error message keeps appearing!
0X800700C1)
Version 150.0.4064.0 (Offizielles Build) canary (64-Bit)
- Kelly_Y
Microsoft
Hey Everyone! I just checked with our developers and they have a fix rolling out soon for this error message. It is expected in EdgeUpdate version 1.3.237.7. Thanks!
-Kelly
I think your developers are fibbing to you. Doesn't appear to me that they fixed anything. Still an error with the latest update - today. And, inquiring minds want to know; what exactly is the component that can't be created? I'd like to know so if Edge Canary blows up, I have something to blame by name 🙂
Come on Kelly and the Edge Team. This has been going on
since March and still not fixed!!! Don't give us empty promises.
Yeah, tends to happen when you have complacent programmers.
And the newest version compared to what Kelly_Y showed us in now,
And still no fix
Dennis5mile
Allow me to call BS on that, version 151.0.4082.0 with EdgeUpdate 1.3.239.19 does the EXACT SAME THING.
I've had this for a few months now. When it first appeared, I got Copilot to walk me through a tone of possible fixes starting with the simplest (reinstall Canary) to various registry changes. Initially it solved it, but it returned a few days later. Per Copilot, it doesn't matter because every Canary update is a whole new version, and I've certainly still been getting frequent updates. As long as you're getting updates, I wouldn't worry about it.
I learned a long time ago as system administrator to not worry about things I had no control over. I simply said the IT admin prayer when stuff like this happened - Thank God I drink. 😂
CrazyKats is right. It's not a matter of "worrying" about it, it's a matter of Edge support team making folks feel like they are wasting their time sending in feedback when they don't bother to respond with any type of acknowledgement.
Secondly, "every canary update" is not a "whole" new version. It's a modified version of the previous version with its inserted fixes, add-ins, or removals of whatever they are trying to change/fix.
And as CrazyKats has also stated, it is now being passed down to the next level versions of Edge. It is only a matter of time before it hits the public versions unless they act on it before then.
Dennis5mile
Yep this is an interesting one as it's now been at least a month or so with no acknowledgement of the issue. I reported it too and no response at all. Hopefully fixed soon. Not a real issue as it updates but more an annoyance.
It isn't a matter of worrying about it. It's a case of Feedback has been sent, no one from Edge team is acknowledging this error or offering any explanation.
It has also now made it down to the Dev Edge build.
and now the same problem new in Dev-Channel with version 150.0.4041.0, and Canary with version 150.0.4045.0
😨I mean the wrong layout ...
Same issue with 4021...
And now Canary Edge is stuck on .4021 and not
updating itself and still has the error.
Yep, still error with "
An error occurred while checking for updates: We couldn't create that component (error code 3: 0X800700C1).
Version 150.0.4031.0 (Official build) canary (64-bit)"
You'd think they'd have gotten tired of getting in-browser FB by now and fix it, but apparently not..... Here comes more FB....
Dennis5mile
same here with Version 149.0.4021.0
Version 149.0.4009.0 (Offizielles Build) canary (64-Bit) same Problem with this Version.
uninstalling and re download. It doesn't work and doesn't fix the problem.
An error occurred while searching for updates: This component could not be created.
(Fehlercode: 3: 0X800700C1)
Version 149.0.4009.0 (Offizielles Build) canary (64-Bit)
I've noticed similar weird update glitches with Canary builds before, since they are so experimental. As long as the version number is actually changing from .3967 to .3968 like you mentioned, it's usually just a visual bug with the updater itself. Hopefully, the next daily build clears that error code for you!
And Still, nothing has changed.
"
An error occurred while checking for updates: We couldn't create that component (error code 3: 0X800700C1).
Version 149.0.4002.0 (Official build) canary (64-bit)"
Dennis5mile
