Launcher does not work in 21H1 about legacy-edge-launcher HOT 55 CLOSED

LdrpProcessWork - ERROR: Unable to load DLL: "eData.dll", Parent Module: "C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EMODEL.dll", Status: 0xc0000428
The error 0xc0000428 seems to sometimes appear during boot in case a digital signature can not be verified or has expired!
https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows-boot-error-invalid-image-hash

from legacy-edge-launcher.

Well, I'm pretty sure I would have the code integrity issue, but I think something else is preventing it from even getting that far. If I figure that out, then I'll probably have the code integrity problem.

Thanks for the help!

There's always Browser Stack. :P

from legacy-edge-launcher.

At some point, Windows removes the binaries of Edge Legacy with an update.
You'd need to copy those files from a backup or sth similar and then uninstall the new one (manually).
With the newest update even that trick doesn't work. I'm still looking for a solution...

from legacy-edge-launcher.

Thx your answer , I use zh-cn windows10. I find a solution to use Edge Legacy. Give you url：Install Edge. But this page is chinese website,may you need google translate. I use this method install the Edge Legacy. And, install the edge beta version, and use the zip file uninstall.bat uninstall the edge again, then the edge Legacy and edge beta is all install. use win+r open run shell:appsfolder, can see the two version edge. I'm not sure the package can run your system, but you can try. Thx again.

from legacy-edge-launcher.

Thank you for your tip. I looked into those bat files and figured out how they work.
They at first do the job my launcher is intened to do.
Then they do what I mentioned above: Uninstalling the new edge and copying the old files to were they were (my launcher can not do this (at the moment)).

Sadly, this does not seem to work in the newest windows update (Removal of Adobe Flash (??)). Edge just crashes.
I'll try to do some debugging as soon as I have some more time but it doesn't look good...

21H1
19043.1110
Windows Feature Experience Pack 120.2212.3530.0

from legacy-edge-launcher.

I got an idea if you know maybe turn Microsoft edge into .Appx package and re-structure it so that it isn't detected.
You might want to check the files I got from my Edge Legacy USB windows to go drive that still have original latest edge contents on System Apps.

(Download links of system Apps located Microsoft Edge)
Edge.zip
https://drive.google.com/file/d/1pldiE23u_fGsspIcUkTexmwW7BnFLbFt/view?usp=sharing

Putting the Edge Weky name whatever in the system apps will not work instead for other computers it will just open for a few seconds then close itself this does not happen on Windows to go drive however.
(IF NEEDING MORE INFORMATION FROM WINDOWS TO GO DRIVE ASK ME! I got a fully working Edge on my Windows To Go drive)

from legacy-edge-launcher.

Thanks (@nuengdioew) for sharing.
Actually I have the files of Edge Legacy in place and everything worked fine until one of the 21H1 updates.
No "hiding" was required! You have to uninstall the stable version of Edge Chromium though, but you can still use the Beta or Dev Version if you want to...

instead for other computers it will just open for a few seconds then close itself

The thing is, I got 2 VMs: One with Edge running just fine.
And on my real PC, Edge is also crashing ("symptoms" above) with the following failure (same goes for my 2nd VM):

from legacy-edge-launcher.

I'd say even I tried removing the Edge stable nothing apparently work I am on 20H2 all methods I tried registry and removing edge doesn't work this is getting real annoying I'd say it's best if maybe pack it in a .Appx still wondering how should I fix it Im not a programmer and windows UWP is weird to me.

from legacy-edge-launcher.

Actually Microsoft Edge Legacy is more complicated than just the UWP app. It is dependent on the "Microsoft-Windows-Internet-Browser-Package-amd64" package. But some people managed to install it on Windows 10 LTSC 2019 which doesn't have Edge installed at all (Edge legacy is missing and Edge chromium didn't exist when it was released so it uses IE). Here is more info: https://forums.mydigitallife.net/threads/solved-add-microsoft-edge-to-windows-10-enterprise-ltsb-ltsc.76296/

from legacy-edge-launcher.

