Bug Report: Extension warnings reappearing in Edge
MonfGeiger opened this issue · 18 comments
Describe your problem in one sentence:
I use the patcher, it stops the warnings for a while, but then the dev extension warnings happen again
Name the affected patch/problem (if available)
The "Dev Extension Warning" patch acting less of a permanent-ish removal/hider and more of a "temp sleep mode" patch
Your used browser
Microsoft Edge 109.0.1518.70
Longer description (optional)
About two weeks ago, i had to fix some edge stuffs, so after making sure the warning patch was uninstalled, i repair installed edge using the setup file downloaded from the microsoft edge webpage, re-configured stuff back to how i had it, and re-applied the warning patch again. the 1st screenshot has the patches im using, the 2nd is the (Re)-Install output. for a time, it worked, not a single "hey, this is a dev extension, best to not use it or whatever, set this warning in sleep mode and blah blah idgaf". I don't use edge as much except for youtube or certain websites that (for SOME dumb reason or another) have compatibility problems or issues with firefox. well, at the time of this post, the warning came back. so i reinstalled the patch with the same choices i chose last time, and for now, it hasn't come back. idk if its my version number of edge, or the patching tool being out of date or something, but even if the patch tool needs to be constantly running to permanently hide the warning, somehow said warning still squeaking by.
Additional information (optional)
No Password
Patch Tool Log (only three).zip
Version of the patch tool is 6.0.0
This feels almost the same as this issue below, but i think its different enough, so ill put it as reference (also, nice)
#69
When you get the extension warning in Edge, do you click on Not now or on Remind me in 2 weeks?
i click on the X button (not the web browser's X button, but the warning message's X button). sometimes, that makes it go away for a long while, while on the most random of times (by random, i do indeed mean non-consistently), when i open edge, it just pops back up again. its ephemeral on when & if it happens again. idk if its something edge is auto-fixing about itself (however it may/may not be doing it), or if the 6.0.0 edition of the patch is faltering against the newer version-updates of edge, but that's what im getting
It could be that it is not injecting fast enough. Also try just clicking on Not now next time. Also make sure that no Edge process is running before you start Edge and after you close it. Windows 11 especially always keeps an instance running, because Microsoft really wants you to use it. This improves startup time by 0.1 seconds and for that they occupy hundreds of megabytes of RAM by default.
I will look into this myself in the next weeks
ah crap, forgot to mention my OS, my bad
Edition Windows 10 Pro
Version 22H2
Installed on 10/29/2022
OS build 19045.2364
@MonfGeiger Did the warning appear again?
I'm getting this too for the past couple weeks.
Disabled "continue running background extensions..." option and ensured no msedge.exe when running the patcher.
OS: Windows 10 Pro build 19045.2728
Tried the "Not now" -> "Remind on browser restart" option, but it didn't work.
Of course, "Not now" -> "Remind in 2 weeks" blocks it, but not permanently like the patcher's supposed to.
@MonfGeiger Did the warning appear again?
i think it might've a couple weeks ago, but in the now (at the time of this post), it hasn't reappeared. ill be honest, i forgot about this issue i opened up, but lately i havent been using edge for much, so unless i rapidly open & close edge to proc the warning somehow, it isnt showing just yet
@MonfGeiger Did the warning appear again?
i think it might've a couple weeks ago, but in the now (at the time of this post), it hasn't reappeared. ill be honest, i forgot about this issue i opened up, but lately i havent been using edge for much, so unless i rapidly open & close edge to proc the warning somehow, it isnt showing just yet
What about now?
I am also currently having this issue. The warning appeared when I opened Edge just now.
No background running process, Startup Boost in settings is turned off.
I have just tried to reproduce it and the warning did not appear for me once I installed my patcher. After uninstalling the patcher, the warning reappears.
@Gabanders
Please do the following:
- Start Edge as normal
- Locate it in the Task Manager and tell me the file path of the running
msedge.exe
process (Find it in the Details tab, then go to the file) - Find the
msedge.dll
file located in the same folder or nearby (in a child folder), zip it with any good zip compressor, and then upload the file here
My running msedge.exe
process is located in C:\Program Files (x86)\Microsoft\Edge\Application
The uploaded msedge.dll
was located in C:\Program Files (x86)\Microsoft\Edge\Application\112.0.1722.46. It was too large to be uploaded directly to Github so I uploaded it to my Google Drive.
My running
msedge.exe
process is located in C:\Program Files (x86)\Microsoft\Edge\ApplicationThe uploaded
msedge.dll
was located in C:\Program Files (x86)\Microsoft\Edge\Application\112.0.1722.46. It was too large to be uploaded directly to Github so I uploaded it to my Google Drive.
Please open edge://settings/help and let it update to the latest stable version (112.0.1722.48), then do the same steps again. I would like your 112.0.1722.48
msedge.dll
Here is the 112.0.1722.48
version of my msedge.dll: Google Drive.
@Gabanders
I have the exact same file and also at the same location.
Can you (re)install the patcher and also send me the logs that the patcher produces?
What antivirus do you use? Do you have a game running with anticheat? Do you have a kernel anticheat installed? Is there anything noteworthy in regards to your system?
I notice that the extension warning will only pop up when I launch Edge immediately after a reboot before waiting for the ChromeDLLInjector to appear. So the patcher does work but I hope you come up with a different method so we don't have to wait for it to launch first on startup.
I notice that the extension warning will only pop up when I launch Edge immediately after a reboot before waiting for the ChromeDLLInjector to appear. So the patcher does work but I hope you come up with a different method so we don't have to wait for it to launch first on startup.
This is hardly possible. It is better to patch during runtime and this requires the injector to be launched.
Computers running with a fast CPU, unlike yours, should be able to launch the injector within 1-10 seconds after logging in.
I just encountered this problem. It only happens after a computer restart. I didn't choose any of the options when I first saw the popup and just closed the browser (because it annoys me so much).