A keychain cannot be found to store "Microsoft Edge"

%3CLINGO-SUB%20id%3D%22lingo-sub-1350265%22%20slang%3D%22en-US%22%3EA%20keychain%20cannot%20be%20found%20to%20store%20%22Microsoft%20Edge%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1350265%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20the%20previous%20dev%20update%20I%20got%20this%20%22A%20keychain%20cannot%20be%20found%20to%20store%20%22Microsoft%20Edge%22%22%20message.%26nbsp%3B%20I%20chose%20%22reset%20to%20defaults%22%20and%20it%20cleared%20all%20my%20cookies%20etc%2C%20leaving%20me%20logged%20in%20but%20%22not%20syncing%22.%26nbsp%3B%20Then%20with%20today's%20update%20(%3CSPAN%3E84.0.495.2)%26nbsp%3B%3C%2FSPAN%3EI%20got%20the%20same%20message%20again.%26nbsp%3B%20This%20time%20I%20canceled%20that%20dialog%20and%20the%20browser%20launched%2C%20still%20with%20%22not%20syncing.%22%26nbsp%3B%20So%20I%20signed%20out%20and%20signed%20back%20into%20my%20MSA%20profile%20and%20got%20a%20bunch%20of%20%22A%20keychain%20cannot%20be%20found%20to%20store%20%3CVARIOUS%20things%3D%22%22%20identity%3D%22%22%20wants%3D%22%22%20to%3D%22%22%20store%3D%22%22%3E.%22%26nbsp%3B%20Now%20the%20browser%20is%20stuck%20in%20%22setting%20up%20sync.%22%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ESuggestions%20on%20how%20to%20fix%20and%20whether%20more%20info%20is%20needed%20to%20report%20a%20bug%3F%3CBR%20%2F%3E%3CBR%20%2F%3EBruce%3C%2FVARIOUS%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1358595%22%20slang%3D%22en-US%22%3ERe%3A%20A%20keychain%20cannot%20be%20found%20to%20store%20%22Microsoft%20Edge%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1358595%22%20slang%3D%22en-US%22%3EAny%20suggestions%3F%20I've%20had%20to%20abandon%20Edge%20on%20that%20machine%20and%20go%20back%20to%20Chrome.%3CBR%20%2F%3E%3CBR%20%2F%3EBruce%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1361413%22%20slang%3D%22en-US%22%3ERe%3A%20A%20keychain%20cannot%20be%20found%20to%20store%20%22Microsoft%20Edge%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1361413%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F431891%22%20target%3D%22_blank%22%3E%40Bruce_Lowekamp%3C%2FA%3E%20We're%20sorry%20to%20hear%20that!%20A%20couple%20of%20questions%20for%20you%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EHave%20you%20tried%20any%20%3CA%20title%3D%22https%3A%2F%2Fwww.microsoftedgeinsider.com%2Fen-us%2Fdownload%22%20href%3D%22https%3A%2F%2Fwww.microsoftedgeinsider.com%2Fen-us%2Fdownload%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eother%20MS%20Edge%20builds%3C%2FA%3E%3F%20If%20so%2C%20which%2C%20and%20what%20was%20the%20behavior%3F%3C%2FLI%3E%0A%3CLI%3EHave%20you%20had%20a%20chance%20to%20submit%20in-browser%20feedback%20and%20diagnostic%20logs%3F%20If%20not%2C%20feel%20free%20to%20send%20me%20a%20DM%20first%2C%20and%20I%20can%20give%20you%20a%20code%20to%20include.%20(This%20will%20help%20it%20get%20to%20the%20Sync%20team%20faster.)%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BWhat%20OS%20are%20you%20using%3F%3C%2FLI%3E%0A%3C%2FOL%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%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1365676%22%20slang%3D%22en-US%22%3ERe%3A%20A%20keychain%20cannot%20be%20found%20to%20store%20%22Microsoft%20Edge%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365676%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F431891%22%20target%3D%22_blank%22%3E%40Bruce_Lowekamp%3C%2FA%3E%26nbsp%3BExcellent%2C%20I'm%20glad%20to%20hear%20that%20did%20the%20trick.%20Please%20let%20us%20know%20if%20you%20encounter%20anything%20similar%2C%20and%20we'd%20be%20happy%20to%20take%20a%20deeper%20look.%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%3CI%3E%3C%2FI%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1365651%22%20slang%3D%22en-US%22%3ERe%3A%20A%20keychain%20cannot%20be%20found%20to%20store%20%22Microsoft%20Edge%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365651%22%20slang%3D%22en-US%22%3E%3CP%3E%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%3Bthanks.%26nbsp%3B%20I%20hadn't%20used%20Edge%20for%20a%20couple%20of%20days%20but%20when%20I%20went%20to%20check%20it%20had%20been%20updated%20to%20yesterday's%20build%2C%20and%20apparently%20that%20resolved%20the%20problem%20I%20had%20seen%20with%20the%20previous%20two%20builds.%26nbsp%3B%20So%20I%20guess%20I'm%20good%20for%20now.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBruce%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Microsoft

With the previous dev update I got this "A keychain cannot be found to store "Microsoft Edge"" message.  I chose "reset to defaults" and it cleared all my cookies etc, leaving me logged in but "not syncing".  Then with today's update (84.0.495.2) I got the same message again.  This time I canceled that dialog and the browser launched, still with "not syncing."  So I signed out and signed back into my MSA profile and got a bunch of "A keychain cannot be found to store <various things Identity wants to store>."  Now the browser is stuck in "setting up sync."  

Suggestions on how to fix and whether more info is needed to report a bug?

