Edge Beta / Dev / Canary not starting

[Strubi99]

As of this morning Edge Beta stopped working: if I double click on the icon nothing happens.

I tried intalling Dev and Canary but the same thing happens.

Only the stable edition keeps working.

I'm running Windows 10 20H2.

[#2]

Hi,

I've been seeing this behavior since updating to version 105.0.1343.25 (stable). I am running Windows 10 21H2 (build 19044.1949). I don't have the MetricsReportingEnabled registry key. I am seeing not seeing this behavior on my Windows 11-base machine.

In my case, Edge is terminating due to an access violation (0xc0000005) that happens in msedge.dll. Here is the stack trace obtained from the crash dump:

000000e0`c15fe5b0 00007ffa`99fb76b0 : aaaaaaaa`aaaaaaaa aaaaaaaa`aaaaaaaa aaaaaaaa`aaaaaaaa aaaaaaaa`aaaaaaaa : msedge!policy::FilterSensitivePolicies+0x2dd
000000e0`c15fe740 00007ffa`9a3cd97e : 00000ab0`002f52f8 00000ab0`002f52e0 00000000`00000000 000000e0`c15fe900 : msedge!policy::PolicyLoaderWin::LoadChromePolicy+0xd6
000000e0`c15fe860 00007ffa`9a3c7de6 : 00005224`878514bd 00000000`00000108 00000ab0`0024d818 00007ffa`981c6976 : msedge!policy::PolicyLoaderWin::Load+0x1ee
000000e0`c15fe980 00007ffa`9a3c7f83 : 000000e0`c15fea90 00007ffa`9a3cd74e 00000000`00000108 00000ab0`0024ea00 : msedge!policy::AsyncPolicyLoader::InitialLoad+0xa2
000000e0`c15fe9e0 00007ffa`9ab1da47 : 00005224`8785147d 00000000`00000020 00000000`00000000 00007ffa`a325dd38 : msedge!policy::AsyncPolicyProvider::AsyncPolicyProvider+0x8d
000000e0`c15fea40 00007ffa`9ab1d799 : 00000ab0`00260140 00007ffa`97c84dd1 00000000`00000002 00000ab0`0024da00 : msedge!policy::ChromeBrowserPolicyConnector::CreatePlatformProvider+0xf3
000000e0`c15feae0 00007ffa`99fb45f4 : 00005224`878517dd aaaaaaaa`aaaaaaaa 00005224`8785169d aaaaaaaa`aaaaaaaa : msedge!policy::ChromeBrowserPolicyConnector::CreatePolicyProviders+0x59
000000e0`c15feb50 00007ffa`9964beef : 00000000`00000000 00007ffa`981a8b3a 01d8be85`36d90437 00000000`00000000 : msedge!policy::BrowserPolicyConnectorBase::GetPolicyService+0x5a
000000e0`c15febf0 00007ffa`99fb23ca : 000000e0`c15ff3b0 00007ffa`993b8a96 aaaaaaaa`aaaaaa01 002f4640`857c1a05 : msedge!ChromeFeatureListCreator::CreatePrefService+0xe1
000000e0`c15fece0 00007ffa`9a1f7db8 : 000000e0`c15fee58 00000000`ffffffff 000000e0`c15fee58 000000e0`c15fee90 : msedge!ChromeFeatureListCreator::CreateFeatureList+0x64
000000e0`c15fed50 00007ffa`9964ab18 : aaaaaaaa`aaaaaaaa 00007ffa`99a9c50b 00004c12`002bc000 aaaaaaaa`aaaaaaaa : msedge!ChromeMainDelegate::PostEarlyInitialization+0xe8
000000e0`c15fedc0 00007ffa`9964a89c : 00000000`00000011 000000e0`c15fef50 00000ab0`00260170 000000e0`c15feff0 : msedge!content::ContentMainRunnerImpl::RunBrowser+0x14e
000000e0`c15fef00 00007ffa`99e570d9 : 00000000`00000080 00005224`8785125d aaaaaaaa`aaaaaaaa 00000004`aaaaaa01 : msedge!content::ContentMainRunnerImpl::Run+0x31c
000000e0`c15ff040 00007ffa`97fd3ef3 : 000000e0`c15ff300 00004c12`00244230 00007ff6`14580000 00000000`00000009 : msedge!content::ContentMain+0x296
000000e0`c15ff280 00007ff6`146820de : 00000000`c15ff400 00007ffa`97fd3bc0 00004c12`002741e0 00004c12`00268330 : msedge!ChromeMain+0x333
000000e0`c15ff490 00007ff6`146174a7 : 00000000`00000000 00000000`00000000 00000000`00000000 00004c12`00264100 : msedge_exe!MainDllLoader::Launch+0x406
000000e0`c15ff730 00007ff6`14642962 : 00000000`00000000 00007ff6`146429d9 00000000`00000000 00000000`00000000 : msedge_exe!wWinMain+0x3db
000000e0`c15ffc30 00007ffb`20ab7034 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msedge_exe!__scrt_common_main_seh+0x106
000000e0`c15ffc70 00007ffb`22aa26a1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
000000e0`c15ffca0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

The issue seems to be originating in an invalid pointer dereference. Have a look at this:

ExceptionAddress: 00007ffa99fb7f9a (msedge!policy::FilterSensitivePolicies+0x00000000000002dd)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000004
Attempt to read from address 0000000000000004

The value that's in parameter 1 (0x0000000000000004) that is being passed into the policy::FilterSensitivePolicies() function is obviously not a valid address. Pointer dereferencing thus fails, subsequently triggering an access violation. My guess is that an invalid value is being passed to said function, in the second parameter.

[#3]

Nope. The key was already absent.

[#4 · Accepted solution]

FIXED!!
I scanned the registry for 'MetricsReportingEnabled'. It appeared on my PC under Edge two times.
1. [Computer\HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge\]
2. [Computer\HKEY_USERS\S-1-5-21-3783096567-2060243791-1526209860-
1001\Software\Policies\Microsoft\Edge\]
Deleted both and now I'm happy again.

[#5]

@Strubi99 

As of yesterday with a clean install of Windows 11 I can confirm Edge stops working after updating from v90 to 105. Did another clean install this morning and the same thing.

[#6]

Tried this and it worked for me. Thank you

[#7]

Worked for me too! Found the key in two places. (but not in the one first suggested)

[#8]

Hey Josh, that seems to have fixed it for me. Actually, I couldn't locate that specific key, actually I had no Edge keys under the Microsoft folder.
Rather, it was located here [HKEY_USERS\S-1-5-21-2779(snipped)\SOFTWARE\Policies\Microsoft\Edge]
"MetricsReportingEnabled"=dword:00000000

[#9]

Solution just in time. Today Stable got to v105 and would have stopped working.

[#10]

@bjmelchers same.

[#11]

I can confirm that deleting "MetricsReportingEnabled" also fixes Edge 105 stable from not starting. I tried all the dev builds on x86 and x64 and it wouldn't install properly either.
I thought it was an MSI problem.