FYI: Edge 105.0.1343.25 refuse to launch after update

Topic

New Reply

[Susan Bradley]

Microsoft has released Edge 105.0.1343.25 (a new branch) on September 1, 2022. But I got feedback from German blog readers, that the browser can’t start after update on distinct Windows builds. The reason isn’t know yet – there is no workaround till yet.
https://borncity.com/win/2022/09/02/microsoft-edge-105-0-1343-25-1-september-2022/

Moderator edit to fix link

Solution from below:

Just verified deleting the key MetricsReportingEnabled under
Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge

fixes the issue

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

• This topic was modified 1 year, 1 month ago by Susan Bradley. Reason: Adding solution

5 users thanked author for this post.

cyberSAR, dgc-art, lmacri, Microfix, geekdom

Reply | Quote

Replies

Link here:

https://borncity.com/win/2022/09/02/microsoft-edge-105-0-1343-25-1-september-2022/

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

Microfix

Reply | Quote

Don’t use it although failed to restart on two W10 installs x86 and x64.
Tried
System Restart try opening Edge (fail)
Modify/ Repair (fail)
Edge won’t start although seems updated and installed
Now back to a better browser 🙂

No problem can be solved from the same level of consciousness that created IT- AE

Reply | Quote

Edge Webview2 Runtime version not in sync with updated Edge.
Previous versions have followed the edge version installed…someone forget to?

No problem can be solved from the same level of consciousness that created IT- AE

1 user thanked author for this post.

cyberSAR

Reply | Quote

I have webview2 105.0.1343.25 and Edge launching fine.

Reply | Quote

Can confirm my versions of Edge and Webview2 are the same as @microfix and no launch

Never Say Never

1 user thanked author for this post.

Microfix

Reply | Quote

What is your default browser?  Do you remember if you had any extensions or home pages set in Edge?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Default is firefox. Use Brave often. Nothing special with edge but ublock origin and blank page as home. startup boost and garbage turned off.

Just did repair of edge and webview2 but still same versions

Never Say Never

Reply | Quote

What antivirus?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

ESET on Win11 Defender on Win10. My win10 system has version 105… of edge and webview2 and not launching either. Almost nothing installed on the win10 system as it’s a test machine. Curiouser and curiouser. But yes, let MS encrypt my drive! What could go wrong????

Never Say Never

Reply | Quote

Updates to Edge do not encrypt drives.  There’s something at play here because I truly have been checking various machines in the office and mine at home and can’t repro this.  Let me see if I can get eyeballs from MS on this.

To confirm:  on the Windows 10 that has default defender, no extensions, en-us as installed language, bog standard yadda yadda?

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

cyberSAR

Reply | Quote

Sorry just a snarky comment in regards to the other thread. Just verified deleting the key MetricsReportingEnabled under
Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge\

allows Edge to start without even rebooting. That’s the only one I had. Others have had two from what I’ve read.

Never Say Never

1 user thanked author for this post.

geekdom

Reply | Quote

What registry key was under there?

 

https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#metricsreportingenabled

Not supported since Edge 88?

Was it enabled or disabled?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Yes I saw it listed as deprecated. MetricsReportingEnabled was set to 0. Tried changing to 1, reboot, still wouldn’t open. Deleted key and edge opened immediately without even a reboot

Never Say Never

1 user thanked author for this post.

Microfix

Reply | Quote

So my take after years of following patching issues:

They never test on crusty machines.  Deprecated settings are not in their mind when testing/rolling out stuff.  Note this is not new even after they laid off the testing staff.  They NEVER have tested stuff well on crusty boxes, they always built fresh machines to test.

https://admx.help/?Category=EdgeChromium&Policy=Microsoft.Policies.Edge::MetricsReportingEnabled

Interesting that it would cause it to not start, I wonder if it’s interacting with the new “WASM support for Enhanced security mode”

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Well my Win11 is a clean install performed beginning of August using an iso created in January. Boy that’s a short time to get crusty! 🙂

