When trying to login to our Fortinet VPN, the login is successful and the frdsviewer package is activated to login to my Windows 10 Pro X86 Feature 22H2 system at my workplace.
Thank you for your reply, ShiJie Li! I have updated Microsoft Edge to Version 1.69 now (before yesterday's Version 111 was posted) and set MicrosoftRootStoreEnabled to NOT Configured to get it OUT of the Discussion. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. If you have extra questions about this answer, please click "Comment". If the answer is helpful, please click "Accept Answer" and kindly upvote it. Also, you can test in Edge Dev, which is now 1.36. So, you can try leaving this policy unconfigured and see whether this issue still occurs. As a result, scenarios where a user or enterprise installed additional trusted roots to the host operating system's root store should continue to work. Both Windows 10 Pro X86 and X64 Feature 22H2 systems are experiencing this issue.Īccording to the description of MicrosoftRootStoreEnabled policy, "when this policy is not set, the Microsoft Root Store or system provided roots may be used".Įven after the change, in addition to trusting the built-in roots that ship with Microsoft Edge, the browser will also query the underlying platform for-and trust-locally installed roots that users and/or enterprises installed. Everyone's productive help is greatly appreciated. We cannot change the websites as many are on the Internet and not on our Intranet.
We need to have this situation FIXED ASAP or we need knowledge of Edge Flags settings or other GPO's we haven't configured, that may reliably resolve this issue. The ADMX/ADML GPO files are in place as usual and two other Version 110 GPO's are also set to DISABLED: AutofillMembershipsEnabled and SearchFiltersEnabled (Version 109), as well as, LinkAccountEnabled and TextPreditionEnabled settings. I started noticing this after a normal Microsoft Edge update from Version 108 to the Maavailable Version 110. The problem shows itself as a "crash" of the website session after a short period, requiring a new login that many times works OK. Currently, Version 110 should use BOTH Browser and System certificate store, but we decided to start with the Browser store disabled for now. I have not tried enabling it as we have many local Printers with self-signed certificates in our systems.
We do have the "MicrosoftRootStoreEnabled" GPO setting set to DISABLED ( 0x00000000 ) in our GPO setup. However, with Microsoft Edge Version 1.63 I have experienced many "drops" from both internal on-site and off-site websites that require User-Name and Password authentication. We have been moving through the various Microsoft Edge versions for quite some time now without issues.
0 kommentar(er)