Bruce

28 Replies
Highlighted
Any suggestions? I've had to abandon Edge on that machine and go back to Chrome.

Bruce
Highlighted

@Bruce_Lowekamp We're sorry to hear that! A couple of questions for you:

  1. Have you tried any other MS Edge builds? If so, which, and what was the behavior?
  2. Have you had a chance to submit in-browser feedback and diagnostic logs? If not, feel free to send me a DM first, and I can give you a code to include. (This will help it get to the Sync team faster.)
  3.  What OS are you using?

 

Thanks,

 

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

Highlighted

@fawkes thanks.  I hadn't used Edge for a couple of days but when I went to check it had been updated to yesterday's build, and apparently that resolved the problem I had seen with the previous two builds.  So I guess I'm good for now. 

 

Bruce

 

Highlighted

@Bruce_Lowekamp Excellent, I'm glad to hear that did the trick. Please let us know if you encounter anything similar, and we'd be happy to take a deeper look.

 

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

Highlighted

@fawkes I faced it issue right today. On my Macbook Pro. Edge updated via the Microsoft Updater, and then when it re-opened, I get this error message - "A keychain cannot be found to store 'Microsoft Edge'". A new keychain had to be created and now all my previous passwords are lost !!!!

 

Please help restore !!!

Highlighted

@bodhidasgupta Thanks for reaching out, and I'm sorry to hear that! If you haven't yet, can you please try uninstalling and reinstalling MSFT Edge? And can you please confirm what channel and version you're currently using?

 

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

Highlighted

@fawkesI just got this message a few minutes ago when I opened Edge.  When I select Preferences it only shows me the ability to recreate a new keychain.  Is there any way to restore the old one?  I am losing a lot of data.

 

I did get a lot of extension crashes the first open, I exited Edge and saw an Edge update install.  When I opened Edge again, then I got the keychain error.

Highlighted

@fawkes Well now everything has magically reappeared after I exited Edge again and relaunched.

Highlighted

@VMGuru Great, I'm glad to hear it!

 

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

Highlighted

@Bruce_Lowekamp when I open new tab, Edge showing a popup and saying "Keychain Not Found" -in Version 87.0.666.0 (Official build) Canary (64-bit): MacOS, attached screenshot.

 
 
Highlighted

@fawkes This is getting annoying. I am trying to like the edge interface and move away from Chrome. I have been receiving the errors listed above. 

 

I have not been able to get rid of them. If I have to uninstall Edge and reinstall I will most likely just keep it uninstalled. I find this practice a horrible suggestion. I have a couple of extensions I would have to reinstall and set back up. This is time I don't have. 

 

I have been running edge for more than 45 days now and was liking the updated browser. Some were along the line something was updated and now it keeps asking me for keychain information. The problem is I DONT use Key chain. 

 

Please help.

Highlighted

Same issue here, I've been running Edge on macOS for over a year now, but it seems recently every time I update I end up with endless keychain errors so I'm at the point where I'm about ready to start using Brave rather than Edge.

 

I'm actually a big fan of Edge, but losing my cookies and forcing me to wipe my macOS keychain after every update is becoming a deal breaker.

 

Edit: I've just submitted diagnosis data, but that generates further errors and I'm now getting errors for every HTTP request (I've had multiple pop up typing this). I'm switching to Brave.

 

Version 86.0.622.43 (Official build) (64-bit)

Highlighted

@TIA568B @AJB_Daddler @rcreddy I'm sorry to hear that you're still encountering this! Can you please confirm what build number and channel you're currently using? 

 

For more context: we recently started to receive reports from macOS users saying they saw an error, “A keychain cannot be found,” after updating Microsoft Edge. This error was not common, but could be alarming since it was unexpected. A few weeks ago, we deployed a change that we believe resolved the issue.

 

However, if you continue to see this error pop up, we want to know! You can get rid of the keychain error by right-clicking on the Edge logo in the dock, choosing Force Quit, and clicking Cancel in the dialog that appears. Once you start Edge again, the error should be gone and your settings should still be in place; you can then submit feedback to let us know you saw the error again by heading to the  menu > Help and feedback > Send feedback. We appreciate your patience while we investigate and work to get this resolved!

 

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

Highlighted

@fawkes I am sorry but I have no idea what "channel" in this context would be. the version is:

Version 86.0.622.43 (Official Build) (64-bit)

I have been getting this repetitively. 

 

I will report but this pop up is driving me crazy. 

I continuously work on my browsers so I don't close them that often. I use them as place holders for information on various projects I am working on. Right now I have 3 profiles of Chrome and 1 of Edge open each with several tabs. 

 

Highlighted


This issue seems to affect the content of this directory, too: 
~/Library/Keychains

MS Edge will try to creat login.keychain-db.sb-xxxxxxxx-xxxxxx file repeatly, then the folder size will suddenly become very big (from less than 10MB becomes up to more than 1GB) 

Highlighted

@vixyao That's huge!!!!!!!

Highlighted

@fawkes ya these updates and losing the keychain is seriously getting annoying after every update. if this happens again i'm ready to leave edge as well. any idea on when a fix will be made? seems to be an ongoing issue with many people.

Highlighted

@fawkes I had the same issue occur this evening with an Edge update to Version 86.0.622.68 (Official build) (64-bit) 

Highlighted

@Ryanbowley Same happening with me.  And not the first time.  Seriously bad and annoying programming.  In the few years since I switched to Apple products, I have never seen this issue before.  Come on MS, get your act together!  I am trying to use your product on MacOS but it's proving to be a dismal failure...  I should have known better.