Never Say Never

1 user thanked author for this post.

Microfix

Reply | Quote

Crusty = any registry keys/any settings/anything not from a fresh clean install.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

cyberSAR

Reply | Quote

Well mine was crusty from the first reboot 🙂

Can’t blame MS for this one. All on me using an older version of O&O Shutup

Never Say Never

Reply | Quote

Actually this is a great thread showcasing diagnosis/issues with updates and debugging.

1. determine if others are seeing it as well
2. determine commonality
3. rule out extensions, antivirus
4. review unique settings

And then too often… recall what you’ve installed

Thank you CyberSar for the heavy lifting and diagnosis here!

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

cyberSAR

Reply | Quote

Same here CyberSAR, exported then removed MetricsReportingEnabled key. Edge worked so then uninstalled the previous version of edge Webview2 Runtime. No problems. Systeminternals autoruns excursion and a restart put edge to sleep again.

No problem can be solved from the same level of consciousness that created IT- AE

2 users thanked author for this post.

geekdom, cyberSAR

Reply | Quote

105 is launching fine here with no issues.  Is it a localization issue?  105 includes the new

Johnathan Norman on Twitter: “Edge 105 will release to stable this week and include WASM support for Enhanced Security Mode on Windows x64 platforms. So far millions of users have tried jitless browsing and seem to enjoy it, despite the claims it would be too slow. 1/” / Twitter

 

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Failing to launch on my Win11 system. Doesn’t even show up in task manager. I don’t use it but many of my clients do. Guess this will be my labor day weekend!

Never Say Never

1 user thanked author for this post.

Microfix

Reply | Quote

Launch fine on my Windows 10 Pro 21H2 with AUG. updates.

Reply | Quote

Saw this posted as a workaround. Seems easier and faster than restoring old version.

https://answers.microsoft.com/en-us/microsoftedge/forum/all/edge-wont-run-after-the-update-104105/e7bbd14e-4221-443c-bbea-97edbc880451

All you have to do is go to regedit via Windows key + R and search for MetricsReportingEnabled under Edit -> Search . Delete the 1-2 entries and the Edge will start again.

Never Say Never

3 users thanked author for this post.

geekdom, Microfix, b

Reply | Quote

Before seeing this useful thread (and thinking the issue was just me), in frustration I did a forced uninstall of Edge (uninstall button was greyed out in apps) using Revo Uninstaller and via Brave, downloaded Edge and reinstalled it. Now on version 105.0.1343.25 and it is opening fine on Windows 10 21H2 Pro with Norton 360.

Reply | Quote

OK Figured out what caused it on my machines. I deleted the value MetricsReportingEnabled and it started working.
Deleted the key Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge\

Ran an older version of O&O and it created the key with MetricsReportingEnabled and wouldn’t open.

Deleted the key again and ran the new version of O&O and it recreated the key without MetricsReportingEnabled and everything is working.

I use O&O as it is a quick way to set a lot of settings.

Never Say Never

4 users thanked author for this post.

oldfry, Lars220, lmacri, PKCano

Reply | Quote

O&O is a company with 22 software products.

Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

Reply | Quote

@b SHUTUP 🙂

Never Say Never

1 user thanked author for this post.

b

Reply | Quote

Gentlemen…. it’s Friday.  Give us all a break.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

cyberSAR

Reply | Quote

We just kidding! No offense intended!

Never Say Never

1 user thanked author for this post.

Susan Bradley

Reply | Quote

I wish I had read this post yesterday as that would have saved me lots of time.  THANKS!

Reply | Quote

https://twitter.com/seanontwt/status/1565846234719727622?s=21&t=eBzfEuTRNym36LQT-H8-og

Microsoft has been notified.  “Fix is in the next Stable update (next week). Deleting the key (which is an obsolete policy) is a sufficient workaround.”

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

lmacri

Reply | Quote

