Forum Discussion
Bruce_Lowekamp
Microsoft
Apr 30, 2020A keychain cannot be found to store "Microsoft Edge"
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 s...
AJB_Daddler
Oct 18, 2020Copper Contributor
Deleted 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.
TIA568B
Oct 19, 2020Copper Contributor
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)
- eugenerysajJan 25, 2022Copper Contributor
Hi Fawkes,
Have your team managed with Apple's help to figure out the root cause? I'd be grateful if you could share the details.
I have a very similar issue with my app: "A keychain cannot be found to store ..." popup occasionally appears after the app is restarted by management script and your case seems to be the closest of what I've managed to find.
- sergeityrNov 24, 2021Copper ContributorHave an error, EDGE is trying to use Keychain. How to stop using Keychain at all ? I am having EDGE for M1. Having a message, there is option deny, but the message coming back ?
S - AJB_DaddlerDec 04, 2020Copper Contributor
Deleted Nope didn't work. the persistent error keeps coming up. Talk about a pain..........
Any true fixes in store.
- DeletedDec 02, 2020
Laris_Qiao Bruce_Lowekamp AJB_Daddler haligasd Shaun Parfett Hi all, I wanted to provide you with an update on the keychain error.
We are actively working with Apple to address this. In the meantime, we suggest clicking Cancel on the keychain error dialog and restarting your Mac device to resolve the issue.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - Laris_QiaoNov 14, 2020Copper ContributorPlease fix it ASAP.
Microsoft Edge is up to date.Version 86.0.622.69 (Official build) (64-bit).
```
> pwd
/Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app/Contents
> plutil -p Info.plist
{
"BuildMachineOSBuild" => "19G2021"
"CFBundleDevelopmentRegion" => "en"
"CFBundleDisplayName" => "Microsoft AutoUpdate"
"CFBundleExecutable" => "Microsoft AutoUpdate"
"CFBundleIconFile" => "AppIcon"
"CFBundleIconName" => "AppIcon"
"CFBundleIdentifier" => "com.microsoft.autoupdate2"
"CFBundleInfoDictionaryVersion" => "6.0"
"CFBundleName" => "Microsoft AutoUpdate"
"CFBundlePackageType" => "APPL"
"CFBundleShortVersionString" => "4.29"
"CFBundleSignature" => "MSau"
"CFBundleSupportedPlatforms" => [
0 => "MacOSX"
]
"CFBundleURLTypes" => [
0 => {
"CFBundleURLSchemes" => [
0 => "updateoffice"
]
}
]
"CFBundleVersion" => "4.29.20110804"
"CSFlags" => 73728
"DTCompiler" => "com.apple.compilers.llvm.clang.1_0"
"DTPlatformBuild" => "12A7209"
"DTPlatformName" => "macosx"
"DTPlatformVersion" => "10.15.6"
"DTSDKBuild" => "19G68"
"DTSDKName" => "macosx10.15"
"DTXcode" => "1200"
"DTXcodeBuild" => "12A7209"
"LSHasLocalizedDisplayName" => 1
"LSMinimumSystemVersion" => "10.10"
"MbuLoggingFullLegacyUpload" => 1
"MicrosoftBuildIncrement" => "4"
"MicrosoftBuildNumber" => "201108"
"NSAppTransportSecurity" => {
"NSAllowsArbitraryLoads" => 1
}
"NSHumanReadableCopyright" => "© 2020 Microsoft Corporation. All rights reserved."
"NSMainNibFile" => "SAUMainWindow"
"NSPrincipalClass" => "SAUApplication"
"OfficeLegacyVersion" => "4.29.1108.0"
}
``` - AJB_DaddlerNov 14, 2020Copper Contributor
Deleted MAU version? Don't know what that is. If it's the version of edge I am running that should be: Microsoft Edge is up to date.Version 86.0.622.69 (Official build) (64-bit).
Just updated and pop-up has appeared twice within 5 min. arrggg.....
- DeletedNov 14, 2020
haligasd Thank you! I just passed that on to the correct dev.
AJB_Daddler, if you're comfortable providing your MAU version as well, that would help us fix this as soon as possible.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - haligasdNov 13, 2020Copper Contributor
Deleted 4.29.20110804. i get this error after every update. at one point i had i was in the beta build program if that helps at all for all the other MS products but i am now only on the stable builds
- AJB_DaddlerNov 13, 2020Copper Contributor
Deleted The worst part is the issue never went away for me. I have submitted several feedback submissions but have gotten no results, just annoying popups.
And why is it every time Edge updates (Which is a lot) all my extension passwords have to be re-entered? Extremely annoying. I could see having an update that forced this bi-annually but every other week?
- DeletedNov 13, 2020
Shaun Parfett Ryanbowley The team confirmed that they're actively looking into this. However, they said it would be really helpful to know your specific MAU (Microsoft AutoUpdate) versions. This isn't personally-identifiable information, and would help them troubleshoot. If you two, and anyone else who's seeing this issue again could provide the following, our devs would appreciate it:
1. Check your MAU versions by navigating to/Library/Application Support/Microsoft/MAU2.0/
2. Then highlight Microsoft AutoUpdate.app -- The version should show up on the right.3. Comment below with what that version number is. (See the screenshot for an example.)
Program Manager & Community Manager - Microsoft Edge - DeletedNov 13, 2020
Shaun Parfett Ryanbowley Thank you both for reporting this! It sounds like we're seeing a recent resurgence of the issue, so we're reaching out to the Mac team right now. If you haven't yet, please also submit diagnostics through the browser ("..." menu > Help and feedback > Send feedback) as it provides our devs with logs.
Fawkes (they/them)
Program Manager & Community Manager - Microsoft Edge - Shaun ParfettNov 13, 2020Brass Contributor
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.
- RyanbowleyNov 13, 2020Copper Contributor
Deleted I had the same issue occur this evening with an Edge update to Version 86.0.622.68 (Official build) (64-bit)
- AJB_DaddlerOct 19, 2020Copper Contributor
Deleted 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.
- DeletedOct 19, 2020
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