`eData.dll` fails `Code Integrity` due to `Store signing level requirements` about legacy-edge-launcher HOT 6 OPEN

Well, if your just disabling Code Integrity for eData.dll (like you seem to do) that should be "fine".
But keep in mind, that using Legacy Edge itself might be a security issue (no patches since 2 years).

If you want, feel free to clean up your cmd file a bit and create a PR to include it into this repo.

• *.cmd -> *.ps1
• Comments + Readme
• User consent request
• ...

from legacy-edge-launcher.

I have Edge Legacy and Edge Chromium running side by side without disabling Code Integrity on the latest build.


I can develop a small app that can automatically set everything up for the user if anyone wants it. Would be handy to deploy the legacy edge again for more users without needing to downgrade or disable security features. The browser extensions don't load in the latest version of the Microsoft store, so I will try some older builds and see if the issues are caused by the server or by the client.

from legacy-edge-launcher.

To clairify: What would your app do?
Please also remember Spartan does not work on Windows 11+ any more (See #2)!

from legacy-edge-launcher.

I decided not to put the effort in creating an app when a simple powershell script like this also works. I'm not entirely sure about the security but to my knowledge it shouldn't make the system more vulnerable. Someone who's smarter or has more knowledge should verify that for me.
In its current state this method seems to work pretty well, I used to have blue screens and startup repair issues when doing it this way before because of random conflicts with driver signatures, but it appears that I managed to get that fixed.

To use it you simply need to copy Edge's missing binaries back to "C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe", you don't need to replace the files that are already there, those should be left there. If you replace them it's nessecary to register the app again, but the script automatically does that anyways to make sure there's no issues with that. To fix the edata.dll file from being blocked, you need to right click the script and choose run as administrator so it can create a new system integrity base policy and install it. For the policy to work you have to reboot.

It should work but in case something magically goes wrong and the system refuses to boot you'll have to go into the startup options menu and select option 7 to disable driver signature validation so you can delete the policy file again by hand. Otherwise you can try going into the command line or another operating system to remove the policy.

I hope it's a good enough solution.

from legacy-edge-launcher.

@Iemand005 Hey, can you help me with this case? I'm having this following problem. It just refused to register.

from legacy-edge-launcher.

@B1ue-Dev

@Iemand005 Hey, can you help me with this case? I'm having this following problem. It just refused to register.

You should first of all check if it doesn't already work. If not, make sure to have all the files in place under "C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe".
I would assume that you are missing some files, if so take a look here for downloads. After making sure all files are present try to register the app again. If that doesn't work, make sure all binaries have the right permissions. You can try fixing that by applying the folder permissions recursively by enabling the files and sub folders to use the permissions of the parent folder. Otherwise grant "all application packages" read permissions.
If you have other issues you can also try going to Settings > Apps > Microsoft Edge and reset the app or clear the app data.

from legacy-edge-launcher.