This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 34%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Anyone using (new) Edge C (GA) & or testing the Edge Insider beta Channels, comments (bad AND good), tips, info to share, observations, suggestions/requests, issues/problems, curiosities, questions, you name it... The floor is yours...
Myself, I have run all available Insider Builds since April. And, now, running Edge C GA, as well; swapped from HTML Jan. 15th.
I am/have been very impressed with the performance. Been a bit fun adapting to some things/methods/locations/layouts/structure. Some NTML features seem missing, BUT, heaps more stuff is coming very soon. Some 'new' & different items are quite cool. It has been interesting as an Insider. And it will be interesting for people using & discovering THIS Edge. It is, well, IMHO, will be THE outstanding browser. I, strongly urge & encourage Folks to adopt it. Be prepared, though... it's very fast ��
Let's see what more detail & specifics y'all may have, will have to add here...
Anxious for your remarks, look forward to the input that can be share to everyone's benefit, of course.
The floor is yours...
Cheers,
Drew
Other issues or features related to Microsoft Edge on Windows 10
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
It Makes perfect sense Now Drew,
er... you mentioned that a flag is No Longer Needed if in the flags settings it is set to "Default" . But both of my Flags were set to default for the Grammar and Force dark mode. I had to change them to "Enable" to get them to work properly. ?
Ok , Kevin, I'll toss in my 2 cents, FWIW.
I not going to say what's the cause but, it is NOT because, Edge C is "buggy", it is not. When I 1st read your 1st note, 2 thoughts came to mind...
and
You could, also, create a test User Profile/Account, grab Edge C there & see what behavior there is in that.
Edge C should be as fast or faster than Edge HTML. My own, not much time to blink whilst loading & then fun keeping up with it 😉
I would suggest start over. Edge C is far from "buggy" & sure as heck not slow, loading or after that!
It sounds, to me, rightly or wrongly, that the install you had suffered a wee bit of corruption so to speak. Please, try it all over, again or make a dummy User account & try it there.
Check that 1909 is fully up date, too.
Edge C Download is HERE
Cheers,
Drew
I might not have worded it very well or very clearly. Default works IF the thing didn't need a flag. As long as a flag is needed or is, still, needed then, YES, it must be changed from Default to Enabled.
And sometimes can be like this example: Collections does not use a flag, anymore, in Dev. Dark, still, does.
However, Edge C GA, there is no flag for Collections ... with or without a flag, Collections hasn't made it to GA, yet.
Does it, still, make sense? LOL They come & they go, a way to test things before embedding in the browser.
Cheers,
Drew
Now I got it, It's perfectly clear now 🤔 (LOL) Thanks Drew.
