Oct 20 2019 05:19 PM
it's annoying and didn't happen before the newest update
Oct 20 2019 06:31 PM
Oct 20 2019 07:59 PM
Oct 21 2019 12:41 AM
Okay so based on what you say, If all of the websites are shown as insecure, the first logical thing that comes to mind is that the Trusted Root Certificate Authorities are probably missing/deleted.
https://www.thewindowsclub.com/manage-trusted-root-certificates-windows
Though it could also be a 3rd party extension or Flags. so you could try resetting all the flags to their default values and temporary disabling any 3rd party extension.
Oct 21 2019 11:24 AM
@pneenkoalabear I'm getting a similar behavior from Google Chrome, so I assume it's not specific to Edge, but to Chromium itself.
Oct 21 2019 12:30 PM
Oct 21 2019 12:45 PM
@HotCakeX I'm using Chrome 77.0.3865.120. I don't have the dev Edge on that machine to confirm the Edge behavior, but I can confirm that it's happening to Chrome. It does not happen to all pages nor all the time, but I saw it happen a couple of time... I see that "exclamation warning message" when starting to load a page (maybe for 1 or 2 seconds) and it goes away when the page loads.
Oct 21 2019 12:52 PM
Oct 21 2019 01:15 PM
Oct 21 2019 01:21 PM
Oct 21 2019 01:32 PM
Oct 21 2019 01:41 PM - edited Oct 21 2019 01:44 PM
Thank you,
Windows 10 accounts extension is installed by your organization,
https://www.ghacks.net/2017/08/17/microsoft-publishes-windows-10-accounts-chrome-extension/
"The extension works with Azure Active Directory services right now, e.g. Office 365, Exchange Online or OneDrive for Business, and provides Chrome users on Windows 10 with options to sign in to resources automatically when they use Chrome and are signed in to a Microsoft Account on Windows 10."
Last updated 2017
https://chrome.google.com/webstore/detail/windows-10-accounts/ppnbnpeolgkicgegkbkbjmhlideopiji
maybe it is malfunctioning somehow
Oct 23 2019 11:47 PM
Oct 24 2019 12:32 AM - edited Oct 24 2019 12:54 AM
SolutionI know! An update set #enable-mark-http-as in the flags to Enabled (mark with a grey triangle icon) from Disabled.
I don't think it should have a grey triangle or be actively dangerous. I think an 'i' in an outlined circle is sufficient. FYI setting it to Enabled, Default and Disabled all set it to Enabled (mark with a Not Secure warning and dangerous on form edits). I still set it to disabled to tell Microsoft and Google (I also use Chrome). I support making HTTPS less prominent though.
Oct 24 2019 02:18 AM
@pneenkoalabear wrote:
I don't have that extension. It's defs an issue on Chromium's side as @cbomtempo said
And there is no Clear instruction as to how to reproduce it?
Oct 24 2019 02:22 AM
@pneenkoalabear wrote:I know! An update set #enable-mark-http-as in the flags to Enabled (mark with a grey triangle icon) from Disabled.
I don't think it should have a grey triangle or be actively dangerous. I think an 'i' in an outlined circle is sufficient. FYI setting it to Enabled, Default and Disabled all set it to Enabled (mark with a Not Secure warning and dangerous on form edits). I still set it to disabled to tell Microsoft and Google (I also use Chrome). I support making HTTPS less prominent though.
Do you still see your problem after disabling that flag? how about setting it to default?
Oct 24 2019 12:32 AM - edited Oct 24 2019 12:54 AM
SolutionI know! An update set #enable-mark-http-as in the flags to Enabled (mark with a grey triangle icon) from Disabled.
I don't think it should have a grey triangle or be actively dangerous. I think an 'i' in an outlined circle is sufficient. FYI setting it to Enabled, Default and Disabled all set it to Enabled (mark with a Not Secure warning and dangerous on form edits). I still set it to disabled to tell Microsoft and Google (I also use Chrome). I support making HTTPS less prominent though.