Forum Discussion
Canary Update
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
- CrazyKatsJun 12, 2026Steel Contributor
Now up to build .4090 and still getting error.
- CrazyKatsJun 12, 2026Steel Contributor
Mine was not fixed on .4090 but it IS fixed on .4091.
Three months to fix. SMH
- cjahn50Jun 15, 2026Iron Contributor
Saw that there was an update overnight. Restarted and it was fixed.
But this is 5 versions higher than it was last night. Wacky, but it's fixed. 🤞
- WestendJun 12, 2026Copper Contributor
Fixed
- cjahn50Jun 09, 2026Iron Contributor
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 🙂
- CrazyKatsJun 08, 2026Steel Contributor
Come on Kelly and the Edge Team. This has been going on
since March and still not fixed!!! Don't give us empty promises.
- Dennis5mileJun 08, 2026Silver Contributor
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
- AtaemonusJun 08, 2026Copper Contributor
Allow me to call BS on that, version 151.0.4082.0 with EdgeUpdate 1.3.239.19 does the EXACT SAME THING.
- cjahn50Jun 04, 2026Iron Contributor
This is probably getting old, but yet again it just udated to Version 150.0.4074.0 (Official build) canary (64-bit) and the error message is still there. Does anyone know what exactly the component that couldn't be created is? And who exactly is we 😂
- cjahn50Jun 03, 2026Iron Contributor
And to add. Just updated to Build .4072 and yes, the error is still there.
- CrazyKatsJun 02, 2026Steel Contributor
Build .4071 is out and we still have this error!!!
- Dennis5mileJun 02, 2026Silver Contributor
Well here we are with the update you posted
And still... as of this morning 06-02-2026
"An error occurred while checking for updates: We couldn't create that component (error code 3: 0X800700C1).
Version 150.0.4064.0 (Official build) canary (64-bit)"
Dennis5mile
- cjahn50Jun 02, 2026Iron Contributor
Well here's an interesting turn of events. I just got the latest auto update. Restarted Canary. And then I saw this:
An error occurred while checking for updates: We couldn't create that component (error code 3: 0X800700C1).
Version 150.0.4070.0 (Official build) canary (64-bit)
Note: It updated and then said it has issues checking for updates... 😂
I love a good mystery. And this ain't that.
Carl
- cjahn50Jun 01, 2026Iron Contributor
What exactly am I looking for in the folder 1.3.237.7. That's where I am now number wise. It shows as having been created on 5/29. So if there was a fix, I didn't get it last Friday. And, FWIW, I did a repair/install today and am still at Version 150.0.4064.0 (Official build) canary (64-bit).
- Dennis5mileMay 28, 2026Silver Contributor
That's nice, but, that is NOT Canary. What about for Edge Canary? "
An error occurred while checking for updates: We couldn't create that component (error code 3: 0X800700C1).
Version 150.0.4059.0 (Official build) CANARY (64-bit)"?
Dennis5mile
- cjahn50May 31, 2026Iron Contributor
Just saw this today. Updates on Canary have been an adventure for some time now. But this is a first for me. I'm on Version 150.0.4064.0 (Official build) canary (64-bit) after a repair/reinstall just a few minutes ago.
I'm guessing for me, this started a couple of days ago. I haven't seen this error message on Edge or Edge Dev. They update just fine (fingers crossed).
- brimaMay 28, 2026Iron Contributor
Hi Dennis,
i think she talked about this file.C:\Users\USERNAME\AppData\Local\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe
act. Version of this file is: 1.3.225.7
This file is used from the Tasksheduler Task > MicrosoftEdgeUpdateTask...
And i think this file is the Updater for all Edge channels.
Best regards
brima