Just got notified that my post was removed because I was “rude”. Not sure which one it was but was never my intention. Don’t think @b took it as rude when I replied “SHUTUP” I was JOKING! If that was rude so be it. Maybe I don’t belong.

Never Say Never

Reply | Quote

Sorry, I restored it after a kneejerk reaction to you not including the 10++.

Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

Reply | Quote

Apology accepted. Maybe I’m wrong, but I thought 🙂 might have tipped you off! 🙂

Never Say Never

Reply | Quote

cyberSAR wrote:

Deleted the key again and ran the new version of O&O and it recreated the key without MetricsReportingEnabled and everything is working.

So glad I saw this before I opened Edge to have it automatically update and then have problems. Off hand, I have no idea if O&O is on the latest verson.

Ahh…I updated O&O and Edge updated and everything seems fine. (I have no idea though why Edge claims vertical tabs are NEW to this latest version….I’ve had them for some time).

Reply | Quote

Doing updates and just noticed Edge is updating from 105.0.1343.25 to 105.0.1343.27

Don’t have time to dig in but maybe they are fixing the issue with MetricsReportingEnabled

Never Say Never

3 users thanked author for this post.

Microfix, Just another Forum Poster, b

Reply | Quote

Just updated to Edge 105.0.1343.27 and can personally verify that, if the MetricsReportingEnabled DWORD exists in the registry, it still will not start!

Not sure why they issued a new version so quickly, but it doesn’t fix that particular problem (or maybe it’s suppose to but doesn’t — like so many of the other “fixes” they’ve issued in the last year or so )

1 user thanked author for this post.

geekdom

Reply | Quote

Earlier updated to 105.0.1343.27 from 105.0.1343.25 and the MetricsReportingEnabled DWORD is not there in the registry on two systems x64 and x86 as I removed them when on 105.0.1343.25
As for the rapid release, it’s to fix CVE-2022-3075 an inherant cluster that’s ‘in the wild’ now.
Have a Crusty installation per chance 🙂

No problem can be solved from the same level of consciousness that created IT- AE

Reply | Quote

Microfix wrote:

Have a Crusty installation per chance 🙂

Nope, I removed that entry back on Sep 1st when edge wouldn’t start after the 105.0.1343.25 update!

When I saw @CyberSAR’s speculation that 105.0.1343.27 “might‘ have fixed it, I couldn’t resist manually adding it back in to see if it still caused the same problem.

BTW, I just got a call from my Uncle a few hours ago because his Edge wasn’t starting.

I remoted into his PC to check his registry and, sure enough, it had the MetricsReportingEnabled DWORD entry in it (the value was set to 0) and, since he’s never used O&O Shutup or any other similar S/W, it must be a “common” entry that was put there by an Edge installation prior to Edge version 88 that MS simply never got around to actually deleting after it was superseded.

So the new version hasn’t fixed whatever code in Edge causes this and MS still hasn’t included any code in Edge installer to check for and remove this superseded entry.

Reply | Quote

I believe they were fixing a security issue in Chrome, not fixing the metrics registry issue.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Alex5723

Reply | Quote

[Susan Bradley]

gborn wrote:

Microsoft has released Edge 105.0.1343.25 (a new branch) on September 1, 2022. But I got feedback from German blog readers, that the browser can’t start after update on distinct Windows builds. The reason isn’t know yet – there is no workaround till yet.
https://borncity.com/win/2022/09/02/microsoft-edge-105-0-1343-25-1-september-2022/

Moderator edit to fix link

Solution from below:

Just verified deleting the key MetricsReportingEnabled under
Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge

fixes the issue

• This topic was modified 1 year, 1 month ago by Susan Bradley. Reason: Adding solution

Susan, thanks for your added solution and your support (also with the Edge developers) – I got a bit lost the last days during that many changes 😉 Had not the time to update my post here and focussing me to keep the linked blog post up to date.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

Reply | Quote

