Chrome-Developer-Mode-Extension-Warning-Patcher icon indicating copy to clipboard operation
Chrome-Developer-Mode-Extension-Warning-Patcher copied to clipboard

Bug Report: Remove extension warning does not work on MSEdge

Open kien5436 opened this issue 3 years ago • 16 comments

Describe your problem in one sentence: It's simply not working on MSEdge

Name the affected patch/problem (if available) Remove extension warning

Your used browser Microsoft Edge Version 93.0.961.38 (Official build) (64-bit)

Screenshots (optional) image

Longer description (optional) Explain how you encountered the bug or what it is about in detail.

Additional information (optional) Add any other information about the problem here.

kien5436 avatar Sep 07 '21 00:09 kien5436

The issue is not reproducible on my machine and I have also checked the patterns and offsets and everything is still correct. You might have incorrectly installed the injector or it is not running or similar.

Ceiridge avatar Sep 07 '21 01:09 Ceiridge

The injector always run, I can see its process in task manager. I guess I pick wrong path. Here are my steps:

  • Run the injector with admin right
  • Select .dll file
  • Another window appear, ask me to select .exe file
  • Choose "remove extensions warning" patch
  • Apply it, result is:

Patcher gui initialized Searching for Chromium installations... Cleared ChromeExes registry Wrote patch file to C:\Users\kien\AppData\Local\Microsoft\Edge\Application\93.0.961.38 Appended C:\Users\kien\AppData\Local\Microsoft\Edge\Application\93.0.961.38\msedge.dll to the registry key Extracted injector zip Wrote patcher dll to C:\Program Files\Ceiridge\ChromeDllInjector\ChromePatcherDll_1631019153.2268045.dll Created and started task Patches installed! Successfully installed to C:\Users\kien\AppData\Local\Microsoft\Edge\Application\93.0.961.38\msedge.exe

Can you help me where I went wrong?

kien5436 avatar Sep 07 '21 12:09 kien5436

Normally you don't have to choose any path, because the installer GUI automatically finds the Edge installation?

Ceiridge avatar Sep 07 '21 13:09 Ceiridge

Was this the problem? Alternatively, you have to make sure to select the msedge.dll in the application version folder and the msedge.exe in the parent folder (e. g. C:\Users\kien\AppData\Local\Microsoft\Edge\Application)

Ceiridge avatar Sep 07 '21 13:09 Ceiridge

Sorry for late reply. I don't know that the injector can automatically find path. My Windows doesn't include Edge and I install it from store. But I'm sure I chose the right file

kien5436 avatar Sep 07 '21 16:09 kien5436

I'm sure you chose the wrong file. This should not be happening: Wrote patch file to C:\Users\kien\AppData\Local\Microsoft\Edge\Application\93.0.961.38 , instead it should be: Wrote patch file to C:\Users\kien\AppData\Local\Microsoft\Edge\Application

Ceiridge avatar Sep 07 '21 16:09 Ceiridge

Oh, I'll try it. Edge gives me option to disable warning in 2 weeks so I'll notice you result after that

kien5436 avatar Sep 07 '21 16:09 kien5436

If you choose the files correctly as stated in this comment (https://github.com/Ceiridge/Chrome-Developer-Mode-Extension-Warning-Patcher/issues/69#issuecomment-914302873), it should work. I will add it to the automatic installation finder in the future (https://github.com/Ceiridge/Chrome-Developer-Mode-Extension-Warning-Patcher/issues/70).

Ceiridge avatar Sep 07 '21 16:09 Ceiridge

I tried as you said but the injector didn't work

image

kien5436 avatar Sep 21 '21 12:09 kien5436

You can try looking up the actual executable path of msedge.exe by performing a right click on the Edge process (you might have to expand the group of Edge processes first) in the task manager and by clicking on "Open file location".

If this doesn't help, please send these log files located at these paths: C:\Windows\Temp\ChromePatcherDll.log C:\Windows\Temp\ChromePatcherDllErr.log C:\Windows\Temp\ChromePatcherInjector.log (might require Administrator permissions to read, so try copying the file to another location) C:\Windows\Temp\ChromePatcherInjectorErr.log (might require Administrator permissions to read, so try copying the file to another location)

Ceiridge avatar Sep 21 '21 13:09 Ceiridge

I can't find ChromePatcherInjectorErr.log. Here are log files: ChromePatcherDll.log ChromePatcherDllErr.log ChromePatcherInjector.log

kien5436 avatar Sep 21 '21 13:09 kien5436

The DLL was only injected once. Is that how often you started Edge in the last hour? I would recommend updating the patcher and then reinstall it and maybe install Edge manually and not from the Windows store: https://www.microsoft.com/de-de/edge The saved data in your Edge profile should stay the same.

Ceiridge avatar Sep 21 '21 14:09 Ceiridge

I did install new Edge from its homepage, the injector automatically detected the path but the patch still didn't work. I also tried to uninstall then reinstall patches.

Patcher gui initialized
Searching for Chromium installations...
Cleared ChromeExes registry
Wrote patch file to C:\Program Files (x86)\Microsoft\Edge\Application
Appended C:\Program Files (x86)\Microsoft\Edge\Application\93.0.961.52\msedge.dll to the registry key
Extracted injector zip
Wrote patcher dll to C:\Program Files\Ceiridge\ChromeDllInjector\ChromePatcherDll_1632233909.805007.dll
Created and started task
Patches installed!
[ChromePatcherDllErr.log](https://github.com/Ceiridge/Chrome-Developer-Mode-Extension-Warning-Patcher/files/7203907/ChromePatcherDllErr.log)
Successfully installed to C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe

Logs:

ChromePatcherDllErr.log ChromePatcherDll.log ChromePatcherInjector.log

kien5436 avatar Sep 21 '21 14:09 kien5436

The DLL was only injected once. Is that how often you started Edge in the last hour? I would recommend updating the patcher and then reinstall it and maybe install Edge manually and not from the Windows store: https://www.microsoft.com/de-de/edge The saved data in your Edge profile should stay the same.

I don't use Edge usually, Edge has an option to hide the warning in 2 weeks and I have to wait till today to test your latest injector.

kien5436 avatar Sep 21 '21 14:09 kien5436

I just tried the patcher again in a virtual machine with the latest version and the patcher fully worked. Maybe your antivirus does something strange. I will leave this issue open to make sure this is only a single case and not an actual bug.

Ceiridge avatar Sep 21 '21 16:09 Ceiridge

Ok. I think I have to deal with it. Anw, thanks for your time

kien5436 avatar Sep 21 '21 23:09 kien5436

This is now actually a duplicate of #95 The discussion goes on further there

Ceiridge avatar Apr 15 '23 20:04 Ceiridge