Follow us on X (Twitter)  Like us on Facebook  Connect with us on LinkedIn  Subscribe to our YouTube Channel  Subscribe to our WhatsApp Group

Almost four weeks after releasing Microsoft Edge version 101 to the stable channel, Microsoft has now released Edge version 102. The latest build version 102.0.1245.30 in the stable channel adds no new features. But the latest version is packed with four new policies and the latest security updates of the Chromium project. For a detailed list of changes, continue reading further.


Microsoft Edge 102 adds new policies


What's new and improved in Microsoft Edge 102.0.1245.30

New policies

  • AllHttpAuthSchemesAllowedForOrigins - Set this policy to specify which origins allow all the HTTP authentication schemes Microsoft Edge supports regardless of the AuthSchemes policy.

    Up to 1,000 exceptions can be defined in AllHttpAuthSchemesAllowedForOrigins. Wildcards are allowed for the whole origin or parts of the origin. Parts include the scheme, host, or port.

  • OutlookHubMenuEnabled - This policy is used to manage access to the Outlook menu from Microsoft Edge. If you enable or don't configure this policy, users can access the Outlook menu. If you disable this policy, users can't access the Outlook menu.

  • NetworkServiceSandboxEnabled - This policy controls whether or not the network service process runs sandboxed.

    If this policy is enabled, the network service process will run sandboxed. If this policy is disabled, the network service process will run unsandboxed.

    This leaves users open to additional security risks related to running the network service unsandboxed. If this policy is not set, the default configuration for the network sandbox will be used.

    This may vary depending on the Microsoft Edge release, currently running field trials, and platform. This policy is intended to give enterprises flexibility to disable the network sandbox if they use third-party software that interferes with the network service sandbox.

  • UserAgentClientHintsGREASEUpdateEnabled - The User-Agent GREASE specification recommends the inclusion of additional GREASE characters beyond the current semicolon and space, and recommends that the arbitrary version number be varied over time.

    When enabled, the User-Agent Client Hints GREASE Update feature aligns the User-Agent GREASE algorithm with the latest version from the specification. The updated specification may break some websites that restrict the characters that requests may contain.

    If this policy is enabled or not configured, the User-Agent GREASE algorithm from the specification will be used. If the policy is disabled, the prior User-Agent GREASE algorithm will be used.



Security updates

  • CVE-2022-30128 - Microsoft Edge (Chromium-based) Elevation of Privilege Vulnerability
  • CVE-2022-30127 - Microsoft Edge (Chromium-based) Elevation of Privilege Vulnerability
  • CVE-2022-26905 - Microsoft Edge (Chromium-based) Spoofing Vulnerability


Have a question? Or, a comment? Let's Discuss it below...


Thank you for visiting our website!

We value your engagement and would love to hear your thoughts. Don't forget to leave a comment below to share your feedback, opinions, or questions.

We believe in fostering an interactive and inclusive community, and your comments play a crucial role in creating that environment.