It’s now September 22.  I just stumbled across this problem a couple of days ago.  I now have 105-0.1343.42 and still have the problem, but I don’t even have

Computer HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge

certainly not

MetricsReportingEnabled

Reply | Quote

Try searching under HKEY_USERS. I actually started doing that as it was faster and fixed all users.

Never Say Never

Reply | Quote

I don’t appear to have MetricsReportingEnabled anywhere in the registry.

Could these differences possibly be because I have Windows 10 Home?

Reply | Quote

Could be another issue. Have you tried a repair/reset or even install of Edge over the top?

Never Say Never

1 user thanked author for this post.

lmacri

Reply | Quote

Running Edge Version 105.0.1343.50. No problems.

Reply | Quote

Bob Coleman wrote:

… I now have 105-0.1343.42 and still have the problem, but I don’t even have Computer HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge certainly not MetricsReportingEnabled

Hi Bob Coleman:

I’m also running the current MS Edge v105.0.1343.50 (rel. 22-Sep-2022) – see the release notes <here> for the stable release channel of MS Edge.

If you search your registry for MetricsReportingEnabled and cannot find that value at under the HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge or the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge registry keys then it’s unlikely that your problem launching Edge has anything to do with the issue being discussed in this thread. I believe the majority of users who encountered this problem in early September 2022 were using an outdated version of the O&O Shutup++ privacy tool that was incorrectly re-creating the deprecated MetricsReportingEnabled value in the registry. Once they deleted those registry values and updated O&O Shutup++ they had no further issues launching MS Edge. According to the 03-Sep-2022 BleepingComputer article Microsoft Edge 105 Won’t Start Due to Old Group Policy – How to Fix there are outdated versions of other privacy tools like PrivaZilla that have the same problem and will also re-create the deprecated MetricsReportingEnabled value in the registry.

Microsoft agent Eric-SE posted on 09-Sep-2022 in the MS Answers thread Edge Won’t Run After the Update 104=>105 that the problem with MetricsReportingEnabled was fixed in MS Edge v105.0.1343.33 (rel. 08-Sep-2022), although I can’t confirm since the release notes <here> for v105.0.1343.33 only say “Fixed various bugs and performance issues“.

The Microsoft support article What To Do If Microsoft Edge Isn’t Working includes instructions on how to repair MS Edge that might be helpful. If you need to reinstall see Step # 4 of Troubleshooting Tips for Installing and Updating Microsoft Edge.
———-
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.2006 * Firefox v105.0.0 * MS Edge v105.0.1343.50 * Microsoft Defender v4.18.2207.7-1.1.19600.3 * Malwarebytes Premium v4.5.14.210-1.0.1767

Reply | Quote

lmacri wrote:

Microsoft agent Eric-SE posted on 09-Sep-2022 in the MS Answers thread Edge Won’t Run After the Update 104=>105 that the problem with MetricsReportingEnabled was fixed in MS Edge v105.0.1343.33 (rel. 08-Sep-2022), although I can’t confirm since the release notes for v105.0.1343.33 only say “Fixed various bugs and performance issues“.

Don’t know about Edge 105.0.1343.33 but, after “manually” adding the MetricsReportingEnabled DWORD back to my registry, I can confirm it no longer causes problems running Edge 105.0.1343.42.

1 user thanked author for this post.

lmacri

Reply | Quote

I guess I have a different issue than the one taking up most of this thread though it certainly fits Edge Refuses to Launch after update though I no longer know update of what.

I tried most of the things mentioned above including Repair from Apps in Settings and force uninstall using Revo Uninstaller followed by reinstall.

I even did a repair reinstall of windows which didn’t help.

However almost as an accidental side effect of the repair reinstall, I discovered that while Edge doesn’t work in the user account that I normally use it does work in another user account that I seldom use.

This turns out to be true both before and after the repair reinstall.

At this point, I have no idea why Edge works in one account and not the other.

