Forum Discussion
Canary Update
I've had this for a few months now. When it first appeared, I got Copilot to walk me through a tone of possible fixes starting with the simplest (reinstall Canary) to various registry changes. Initially it solved it, but it returned a few days later. Per Copilot, it doesn't matter because every Canary update is a whole new version, and I've certainly still been getting frequent updates. As long as you're getting updates, I wouldn't worry about it.
I learned a long time ago as system administrator to not worry about things I had no control over. I simply said the IT admin prayer when stuff like this happened - Thank God I drink. 😂
CrazyKats​ is right. It's not a matter of "worrying" about it, it's a matter of Edge support team making folks feel like they are wasting their time sending in feedback when they don't bother to respond with any type of acknowledgement.
Secondly, "every canary update" is not a "whole" new version. It's a modified version of the previous version with its inserted fixes, add-ins, or removals of whatever they are trying to change/fix.
And as CrazyKats​ has also stated, it is now being passed down to the next level versions of Edge. It is only a matter of time before it hits the public versions unless they act on it before then.
Dennis5mile
Yep this is an interesting one as it's now been at least a month or so with no acknowledgement of the issue. I reported it too and no response at all. Hopefully fixed soon. Not a real issue as it updates but more an annoyance.
It isn't a matter of worrying about it. It's a case of Feedback has been sent, no one from Edge team is acknowledging this error or offering any explanation.
It has also now made it down to the Dev Edge build.
