{"id":26916,"date":"2022-10-10T11:42:09","date_gmt":"2022-10-10T09:42:09","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=26916"},"modified":"2022-10-10T11:42:09","modified_gmt":"2022-10-10T09:42:09","slug":"edge-106-0-1370-37-with-bug-fixes-failed-start-issue-not-fixed","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/10\/10\/edge-106-0-1370-37-with-bug-fixes-failed-start-issue-not-fixed\/","title":{"rendered":"Edge 106.0.1370.37 with bug fixes; failed start issue not fixed"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" title=\"Edge\" style=\"margin: 0px 10px 0px 0px\" border=\"0\" alt=\"Edge\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2020\/01\/Edge.jpg\" width=\"65\" align=\"left\" height=\"67\">[<a href=\"https:\/\/www.borncity.com\/blog\/2022\/10\/07\/edge-106-0-1370-37-mit-bug-fixes-startprobleme-behoben\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]Short addendum: Microsoft has updated the Edge browser in the stable channel to version 106.0.1370.37 on October 6, 2022. Is a bug fix update that is supposed to fix bugs in the Edge 106.0.1370.34 released on October 3, 2022. But I got reports, that the Edge start problem, observed in Edge 106.0.1370.34, is still present &#8211; there is a workaround known. Here is a brief overview of the current version and Edge 106.0.1370.34.<\/p>\n<p><!--more--><\/p>\n<h2>Edge Version 106.0.1370.37<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg05.met.vgwort.de\/na\/97ffd4a13c9c4bc8aff519de9ff1b9eb\" width=\"1\" height=\"1\">Microsoft had to upgrade the previous Edge version 106.0.1370.34 after just three days. In terms of \"best practice\", the <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnote-stable-channel\">release notes<\/a> from Redmond don't really give anything away. It only says: <em>Fixed various bugs and performance issues.<\/em><\/p>\n<h3>Locking Back: Edge 106.0.1370.3 policies changes<\/h3>\n<p>Within the <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnote-stable-channel\" target=\"_blank\" rel=\"noopener\">release notes<\/a> for Edge 106.0.1370.34, Microsoft lists the following new policies that are introduced starting with this version:&nbsp; <\/p>\n<ul>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#efficiencymodeenabled\" target=\"_blank\" rel=\"noopener\">EfficiencyModeEnabled<\/a> &#8211; Efficiency mode is set to enabled.\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#efficiencymodeonpowerenabled\" target=\"_blank\" rel=\"noopener\">EfficiencyModeOnPowerEnabled<\/a> &#8211; enables efficiency mode when the device is connected to a power source\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#internetexplorerintegrationalwaysuseoscapture\" target=\"_blank\" rel=\"noopener\">InternetExplorerIntegrationAlwaysUseOSCapture<\/a> &#8211; Always use the OS capture engine to avoid tab capture problems in Internet Explorer mode.<\/li>\n<\/ul>\n<p>In addition, Microsoft declares the following policies as deprecated  <\/p>\n<ul>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#newsmartscreenlibraryenabled\" target=\"_blank\" rel=\"noopener\">NewSmartScreenLibraryEnabled<\/a> &#8211; Enable new SmartScreen library &#8211; the library is now enabled by default\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#shadowstackcrashrollbackbehavior\" target=\"_blank\" rel=\"noopener\">ShadowStackCrashRollbackBehavior<\/a> &#8211; Configure ShadowStack crash rollback behavior<\/li>\n<\/ul>\n<p>The following two policies are now obsoleted:  <\/p>\n<ul>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#outlookhubmenuenabled\" target=\"_blank\" rel=\"noopener\">OutlookHubMenuEnabled<\/a> &#8211; Allow users to access the Outlook menu.\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#edgediscoverenabled\" target=\"_blank\" rel=\"noopener\">EdgeDiscoverEnabled<\/a> &#8211; Discover-Feature in Microsoft Edge<\/li>\n<\/ul>\n<p><em><\/em>Edge 106.0.1370.34 comes also with two slight Feature Updates: <em>More reliable web defense<\/em> and <em>Increased Work Results in the Microsoft Edge addr<\/em>, detailed within the release notes. <\/p>\n<h2>Edge won't launch<\/h2>\n<p>Shortly after release of Edge 106.0.1370.34 I got a user <a href=\"https:\/\/www.borncity.com\/blog\/2022\/10\/06\/edge-106-0-1370-3\/#comment-133477\" target=\"_blank\" rel=\"noopener\">report<\/a> from German blog reader Daniela, that the browser won't launch after update. <\/p>\n<blockquote>\n<p>Since Tuesday (Oct. 4, 2022) we have had calls from customers again, where the problem, addressed within the blog post&nbsp; <a href=\"https:\/\/borncity.com\/win\/2022\/09\/02\/microsoft-edge-105-0-1343-25-1-september-2022\/\">Microsoft Edge 105.0.1343.25 (September 1, 2022) \u2013 fail to start after update<\/a>, occurs again after the latest update. Anyone else have similar experiences?<\/p>\n<\/blockquote>\n<p>Within my German blog post I addressed an issue, caused by changed policies. Users with the old <em>MetricsReportingEnabled <\/em>policy set were affected by this startup issue at the time. Susan Bradley had suggested in <a href=\"https:\/\/twitter.com\/SBSDiva\/status\/1566090013372125186\">that tweet<\/a> that the O&amp;Oshutup tool had set this registry entry &#8211; I can't verify it. The fix linked in the old article, which was also confirmed by Microsoft developers, was: <\/p>\n<blockquote>\n<p>Just run the registry editor and let it search for the registry entries with MetricsReportingEnabled. Delete the affected entries from the registry.<\/p>\n<\/blockquote>\n<p>To do this, run the registry editor <em>regedit.exe<\/em> as a normal user (do not use <em>Run as administrator<\/em>) and then go to the key: <\/p>\n<pre><code>HKEY_CURRENT_USER\\SOFTWARE\\Policies\\Microsoft\\Edge\\ <\/code><\/pre>\n<p>There you should then delete the M<em>etricsReportingEnabled<\/em> entry. After this entry has been removed, the updated Edge browser should also start again. If this does not help, try the same in the registry path: <\/p>\n<pre><code>HKEY_Local_Machine\\SOFTWARE\\Policies\\Microsoft\\Edge\\ <\/code><\/pre>\n<p>where the <em>MetricsReportingEnabled <\/em>entry is to be deleted. Here it is important to call the registry editor regedit.exe via context menu <em>Run as administrator<\/em>, otherwise the entry cannot be deleted. <\/p>\n<p>After publishing the German edition of this article, I got feedback from readers, that the issue still occur in Edge 106.0.1370.37, so the registry fix is necessary, if affected.&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]Short addendum: Microsoft has updated the Edge browser in the stable channel to version 106.0.1370.37 on October 6, 2022. Is a bug fix update that is supposed to fix bugs in the Edge 106.0.1370.34 released on October 3, 2022. But &hellip; <a href=\"https:\/\/borncity.com\/win\/2022\/10\/10\/edge-106-0-1370-37-with-bug-fixes-failed-start-issue-not-fixed\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[872,463,22],"tags":[320,47,195],"class_list":["post-26916","post","type-post","status-publish","format-standard","hentry","category-browser","category-issue","category-update","tag-edge","tag-issue","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/26916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=26916"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/26916\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=26916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=26916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=26916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}