Before anybody asks, both accounts have administrator rights.

The account where Edge works is very close to a “plain vanilla” account whereas the other one is much more customized to my liking.  I guess I must have done something in the latter account that’s interfering with Edge, but I currently have no idea what.

I don’t know how long this issue has actually been present.  I seldom use Edge, but it did work in my normally used account at some point.

 

 

Reply | Quote

I’ve solved my problem which was self inflicted.

At one time, I experimented with moving the Edge User Data to a partition other than the Windows partition by creating a User Data folder on the other partition and a junction User Data in C:\Users\[me]\Apdata\Local\Microsoft\Edge pointing to User Data on the other partition.  It worked.  Then I changed by mind, for now at least,  and removed both my User Data folder and the junction.  I’m pretty sure that was OK also, but somehow I ended up with the junction pointing to a nonexisting folder.  I don’t know when or how.  Perhaps I inadvertently restored an image of the Windows partition containing the junction after I had removed the target folder.  Anyway, I removed the junction and Edge now works.

 

1 user thanked author for this post.

Alex5723

Reply | Quote

Updated to Edge Version 106.0.1370.34 (Official build) (64-bit) and the same thing (no restart) happened .. used same solution (deleting the key MetricsReportingEnabled) and all is good. FYI.

Reply | Quote

CBA wrote:

Updated to Edge Version 106.0.1370.34 (Official build) (64-bit) and the same thing (no restart) happened .. used same solution (deleting the key MetricsReportingEnabled) and all is good.

Hi CBA:

I updated to MS Edge Version 106.0.1370.34 and then searched my Windows registry for “MetricsReportingEnabled”, and like Alex5723, I didn’t find any Key, Value or Data with that deprecated policy in my registry. The 03-Sep-2022 BleepingComputer article Microsoft Edge 105 Won’t Start Due to Old Group Policy – How to Fix notes that there are some Windows optimization tools like PrivateZilla and outdated versions of O&O Shutup++ that will incorrectly re-create these MetricsReportingEnabled registry entries. Do you use any similar utilities on your computer?
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.2006 * Firefox v105.0.1 * MS Edge v106.0.1370.34 * Microsoft Defender v4.18.2207.7-1.1.19600.3 * Malwarebytes Premium v4.5.14.210-1.0.1772

1 user thanked author for this post.

CBA

Reply | Quote

CBA wrote:

used same solution (deleting the key MetricsReportingEnabled) and all is good

I have Edge installed and updated yet I don’t have Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge registry entry.

Reply | Quote

Alex5723 wrote:

I have Edge installed and updated yet I don’t have Computer\HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge registry entry.

This is what I have after deleting the key MetricsReportingEnabled.  Go figure!

 

1 user thanked author for this post.

lmacri

Reply | Quote

CBA wrote:

This is what I have after deleting the key MetricsReportingEnabled. Go figure!

Notice how the value for most of them is set to 0.

They represent the specific Edge Group Policy settings you’ve “disabled” (i.e. if it’s set to 0, it’s not enabled/allowed) and I also have most of those same ones disabled on my PC.

@Alex5723 doesn’t have the Edge registry key because all his Edge Group Policy settings are likely set as “not configured”.

3 users thanked author for this post.

Alex5723, lmacri, CBA

Reply | Quote

lmacri wrote:

O&O Shutup++

I noticed that article (back then) and, yes, I have the current O&O Shutup++ installed plus a few GP Edge settings activated.  The main point now is that I found the culprit and it works.  That said, I rarely use Edge .. but it should work regardless.

Reply | Quote

Just another Forum Poster wrote:

They represent the specific Edge Group Policy settings you’ve “disabled” (i.e. if it’s set to 0, it’s not enabled/allowed) and I also have most of those same ones disabled on my PC.

This sounds likely .. as I have pretty much everything “disabled” via O&O Shutup++ (see .jpg) and settings in GP.  Thanks for the insight!

Reply | Quote