Forum Discussion

DavidGB's avatar
DavidGB
Steel Contributor
Feb 10, 2021

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?

  • gduvl's avatar
    gduvl
    Copper Contributor

    DavidGB 

     

    Same here on Developer Version 90.0.796.0 (Official build) dev (64-bit). Also sent via FB etc.

  • Hey folks! 

     

    Just an update that we're investigating this, thanks for your reports! 😃

     

    -Alex

    • ms4132's avatar
      ms4132
      Steel Contributor

      Alexandra-R 

       

      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.

    • ms4132's avatar
      ms4132
      Steel Contributor

      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)

    • ms4132's avatar
      ms4132
      Steel Contributor

      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.

      • ms4132's avatar
        ms4132
        Steel Contributor

        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.

  • ms4132's avatar
    ms4132
    Steel Contributor

    DavidGB I am receiving this error as well and have reported it via Send feedback. For me it started in 793 and continued in 794.

    • DavidGB's avatar
      DavidGB
      Steel Contributor
      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.
  • 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?

Resources