SOLVED

An error occurred while checking for updates: We could not create this component (error code 3)

%3CLINGO-SUB%20id%3D%22lingo-sub-1298886%22%20slang%3D%22fr-FR%22%3EAn%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20could%20not%20create%20this%20component%20(error%20code%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1298886%22%20slang%3D%22fr-FR%22%3E%3CP%3EAn%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20could%20not%20create%20this%20component%20(error%20code%203%3A%200x80040154).%20%3CBR%20%2F%3ESo%20how%20is%20it%20going%3F%20Knowing%20that%20I%20had%20an%20update%20since%20Windows%20update%20%22KB4552455%22.%20%3CBR%20%2F%3EI%20don't%20know%20if%20it%20is%20this%20maj%20that%20cause%20worries!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1298903%22%20slang%3D%22en-US%22%3ERe%3A%20%D0%9E%D1%88%D0%B8%D0%B1%D0%BA%D0%B0%20%D0%BF%D1%80%D0%BE%D0%B8%D0%B7%D0%BE%D1%88%D0%BB%D0%B0%20%D0%BF%D1%80%D0%B8%20%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B5%20%D0%BE%D0%B1%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B9%3A%20%D0%9C%D1%8B%20%D0%BD%D0%B5%20%D1%81%D0%BC%D0%BE%D0%B3%D0%BB%D0%B8%20%D1%81%D0%BE%D0%B7%D0%B4%D0%B0%D1%82%D1%8C%20%D1%8D%D1%82%D0%BE%D1%82%20%D0%BA%D0%BE%D0%BC%D0%BF%D0%BE%D0%BD%D0%B5%D0%BD%D1%82%20(%D0%BA%D0%BE%D0%B4%20%D0%BE%D1%88%D0%B8%D0%B1%D0%BA%D0%B8%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1298903%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F433613%22%20target%3D%22_blank%22%3E%40bilalop44%3C%2FA%3E%26nbsp%3BHello.%20I%20have%20exactly%20the%20same%20problem.%26nbsp%3Bit%20appeared%20after%20the%20update%20to%2084.0.480.0%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1299036%22%20slang%3D%22en-US%22%3ERe%3A%20%D0%9E%D1%88%D0%B8%D0%B1%D0%BA%D0%B0%20%D0%BF%D1%80%D0%BE%D0%B8%D0%B7%D0%BE%D1%88%D0%BB%D0%B0%20%D0%BF%D1%80%D0%B8%20%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B5%20%D0%BE%D0%B1%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B9%3A%20%D0%9C%D1%8B%20%D0%BD%D0%B5%20%D1%81%D0%BC%D0%BE%D0%B3%D0%BB%D0%B8%20%D1%81%D0%BE%D0%B7%D0%B4%D0%B0%D1%82%D1%8C%20%D1%8D%D1%82%D0%BE%D1%82%20%D0%BA%D0%BE%D0%BC%D0%BF%D0%BE%D0%BD%D0%B5%D0%BD%D1%82%20(%D0%BA%D0%BE%D0%B4%20%D0%BE%D1%88%D0%B8%D0%B1%D0%BA%D0%B8%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1299036%22%20slang%3D%22en-US%22%3EThis%20one%20has%20been%20widely%20reported.%2084.0.480%20seems%20to%20have%20quite%20a%20few%20issues....%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1299522%22%20slang%3D%22en-US%22%3ERe%3A%20An%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20could%20not%20create%20this%20component%20(error%20code%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1299522%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F433613%22%20target%3D%22_blank%22%3E%40bilalop44%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%3CSTRONG%3Eit's%20Not%20related%20to%20Windows%2010%20updates.%20we%20are%20All%20experiencing%20this%20problem%3C%2FSTRONG%3E%20and%20it's%20only%20related%20to%20Edge%20canary.%3C%2FP%3E%3CP%3Eit's%20natural%20with%20Canary%20builds%20as%20they%20tend%20to%20have%20these%20problems%20and%20be%20less%20stable%20than%20Dev%20and%20other%20channels%20respectively.%3C%2FP%3E%3CP%3Elet's%20wait%20it%20out%20for%20the%20team%20to%20fix%20this%20issue%2C%20meanwhile%20you%20can%20always%3CA%20href%3D%22https%3A%2F%2Fwww.microsoftedgeinsider.com%2Fen-us%2Fdownload%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20use%20the%20Dev%20channel%3C%2FA%3E%20side%20by%20side%20your%20Canary%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1299561%22%20slang%3D%22en-US%22%3ERe%3A%20%D0%9E%D1%88%D0%B8%D0%B1%D0%BA%D0%B0%20%D0%BF%D1%80%D0%BE%D0%B8%D0%B7%D0%BE%D1%88%D0%BB%D0%B0%20%D0%BF%D1%80%D0%B8%20%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B5%20%D0%BE%D0%B1%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B9%3A%20%D0%9C%D1%8B%20%D0%BD%D0%B5%20%D1%81%D0%BC%D0%BE%D0%B3%D0%BB%D0%B8%20%D1%81%D0%BE%D0%B7%D0%B4%D0%B0%D1%82%D1%8C%20%D1%8D%D1%82%D0%BE%D1%82%20%D0%BA%D0%BE%D0%BC%D0%BF%D0%BE%D0%BD%D0%B5%D0%BD%D1%82%20(%D0%BA%D0%BE%D0%B4%20%D0%BE%D1%88%D0%B8%D0%B1%D0%BA%D0%B8%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1299561%22%20slang%3D%22en-US%22%3E%3CP%3Esame%20problem%20with%26nbsp%3B%3CSPAN%3EVersion%2084.0.481.0%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1299566%22%20slang%3D%22en-US%22%3E%D0%A0%D0%B5%3A%20%D0%97%D0%B8%D0%BD%D0%B5%D0%B4%D0%B8%D0%BD%20%D0%97%D0%B8%D0%B4%D0%B0%D0%BD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1299566%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F335201%22%20target%3D%22_blank%22%3E%40Seewolfpk%3C%2FA%3E%26nbsp%3BYes.%20I'm%20going%20to%20say%20that%2C%20too.%20We're%20waiting%20for%20the%20edge%20team%20to%20fix%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303408%22%20slang%3D%22en-US%22%3ERe%3A%20An%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20could%20not%20create%20this%20component%20(error%20code%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303408%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F433613%22%20target%3D%22_blank%22%3E%40bilalop44%3C%2FA%3E%20The%20good%20news%20is%20that%20this%20doesn't%20actually%20affect%20the%20updater's%20ability%20to%20check%20for%20updates%2C%20so%20you'll%20still%20keep%20getting%20them.%26nbsp%3B%20You%20just%20can't%20get%20them%20on-demand.%26nbsp%3B%20We%20believe%20we've%20got%20a%20fix%20for%20this%20that%20you%20should%20see%20in%20the%20next%20day%20or%20two%2C%20depending%20on%20when%20your%20updater%20decides%20to%20run.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303483%22%20slang%3D%22en-US%22%3ERe%3A%20An%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20could%20not%20create%20this%20component%20(error%20code%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303483%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F433613%22%20target%3D%22_blank%22%3E%40bilalop44%3C%2FA%3EThe%20good%20news%20is%20that%20this%20doesn't%20actually%20affect%20the%20updater's%20ability%20to%20check%20for%20updates%2C%20so%20you'll%20still%20keep%20getting%20them.%26nbsp%3B%20You%20just%20can't%20get%20them%20on-demand.%26nbsp%3B%20We%20believe%20we've%20got%20a%20fix%20for%20this%20that%20you%20should%20see%20in%20the%20next%20day%20or%20two%2C%20depending%20on%20when%20your%20updater%20decides%20to%20run.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3Eis%20it%20possible%20to%20change%20when%20the%20updater%20runs%20using%20group%20policy%3F%20by%20installing%20Edge%20ADMX%20files%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehow%20about%20running%20these%20task%20manually%20from%20Windows%20task%20scheduler%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22fdsfs.png%22%20style%3D%22width%3A%20933px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F184056iA6A5FB09B13CB963%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22fdsfs.png%22%20alt%3D%22fdsfs.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1303525%22%20slang%3D%22en-US%22%3ERe%3A%20An%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20could%20not%20create%20this%20component%20(error%20code%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1303525%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309365%22%20target%3D%22_blank%22%3E%40josh_bodner%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20running%20these%20work%20and%20force%20Edge%20to%20update%20or%20check%20for%20update%20when%20it's%20closed%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EC%3A%5CUsers%5CUSERNAME%5CAppData%5CLocal%5CMicrosoft%5CEdgeUpdate%5CMicrosoftEdgeUpdate.exe%20%2Fc%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3EC%3A%5CUsers%5CUSERNAME%5CAppData%5CLocal%5CMicrosoft%5CEdgeUpdate%5CMicrosoftEdgeUpdate.exe%20%2Fua%20%2Finstallsource%20scheduler%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1304843%22%20slang%3D%22en-US%22%3ERe%3A%20%D0%9E%D1%88%D0%B8%D0%B1%D0%BA%D0%B0%20%D0%BF%D1%80%D0%BE%D0%B8%D0%B7%D0%BE%D1%88%D0%BB%D0%B0%20%D0%BF%D1%80%D0%B8%20%D0%BF%D1%80%D0%BE%D0%B2%D0%B5%D1%80%D0%BA%D0%B5%20%D0%BE%D0%B1%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B9%3A%20%D0%9C%D1%8B%20%D0%BD%D0%B5%20%D1%81%D0%BC%D0%BE%D0%B3%D0%BB%D0%B8%20%D1%81%D0%BE%D0%B7%D0%B4%D0%B0%D1%82%D1%8C%20%D1%8D%D1%82%D0%BE%D1%82%20%D0%BA%D0%BE%D0%BC%D0%BF%D0%BE%D0%BD%D0%B5%D0%BD%D1%82%20(%D0%BA%D0%BE%D0%B4%20%D0%BE%D1%88%D0%B8%D0%B1%D0%BA%D0%B8%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1304843%22%20slang%3D%22en-US%22%3E%3CP%3Eproblem%20also%20with%26nbsp%3B%3CSPAN%3EVersion%2084.0.484.0%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1306748%22%20slang%3D%22fr-FR%22%3ERe%3A%20An%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20could%20not%20create%20this%20component%20(error%20code%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1306748%22%20slang%3D%22fr-FR%22%3E%3CP%3E84.0.485.0%20has%20resolved!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1306603%22%20slang%3D%22en-US%22%3ERe%3A%20An%20error%20occurred%20while%20checking%20for%20updates%3A%20We%20could%20not%20create%20this%20component%20(error%20code%203)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1306603%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F433613%22%20target%3D%22_blank%22%3E%40bilalop44%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EFixed%20in%20Version%2084.0.485.0%20(Official%20build)%20canary%20(64-bit)%3C%2FSTRONG%3E%20%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fhearteyes_40x40.gif%22%20alt%3D%22%3Ahearteyes%3A%22%20title%3D%22%3Ahearteyes%3A%22%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22bvbv.png%22%20style%3D%22width%3A%20727px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F184332iC16931265F0911A8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22bvbv.png%22%20alt%3D%22bvbv.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

An error occurred while checking for updates: We could not create this component (error code 3: 0x80040154).
So how is it going? Knowing that I had a update since Windows update "KB4552455".
I do not know if it is this maj that cause worries !!

15 Replies
Highlighted
Highlighted
Highlighted

@bilalop44 

Hello,

it's Not related to Windows 10 updates. we are All experiencing this problem and it's only related to Edge canary.

it's natural with Canary builds as they tend to have these problems and be less stable than Dev and other channels respectively.

let's wait it out for the team to fix this issue, meanwhile you can always use the Dev channel side by side your Canary :)

Highlighted

@Seewolfpk Yes. I'm going to say that, too. We're waiting for the edge team to fix it.

Highlighted

@bilalop44 The good news is that this doesn't actually affect the updater's ability to check for updates, so you'll still keep getting them.  You just can't get them on-demand.  We believe we've got a fix for this that you should see in the next day or two, depending on when your updater decides to run.  

Highlighted

@josh_bodner 


@josh_bodner wrote:

@bilalop44The good news is that this doesn't actually affect the updater's ability to check for updates, so you'll still keep getting them.  You just can't get them on-demand.  We believe we've got a fix for this that you should see in the next day or two, depending on when your updater decides to run.  


Hi,

is it possible to change when the updater runs using group policy? by installing Edge ADMX files?

 

how about running these task manually from Windows task scheduler?

 

fdsfs.png

 

 

Highlighted

@josh_bodner @fawkes 

 

Will running these work and force Edge to update or check for update when it's closed?

 

C:\Users\USERNAME\AppData\Local\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe /c

 

C:\Users\USERNAME\AppData\Local\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe /ua /installsource scheduler

 

Highlighted
Best Response confirmed by bilalop44 (Occasional Contributor)
Solution

@bilalop44 @Seewolfpk @josh_bodner @geoffarnold @nikitat1260 

Fixed in Version 84.0.485.0 (Official build) canary (64-bit) :hearteyes:

 

bvbv.png

 

Highlighted

Thanks, @HotCakeX I had to go to the channel and download the latest Edge Canary, then guessed that the next step should be to quit Edge and restart it. That worked. It would be helpful if the installer recommended the restart.

Highlighted
oh of course when you are running the installer you have to have Edge closed first :)
Highlighted
Highlighted

 

1) Start your computer and log on as an administrator.

2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.

3) In the new window, select "Restore my computer to an earlier time" option and then click Next.

4) Select the most recent system restore point from the "On this list, click a restore point" list, and then click Next.

5) Click Next on the confirmation window.

6) Restarts the computer when the restoration is finished.

@bilalop44