Forum Discussion
Profile error in Canary
Since yesterday's Canary update, every time I start Edge Canary I get a 'Profile error - Some features may not be available. Something went wrong.' message. Although Canary then finishes launching and appears to work OK. This has continued after today's update, to 90.0.794.0, and after a re-start following a Windows 10 update, but I do not get the Profile Error message with Edge Dev or standard. Any idea how to clear it in Canary?
- I've also reported it via Send Feedback, and as well as the usual instant auto-acknowledgement email yesterday evening, I got a further one today saying they are actively looking into it now. Hopefully a fix soon, then.
- Alexandra-R
Microsoft
Hey folks!
Just an update that we're investigating this, thanks for your reports! 😃
-Alex
Alexandra-R I am still seeing this issue on 90.0.795.0 (Official build) canary (64-bit) on two systems. On both systems, Edge Canary on 794 would not reopen until I signed out of my Windows account and back in. Today when I signed out of my Windows account and back in, the upgrade to 795 was complete and Edge Canary will now reopen successfully.
- I too am still seeing the problem on 795. But in my case, once the OK button is clicked in the error message, Edge has finished starting and worked without any problem (at least that I've come across) in all versions since this issue has appeared.
Alexandra-R I am still seeing this error message after updating to Version 90.0.796.0 (Official build) canary (64-bit) today.
Alexandra-R On one of my computers the problem came back where Edge Canary would not open until I signed out of my Windows account and signed back in.
Alexandra-R I found in one test that if I stopped all the Microsoft Edge processes in the Task Manager, Edge Canary would open successfully without signing out of my Windows account and signing in again. But there were a lot of processes to be stopped.
- I'm not getting this error despite being on the same OS and Edge version, can you attach a screenshot of that error message please?
I am getting this as well started Monday I believe.