@kristibektashi Also thanks for sharing!
Your provided link led me to this page where the package you mentioned can be downloaded.
But it seems like this Package contains just the components that make up the UWP part of Edge and also some runtime stuff (I've already installed), so sadly this did not help me in my specific case.

from legacy-edge-launcher.

@kristibektashi Also thanks for sharing!
Your provided link led me to this page where the package you mentioned can be downloaded.
But it seems like this Package contains just the components that make up the UWP part of Edge and also some runtime stuff (I've already installed), so sadly this did not help me in my specific case.

BTW that is version 1809. You might want to use version 2004 of the Edge package (idk where to find it)

from legacy-edge-launcher.

It looks like the easiest way to use old Edge is to create VM with old version of Windows

from legacy-edge-launcher.

That’s true and I also got a VM with a working Edge (You could also use a tool like browserstack).
The thing is, that this approach doesn’t fit to the (original) purpose of this application: Launching Edge on any Win10 device even if it has been removed.

from legacy-edge-launcher.

I could confirm that Legacy Edge still crashes on Windows 10 21H2. Even with the Edge package contents copied mind you.

from legacy-edge-launcher.

Well, I had an 1809 VM. I extracted the Legacy Edge's content into this file:
Edge (2).zip
Maybe that should work?

from legacy-edge-launcher.

@nguyenthienminh
Thanks! I just tried it out but did not had any luck. To be honest, I didn’t really believed this to work as I’ve already tried it with the files from my own VM.
I don’t really know, but I think it might be a bug or even intentionally implemented kill switch in one of the edge related files in System32 or even deep nested in the OS itself (e.g. Appx-Activation).
As MS already implemented a redirect for Legacy Edge (Spartan) ➜ New Edge (Anaheim), this doesn’t sound to wrong to me…

from legacy-edge-launcher.

from legacy-edge-launcher.

At this point, the only thing to do now... is to revert a cumalative update in Windows 10. Edge Legacy seems to be removed in Patch Tuesday in April last year. Finding said patch however, is much harder.

from legacy-edge-launcher.

from legacy-edge-launcher.

Well, found the patch that both removed Legacy Edge and patched the system files (so that Edge Legacy won't start if the files are copied) in Windows 10. It's the KB5001330 update. Maybe revert the patch using DISM (if it's even there at all)?

from legacy-edge-launcher.

from legacy-edge-launcher.

How do I remove that "patch" then I cannot do it in 20H2

Is it even a fresh install or not?

from legacy-edge-launcher.

I'd say find a .appx or .msixbundle that contained edge legacy likely it will be filled with dependencies. If you manage to find the product ID of edge and use apguard RG should work and if not, you should try and get all of it into a msixbundle or appx.
…

That won't work, Legacy Edge is shipped with your Windows installation and doesn't exist on the Microsoft Store to my knowledge. I looked up the Category ID and the Package Family Name for both Windows 10 and Windows Phone versions of Edge and I can't find anything on the Microsoft Store for it. I have an appx file for Windows Phone but this is for arm processors so won't work on your pc likely. I don't think official appx files exist for Edge Windows 10 as it's a system app and requires special permissions normally installed apps can't have:

		<wincap:Capability Name="cortanaSettings"/>
		<wincap:Capability Name="enterpriseCloudSSO"/>
		<wincap:Capability Name="microsoftEdgeRemoteDebugging"/>
		<wincap:Capability Name="liveIdService"/>
		<wincap:Capability Name="settingSyncConfiguration"/>
		<wincap:Capability Name="storeAppInstall"/>
		<wincap:Capability Name="storeConfiguration"/>
		<wincap:Capability Name="targetedContent"/>

I tried changing the family name and removing all extensions and capabilities and sideloading that under development mode but it still does not work with the exact same error: "COM ActivateExtension". I have had this problem since 20H1 when the files for Edge were removed on my device. Putting them back from my own backups or other backups does not work. I also removed the IsInbox restriction from the state repository to uninstall and completely reinstall the app but that does not help either. I assume there is some sort of extension missing, I don't know what that could be but something important is missing.

from legacy-edge-launcher.

@Iemand005

requires special permissions normally installed apps can't have

You could use MagicUnlock.reg to try to sideload an app with those capabilities (I haven't tested it).

COM ActivateExtension

What does this error refer to?

something important is missing

The KB5001330 update (as @nguyenthienminh suggested) apparently removed Adobe Flash

from legacy-edge-launcher.

The KB5001330 update (as @nuengdioew suggested) apparently removed Adobe Flash

That is the Patch Tuesday KB Update in May 2021 that removed Legacy Edge (and Adobe Flash). Maybe reverting that update would work?

from legacy-edge-launcher.

*(int*)ntdll!LdrpDebugFlags = 1 gives you more information:

1dfc:0858 @ 01529984 - LdrpLoadDllInternal - ENTER: DLL name: eData.dll
1dfc:0858 @ 01529984 - LdrpFindKnownDll - ENTER: DLL name: eData.dll
1dfc:0858 @ 01529984 - LdrpFindKnownDll - RETURN: Status: 0xc0000135
1dfc:0858 @ 01529984 - LdrpSearchPath - ENTER: DLL name: eData.dll
1dfc:0858 @ 01529984 - LdrpComputeLazyDllPath - INFO: Packaged DLL search path computed. Package Dirs: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe;, DllPath: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe;C:\Windows\SYSTEM32
1dfc:0858 @ 01529984 - LdrpResolveDllName - ENTER: DLL name: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\eData.dll
1dfc:0858 @ 01529984 - LdrpResolveDllName - RETURN: Status: 0x00000000
1dfc:0858 @ 01529984 - LdrpSearchPath - RETURN: Status: 0x00000000
1dfc:088c @ 01529984 - LdrLoadDll - ENTER: DLL name: C:\Windows\System32\Windows.UI.Xaml.dll
1dfc:088c @ 01529984 - LdrpLoadDllInternal - ENTER: DLL name: C:\Windows\System32\Windows.UI.Xaml.dll
1dfc:1d68 @ 01529984 - LdrpAllocateTls - INFO: TlsVector 00000157F3048730 Index 12 : 2 bytes copied from 00007FFFF365C978 to 00000157F30671D0
1dfc:1d68 @ 01529984 - LdrpAllocateTls - INFO: TlsVector 00000157F3048730 Index 13 : 2 bytes copied from 00007FFFF2C08BFC to 00000157F30672F0
1dfc:1d68 @ 01529984 - LdrpAllocateTls - INFO: TlsVector 00000157F3048730 Index 14 : 8 bytes copied from 00007FF809515B10 to 00000157F3067070
1dfc:0858 @ 01529984 - LdrpMinimalMapModule - ENTER: DLL name: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\eData.dll
1dfc:0858 @ 01529984 - LdrpMinimalMapModule - RETURN: Status: 0x00000000
1dfc:0858 @ 01529984 - LdrpFindDllActivationContext - INFO: Probing for the manifest of DLL "C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\eData.dll" failed with status 0xc00000bb

fcc8:155c8 @ 1178173359 - LdrpLoadDllInternal - ENTER: DLL name: eData.dll
fcc8:155c8 @ 1178173359 - LdrpFindKnownDll - ENTER: DLL name: eData.dll
fcc8:155c8 @ 1178173359 - LdrpFindKnownDll - RETURN: Status: 0xc0000135
fcc8:155c8 @ 1178173359 - LdrpSearchPath - ENTER: DLL name: eData.dll
fcc8:155c8 @ 1178173359 - LdrpComputeLazyDllPath - INFO: Packaged DLL search path computed. Package Dirs: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe;, DllPath: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe;C:\WINDOWS\SYSTEM32
fcc8:155c8 @ 1178173359 - LdrpResolveDllName - ENTER: DLL name: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\eData.dll
fcc8:155c8 @ 1178173359 - LdrpResolveDllName - RETURN: Status: 0x00000000
fcc8:155c8 @ 1178173359 - LdrpSearchPath - RETURN: Status: 0x00000000
fcc8:7eb0 @ 1178173359 - LdrLoadDll - ENTER: DLL name: C:\Windows\System32\Windows.UI.Xaml.dll
fcc8:7eb0 @ 1178173359 - LdrpLoadDllInternal - ENTER: DLL name: C:\Windows\System32\Windows.UI.Xaml.dll
fcc8:155c8 @ 1178173359 - LdrpProcessWork - ERROR: Unable to load DLL: "eData.dll", Parent Module: "C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EMODEL.dll", Status: 0xc0000428
fcc8:155c8 @ 1178173359 - LdrpLoadDllInternal - RETURN: Status: 0xc0000428
fcc8:155c8 @ 1178173359 - LdrpRedirectDelayloadFailure - ERROR: Failed to find export eData.dll!LoadDataStore (Ordinal:0) in "EMODEL.dll"  0xc0000428

from legacy-edge-launcher.

Well, I think we could try installing Flash with Edge alongside it.

from legacy-edge-launcher.

bool __fastcall IsBrowserReplacementFeaturePresent(__int64 a1, __int64 a2)
{
  LOBYTE(a2) = 1;
  wil::details::FeatureImpl<__WilFeatureTraits_Feature_BrowserReplacement>::ReportUsage(
    &`wil::Feature<__WilFeatureTraits_Feature_BrowserReplacement>::GetImpl'::`2'::impl,
    a2,
    0i64);
  return (unsigned __int8)GetInstalledBrowserChannelInfo() != 0;
}

bool GetInstalledBrowserChannelInfo()
{
  bool v0; // bl
  unsigned __int16 *v1; // r8
  unsigned int v2; // er9
  HKEY hKey; // [rsp+30h] [rbp-448h] BYREF
  WCHAR SubKey[264]; // [rsp+40h] [rbp-438h] BYREF
  HKEY__ v6; // [rsp+250h] [rbp-228h] BYREF

  v0 = 0;
  _o_wcscpy_s(SubKey, 260i64, L"Software\\Microsoft\\EdgeUpdate\\Clients\\");
  _o_wcscat_s(SubKey, 260i64, L"{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062}");
  if ( !RegOpenKeyExW(HKEY_LOCAL_MACHINE, SubKey, 0, 0x20219u, &hKey) )
  {
    v0 = BrowserChannels::Private::ReadExePath((BrowserChannels::Private *)hKey, &v6, v1, v2);
    RegCloseKey(hKey);
  }
  return v0;
}

from legacy-edge-launcher.

Well, I think we could try installing Flash with Edge alongside it.

Might be worth a try, but to me eData.dll not loading doesn’t seem to be associated with Adobe Flash.
eData.dll is located alongside MicrosoftEdge.exe, so it can not be one of the probably “modified” dlls.

from legacy-edge-launcher.

So Windows doesn't let eData.dll to load?

from legacy-edge-launcher.

from legacy-edge-launcher.

Well,

We would need to find other older versions to do the job

It's not really true. Since eData.dll is bundled inside Edge already, it IS the version that'll do the job. But, there's just some pesky file(s) hiding somewhere in Windows that prevents the loading of eData.dll. That's my logical best explanation.

from legacy-edge-launcher.

Eureka! So if we had the valid digital signature of eData.dll, we could probably just apply the signature to it!

from legacy-edge-launcher.

I assume that the signature may just has expired; in that case we won't get a working one.
Therefor we should try to make Windows ignore any of these checks.
What seems really strange to me is that eModel.dll can still be loaded (by the same procedure) but eData.dll (it's loaded by eModel.dll) can not?!

from legacy-edge-launcher.

So if the signature is expired we just roll back our system clock and it should work?

from legacy-edge-launcher.

I assume that the signature may just has expired; in that case we won't get a working one. Therefor we should try to make Windows ignore any of these checks. What seems really strange to me is that eModel.dll can still be loaded (by the same procedure) but eData.dll (it's loaded by eModel.dll) can not?

The procedure to ignore the signature looks like the "Disable driver signature enforcement" thing in Windows.

from legacy-edge-launcher.

@nguyenthienminh Have you tried that?

from legacy-edge-launcher.

https://textslashplain.com/2019/09/27/aw-snap-every-tab-crashes/

Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe) attempted to load \Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\eData.dll that did not meet the Store signing level requirements.

Microsoft-Windows-Internet-BrowserNoAnaheim

from legacy-edge-launcher.

@nguyenthienminh Have you tried that?

Haven't tried the "Disable driver signature enforcement" trick yet ('cause I don't have a 21H2 VM at the moment, only 1809), but I'll try it out later!

Edit: not working. Even with Test Mode turned on (which essentially disables driver signature enforcement all together), it's still not working.

.

from legacy-edge-launcher.

@nguyenthienminh
You can try the following (It worked for me!):

1. Go to desktop-to-uwp-test-windows-s
2. Download the zip with the WDAC policies
3. Extract
4. Copy the SiPolicy_Audit.p7b from the zip to C:\Windows\System32\CodeIntegrity\SIPolicy.p7b (See README.txt)
5. Reboot

Warning
This measure effectively disables CodeIntegrity for your PC and is therefor a potential threat to your device’s security!
This should only be considered a workaround which should only be tested on a VM to verify, that CodeIntegrity is in fact the (only) cause of the crash!

from legacy-edge-launcher.

That actually worked in my 21H2 VM! Just that... well, the assets are seemingly missing, and when I clicked any menu, it just crashed Edge.
Interestingly, Edge on Windows 10 2004 worked, but the older 1809 version didn't for some reason (maybe signature-related stuff again)

from legacy-edge-launcher.

Well I saw this solution 2 days ago and finally got to try it, and to my surprise it actually works!! This is amazing! Now are there ways to fix that expired signature without disabling code integrity?

from legacy-edge-launcher.

@Iemand005 That's great to hear!
Unfortunately, I don’t know (yet), how Store policies determine Code Integrity and the hint above is no solution but rather a dangerous way for testing (Only in a VM)!

from legacy-edge-launcher.

@nguyenthienminh

Edge on Windows 10 2004 worked, but the older 1809 version didn't for some reason (maybe signature-related stuff again)

Legacy Edge (Project Spartan) has extremely strong ties to the OS and uses many internal apis, that may and will change between OS versions. That’s the reason, why Spartan crashes on Win11 (#2).

from legacy-edge-launcher.

@Iemand005 That's great to hear! Unfortunately, I don’t know (yet), how Store policies determine Code Integrity and the hint above is no solution but rather a dangerous way for testing (Only in a VM)!

I'm not a proffessional when it comes to dll signing and stuff, but what would happen to my data if I disable code integrity on my windows installation? And can we redo the signature somehow, or make another dll to replace eData.dll and then call the original or is there any other version of Edge that has a working dll signature?

from legacy-edge-launcher.

@Iemand005

Code Integrity prevents code (dll) from being loaded if it does not comply against certain policies / certificates. This blocks the execution of malicious code.

If you disable it, any code is allowed to load: You could just drop an arbitrary dll with the name of one, that is normally loaded, next to an exe and therefor hijack its process (See DLL hijacking).
This proposes a serious security risk!

It should be possible to exclude only Spartan from Code Integrity but that only limits the mentioned risks to this process.
We could maybe replace some specific signature files but that would almost certainly require (other) serious modifications to the OS.

By the way: Neither Spartan nor EdgeHtml (rendering engine) nor Chakra (js engine) have received any security updates since over a year! Using Spartan in a every-day environment should therefore be considered a security risk itself!

You see: It’s not quite easy to solve this issue and there will always remain some threats to your digital security.

from legacy-edge-launcher.

I've been struggling with trying to get Edge Legacy to run as well on Windows 10 after the April 2021 updates.

I would prefer to try testing Edge Legacy (Spartan) by excluding only Spartan from Code Integrity.

I would appreciate any help from any knowledgeable people on how to do this. Again, this is for testing. I understand the risks.

I have:

Windows 10 Professional 2004 x64 v19041.1415 (the final 2004 release)

I pulled Edge Legacy out of a UUP dump ISO for Windows 10 Professional 2004 x64 v19041.867, the final build of Edge Legacy.

I extracted install.wim out of sources, then extracted Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\ and Windows\SystemApps\Microsoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwe\ out of install.wim. I deleted these two folders from C:\Windows\SystemApps\, then copied the extracted folders into C:\Windows\SystemApps\. (I.e., deleted the existing folders and replaced them with the ones from the ISO.)

I rebuilt the Appx package folders:

Delete folders C:\Users\Admin\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe and C:\Users\Admin\AppData\Local\Packages\Microsoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwe.

Run in Powershell:

• Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml” -Verbose}
• Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdgeDevToolsClient | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml” -Verbose}

Open shell:appsfolder, create shortcut by right clicking Edge Legacy icon ("place on desktop...")

Of course, nothing happens when clicking the shortcut, presumably because of the code integrity thing.

As mentioned, I don't want to disable code integrity on the entire system. So again, I'm looking for any ideas or instructions from knowledgeable people on how to exclude only Edge Legacy from code integrity. I will not be using it as my main browser, and I understand the risks.

from legacy-edge-launcher.

I would prefer to try testing Edge Legacy (Spartan) by excluding only Spartan from Code Integrity.

👍

First of all, check whether code integrity is actually the problem by opening event view at…
Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational
…and looking for a entry like described here #1 (comment)

Updates on this specific issue: #3

from legacy-edge-launcher.

I checked and I didn't see an entry like that... but, I've since installed Edge Chromium 105.0.1343.42, which somehow now runs instead of C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe (when clicking its shortcut from the shell:appsfolder). Directly clicking MicrosoftEdge.exe of course does nothing.

My understanding is if I uninstall Edge Chromium 105.0.1343.42 and instead install it from the Insider Channels, the above behavior will stop.

But before I installed Edge Chromium, nothing was happening when I clicked the link to start Edge Legacy. I guess that would have created a Code Integrity event that would have stayed visible in Event Viewer, which it apparently didn't. So I guess for me, Code Integrity wasn't the issue?

I have to take more time for more testing, which I don't have ATM.

Thanks for the super fast reply (on a closed issue!), I really appreciate it.

from legacy-edge-launcher.

My understanding is if I uninstall Edge Chromium 105.0.1343.42 and instead install it from the Insider Channels, the above behavior will stop.

true

I guess that would have created a Code Integrity event that would have stayed visible in Event Viewer

Well, it should...
Sure there's nothing?

from legacy-edge-launcher.

Only one entry is in there: Code Integrity will disable WHQL driver enforcement for this boot session. Settings 0x80000000 from user SYSTEM on 9/18/2022 10:23:11 PM.

Not sure why that's in there, I think this is about the time I upgraded to 19041.1415. I've since rebooted several times and this entry did not happen again.

from legacy-edge-launcher.

@BlohoJo
Well, that means more debugging then...

I have to take more time for more testing, which I don't have ATM.

I’m sadly facing the same problem...

ToDo (If you find some time):

1. Try to install Visual Studio and debug the Microsoft Edge uwp app in native mode (See docs).
2. If necessary, ask via discussions for help with debugging.
3. Report the crash via a new issue

from legacy-edge-launcher.

from legacy-edge-launcher.

@nguyenthienminh You can try the following (It worked for me!):

1. Go to desktop-to-uwp-test-windows-s
2. Download the zip with the WDAC policies
3. Extract
4. Copy the SiPolicy_Audit.p7b from the zip to C:\Windows\System32\CodeIntegrity\SIPolicy.p7b (See README.txt)
5. Reboot

Warning
This measure effectively disables CodeIntegrity for your PC and is therefor a potential threat to your device’s security!
This should only be considered a workaround which should only be tested on a VM to verify, that CodeIntegrity is in fact the (only) cause of the crash!

Does this work on Windows 11? I don't want my PC being bricked. and no i am not risking my 8gb SSD for an VM.

from legacy-edge-launcher.

@emeraldongithub
It does, but Legacy Edge crashes on Win11 (See #2).

Warning
If you follow any steps from this issue, you’re doing it on your own risk (Read comments above)!

from legacy-edge-launcher.