Forum Discussion
Profile error in Canary
MicrosoftHey 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.
Alexandra-R I am still seeing the profile error and still see the problem with Edge Canary not opening sometimes until I stop the Microsoft Edge processes in Task Manager.
Version 90.0.800.0 (Official build) canary (64-bit)
Version 90.0.801.0 (Official build) canary (64-bit)
I am still seeing the profile error and still see the problem with Edge Canary not opening sometimes until I stop the Microsoft Edge processes in Task Manager.
- Same here. Still seeing this error.....
Dennis5mile- Alexandra-R
Dennis5mile ms4132 thanks for continuing to update on this and check in!
Just want to confirm if you're seeing this error in Dev as well after the weekly update or just Canary? Also, please file feedback on the latest version of Canary.
No updates to share on our side yet, though the team is still digging in to this.
