An error occurred while checking for updates: We couldn't create that component (error code 3: 0x800

%3CLINGO-SUB%20id%3D%22lingo-sub-1302443%22%20slang%3D%22en-US%22%3EAn%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20couldn't%20create%20that%20component%20(error%20code%203%3A%200x800%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1302443%22%20slang%3D%22en-US%22%3E%3CP%3EStarted%20to%20get%20this%20error%20with%20v84.0.480.0%20update.%26nbsp%3B%20Manually%20updated%20today%20to%20481%20and%20still%20have%20this.%26nbsp%3B%20Any%20idea%20on%20how%20to%20fix%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20also%20running%20Dev%20version%20on%20same%20machine%20with%20no%20problems.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1302447%22%20slang%3D%22en-US%22%3ERe%3A%20An%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20couldn't%20create%20that%20component%20(error%20code%203%3A%200%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1302447%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3Eit's%20affecting%20Everyone%20on%20the%20Canary%20channel%20and%20also%20it's%20unrelated%20to%20Windows%20OS%20or%20other%20channels.%3CBR%20%2F%3Ewe're%20waiting%20for%20today%20(Monday)%20update%20that%20maybe%20and%20hopefully%20fix%20this%20issue%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303443%22%20slang%3D%22en-US%22%3ERe%3A%20An%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20couldn't%20create%20that%20component%20(error%20code%203%3A%200%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303443%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F145820%22%20target%3D%22_blank%22%3E%40Tony%20Calabrase%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20reaching%20out.%20Here's%20some%20good%20news%3A%20I%20just%20got%20confirmation%20from%20the%20product%20team%20that%20they%20are%20expecting%20this%20fix%20to%20ship%20in%20the%20next%20version%20of%20Canary!%20So%20hopefully%2C%20you%20should%20see%20this%20resolved%20very%20soon.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CI%3EFawkes%20(they%2Fthem)Project%20%26amp%3B%20Community%20Manager%20-%20Microsoft%20Edge%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Senior Member

Started to get this error with v84.0.480.0 update.  Manually updated today to 481 and still have this.  Any idea on how to fix?  

Am also running Dev version on same machine with no problems.

2 Replies
Highlighted
Hi,
it's affecting Everyone on the Canary channel and also it's unrelated to Windows OS or other channels.
we're waiting for today (Monday) update that maybe and hopefully fix this issue
Highlighted

@Tony Calabrase  Thanks for reaching out. Here's some good news: I just got confirmation from the product team that they are expecting this fix to ship in the next version of Canary! So hopefully, you should see this resolved very soon.

 

Thanks,

 

Fawkes (they/them)
Project & Community Manager - Microsoft Edge