Did 7.6 completely break filtering for anyone else?
- Thread starter imnothere
- Start date
Reopened issue at github:
github.com
Internet Explorer 11 · Issue #3772 · AdguardTeam/AdguardForWindows
AdGuard 7.6.1 не блокирует рекламу в Internet Explorer 11. AdGuard 7.6.1 больше поддерживает Internet Explorer 11?
github.com
It may not matter, as Microsoft is going to fully retire Internet Explorer 11 on June 22nd, 2022.
blogs.windows.com
And to be perfectly honest (as this is my opinion on the subject) if you're still using Internet Explorer right now it might be time to search for a better, more secure alternative. Internet Explorer is basically a dead, outdated web browser. And Microsoft finally announcing an end-of-life date solidifies that fact.
The future of Internet Explorer on Windows 10 is in Microsoft Edge
Update: The retired, out-of-support Internet Explorer 11 desktop application has bee
blogs.windows.com
And to be perfectly honest (as this is my opinion on the subject) if you're still using Internet Explorer right now it might be time to search for a better, more secure alternative. Internet Explorer is basically a dead, outdated web browser. And Microsoft finally announcing an end-of-life date solidifies that fact.
AdGuard website claims:
While i do agree that IE11 is an old browser and about to be retired by Microsoft, the fact is hasn't yet, and up until AdGuard 7.6 was released to the wider public there were no issues with Adguard on IE11 that i noticed.
If AdGuard knew that 7.6 was going to have an issue with IE11 we should have been told about it either before, or when, 7.6 was released from Beta as a final build... as an aside i ran the Beta builds of 7.6 and didn't have any noticeable issues with IE11, it wasn't until the final build of 7.6, more noticable in 7.6.1, were rolled-out that i noticed issues on IE11.
Imo, it just seems odd that we were told in this thread that 7.6.1 had fixed the issue (but it didn't, it made it worse), then it was replicated, then the js features surfaced as a reason, and now it appears that before IE11 has reached end of life there is a sort of back-handed message that IE11 is no longer supported by AdGuard?
Fyi, I don't mean any disrespect to anyone but i am a little frustrated at how this has been handled.
Obviously there are limits to what "any browser" means, e.g. I of course would not expect AdGuard to work with IE1 or Netscape but until IE11 does reach end of life, i would.
While i do agree that IE11 is an old browser and about to be retired by Microsoft, the fact is hasn't yet, and up until AdGuard 7.6 was released to the wider public there were no issues with Adguard on IE11 that i noticed.
If AdGuard knew that 7.6 was going to have an issue with IE11 we should have been told about it either before, or when, 7.6 was released from Beta as a final build... as an aside i ran the Beta builds of 7.6 and didn't have any noticeable issues with IE11, it wasn't until the final build of 7.6, more noticable in 7.6.1, were rolled-out that i noticed issues on IE11.
Imo, it just seems odd that we were told in this thread that 7.6.1 had fixed the issue (but it didn't, it made it worse), then it was replicated, then the js features surfaced as a reason, and now it appears that before IE11 has reached end of life there is a sort of back-handed message that IE11 is no longer supported by AdGuard?
Fyi, I don't mean any disrespect to anyone but i am a little frustrated at how this has been handled.
It's likely because IE11 lacks the JavaScript features needed to get it to work like Blaz mentioned. IE11 itself hasn't had any sort of major update in years and is behind all other browsers when it comes to the level of browsing features it has and the support (or lack thereof in this case) in regards to new technologies and standards (e.g. HTTP/2, QUIC, TLS 1.3, etc.).
It's becoming clearer that 7.6 did break something, whether or not that is the issue with IE11 remains unclear... I srongly suspect that whatever AdGuard changed with the final release of 7.6 (and 7.6.1) to this day remains current for IE11 users.
Confer and make up your own mind:
github.com
github.com
Fwiw, i tried the latest nightly build tonight and i couldn't uninstall AdGuard when it again failed to work, i had to System Restore and then when that didn't work i had to run Revo Uninstaller to uninstall AdGuard, then reinstall AdGuard back to a working state on my PC using 7.5.3
There is not a shadow of doubt in my mind that 7.6 has broken something that it shouldn't have, and discussiuon about IE11 is nothing more than a smokescreen.
I'd love to be proven wrong about this but so far all the evidence seems to point at 7.6 and its variant having broken something.
Confer and make up your own mind:
AdGuard for Windows - 7.6.1
After the recent v7.6 release a small percentage of users encountered a rather severe issue of not being able to update any filters, or even the app itself. This problem isn't very common but extremely critical to those who ran into it, so it justifies an immediate hotfix. If you're one of the...
forum.adguard.com
Release 7.6.1 · AdguardTeam/AdguardForWindows
After the recent v7.6 release a small percentage of users encountered a rather severe issue of not being able to update any filters, or even the app itself. This problem isn't very common but extre...
github.com
AdGuard v7.6 cannot connect to the Internet · Issue #3758 · AdguardTeam/AdguardForWindows
Reported by a user. I have been having some issues with AdGuard for Windows I think all these problems began a week ago or so. I have attached below the Logs. NOTE: I have a stable Internet connect...
github.com
Fwiw, i tried the latest nightly build tonight and i couldn't uninstall AdGuard when it again failed to work, i had to System Restore and then when that didn't work i had to run Revo Uninstaller to uninstall AdGuard, then reinstall AdGuard back to a working state on my PC using 7.5.3
There is not a shadow of doubt in my mind that 7.6 has broken something that it shouldn't have, and discussiuon about IE11 is nothing more than a smokescreen.
I'd love to be proven wrong about this but so far all the evidence seems to point at 7.6 and its variant having broken something.
In my personal opinion nobody in their right mind should be using Internet Explorer in this day and age. Literally every other web browser available is better than and more secure than Internet Explorer - for the sake of security alone nobody should be using it any longer. Even Safari, the most limited modern web browser available (compared to Chrome, Edge, Firefox, Vivaldi, Brave, etc.), is light years ahead of Internet Explorer. Not to mention Microsoft doesn't even develop for it anymore (only issuing security fixes monthly) and has set the retirement date for Internet Explorer and is recommending everyone using Internet Explorer to switch to Edge.
And I agree, at the very least people still using Internet Explorer should switch to Edge ASAP. It's more secure and better than Internet Explorer.
And yes, I get that certain websites like banking websites (lol) still require IE (which is a shame and those sites' webmasters should get with the times) but that's where Edge comes in handy as it has a feature called Internet Explorer Mode which literally addresses the single remaining valid use case of Internet Explorer. So there's really no excuse not to switch web browsers at this point in time, and you really should.
I don't mean to come off as an pushy opinionist or even come off as insulting (which please don't think anything I've said here as an insult!) or rude or anything like that, I'm just trying to implore using reason and to state the reality of the situation Internet Explorer is in now. I'm going to guess the AdGuard team will continue to support Internet Explorer until the retirement a year from now, but I wouldn't be surprised if it stops working sooner than later. If you decide to keep using Internet Explorer, you're willingly accepting the risks involved when using it, but don't expect software companies like AdGuard to keep support Internet Explorer (as they're one of the few who actually do still support Internet Explorer, everyone else has long abandoned it), especially since a lot of websites these days are dropping Internet Explorer support, like YouTube for example. Internet Explorer might not be fully dead yet, but it's as dead as it can be and it's not going to get any better while using it.
P.S. Something else to consider here (in regards to your observation that it works in 7.5 and not in 7.6) is; perhaps the filtering engine changed in 7.6, which takes advantage of and requires newer JavaScript and other modern web browsing features to work correctly, which because Internet Explorer is old and not developed anymore it inadvertently broke Internet Explorer support because IE doesn't support what's being used now? That could explain why it works in 7.5 then suddenly doesn't work anymore in 7.6, as they updated the filtering engine. And if that's indeed the case and there's no way to add some kind of a compatibility shim (which isn't worth it in my opinion) to get it to work again, in my opinion, they should just drop Internet Explorer support now.
And I agree, at the very least people still using Internet Explorer should switch to Edge ASAP. It's more secure and better than Internet Explorer.
And yes, I get that certain websites like banking websites (lol) still require IE (which is a shame and those sites' webmasters should get with the times) but that's where Edge comes in handy as it has a feature called Internet Explorer Mode which literally addresses the single remaining valid use case of Internet Explorer. So there's really no excuse not to switch web browsers at this point in time, and you really should.
I don't mean to come off as an pushy opinionist or even come off as insulting (which please don't think anything I've said here as an insult!) or rude or anything like that, I'm just trying to implore using reason and to state the reality of the situation Internet Explorer is in now. I'm going to guess the AdGuard team will continue to support Internet Explorer until the retirement a year from now, but I wouldn't be surprised if it stops working sooner than later. If you decide to keep using Internet Explorer, you're willingly accepting the risks involved when using it, but don't expect software companies like AdGuard to keep support Internet Explorer (as they're one of the few who actually do still support Internet Explorer, everyone else has long abandoned it), especially since a lot of websites these days are dropping Internet Explorer support, like YouTube for example. Internet Explorer might not be fully dead yet, but it's as dead as it can be and it's not going to get any better while using it.
P.S. Something else to consider here (in regards to your observation that it works in 7.5 and not in 7.6) is; perhaps the filtering engine changed in 7.6, which takes advantage of and requires newer JavaScript and other modern web browsing features to work correctly, which because Internet Explorer is old and not developed anymore it inadvertently broke Internet Explorer support because IE doesn't support what's being used now? That could explain why it works in 7.5 then suddenly doesn't work anymore in 7.6, as they updated the filtering engine. And if that's indeed the case and there's no way to add some kind of a compatibility shim (which isn't worth it in my opinion) to get it to work again, in my opinion, they should just drop Internet Explorer support now.
I rolled back to 7.5.3 but Adguard was still unable to filter IE11. Up until 7.6 Adguard functioned perfectly on IE11. Why would a roll back not restore functionality? Is it due to 7.6 breaking something deep down in the OS related to IE? As a result a system restore is required?It's becoming clearer that 7.6 did break something, whether or not that is the issue with IE11 remains unclear... I srongly suspect that whatever AdGuard changed with the final release of 7.6 (and 7.6.1) to this day remains current for IE11 users.
Confer and make up your own mind:
AdGuard for Windows - 7.6.1
After the recent v7.6 release a small percentage of users encountered a rather severe issue of not being able to update any filters, or even the app itself. This problem isn't very common but extremely critical to those who ran into it, so it justifies an immediate hotfix. If you're one of the...forum.adguard.com
Release 7.6.1 · AdguardTeam/AdguardForWindows
After the recent v7.6 release a small percentage of users encountered a rather severe issue of not being able to update any filters, or even the app itself. This problem isn't very common but extre...
AdGuard v7.6 cannot connect to the Internet · Issue #3758 · AdguardTeam/AdguardForWindows
Reported by a user. I have been having some issues with AdGuard for Windows I think all these problems began a week ago or so. I have attached below the Logs. NOTE: I have a stable Internet connect...
Fwiw, i tried the latest nightly build tonight and i couldn't uninstall AdGuard when it again failed to work, i had to System Restore and then when that didn't work i had to run Revo Uninstaller to uninstall AdGuard, then reinstall AdGuard back to a working state on my PC using 7.5.3
There is not a shadow of doubt in my mind that 7.6 has broken something that it shouldn't have, and discussiuon about IE11 is nothing more than a smokescreen.
I'd love to be proven wrong about this but so far all the evidence seems to point at 7.6 and its variant having broken something.
Is that about the gist of it?
I don't know what the issue is, i'm just reporting what my experience has been so far.
For me 7.5.3 works well with both IE and FF on Win7 64bit... i may be missing some of the latest bells and whistles that 7.6 (& the .1 variant) offers in FF but for me there are far too many bells and whistles associated with AG that i don't need nor want... AG was after all, at it's core, supposed to be all about blocking ads and the malicious websites associated with ads.
@Boo Berry No offence is taken and likewise i don't mean any offence, that said i am struggling to understand how during the Beta process of 7.6 it worked but when the final release was rolled out something was broken, surely whatever change was made between the final Beta build and the first release of 7.6 to the wider public it should have been tested before 7.6 was released because whatever that change was, it broke IE11.
Further, for all the failings of IE11 i have maintained using it because i like the layout of IE11 that neither Edge nor Firefox give me...
For the most part FF is my primary browser but there are occasions when i prefer IE11, i understand and understood that IE11 won't last for ever which is why i installed FF... rightly or wrongly i took solice that AG had my back when i used IE11, that AG now appears to have dumped support for IE11 with no notice is my major issue.
As an aside, i forgot to disable automatic updates so i found myslef back on 7.6.1 again this morning, grrr lol
I looked into this a little bit, and it looks like my guess above about the filtering engine being improved utilizing JavaScript features that IE11 doesn't support is indeed why this occurs and it explains why 7.5 works and 7.6 doesn't work with IE11. URL blocking still works fine in IE11, element hiding (and the Assistant userscript) doesn't work anymore, because IE11 doesn't support the JavaScript features it now uses and requires.
Still, the AG team saying they support IE11 yet element hiding and the Assistant not working anymore pretty much says otherwise, which I think is kinda a mistake and it's creating some confusion here. Since it mostly doesn't work now the line in the sand is drawn, so they should just announce the dropping of support for Internet Explorer now, unless they can add some sort of compatibility shim.
I've posted in that Github issue regarding this.
Still, the AG team saying they support IE11 yet element hiding and the Assistant not working anymore pretty much says otherwise, which I think is kinda a mistake and it's creating some confusion here. Since it mostly doesn't work now the line in the sand is drawn, so they should just announce the dropping of support for Internet Explorer now, unless they can add some sort of compatibility shim.
I've posted in that Github issue regarding this.
@Boo Berry Thanks for looking into this and updating the Github thread, i don't hold out much hope that this will be taken seriously, not least because the Github thread is still marked as Closed, but thanks for trying anyway.
Fwiw, i agree that if no fix is available for IE11 then the least the AG developers should do is be upfront about it and declare that IE11 is no longer supported.
However, if whatever was changed in the first official release of 7.6 (after the final Beta build of 7.6) has had unforseen consequences for IE11 users then the developers need to know about it.... to date the developers appear to be in denial that there is any issue.
Whatever the outcome, an official stance on IE11 support would be appreciated by AG.
For those interested, confer: https://github.com/AdguardTeam/AdguardForWindows/issues/3772
Fwiw, i agree that if no fix is available for IE11 then the least the AG developers should do is be upfront about it and declare that IE11 is no longer supported.
However, if whatever was changed in the first official release of 7.6 (after the final Beta build of 7.6) has had unforseen consequences for IE11 users then the developers need to know about it.... to date the developers appear to be in denial that there is any issue.
Whatever the outcome, an official stance on IE11 support would be appreciated by AG.
For those interested, confer: https://github.com/AdguardTeam/AdguardForWindows/issues/3772
KatherineHunter
New Member
Thanks for sharing
Thanks for clarifying that this was a mistake and it will be fixed
Same.
I am incredibly hesitant to ask this but having tried all the releases since 7.6 without the issue being fully resolved, has this issue been finally been resolved in 7.7.1, or will it never be resolved?
Last edited:
Okay, wait, I was too fast to judge. Actually, we fixed the issue from v7.6.
Here's how things are now:
1. Cosmetic filtering works in IE11.
2. Extended CSS rules work only partly in IE11.
3. Legacy AdGuard Assistant does not work in IE11 and we're not going to change this.
Here's how things are now:
1. Cosmetic filtering works in IE11.
2. Extended CSS rules work only partly in IE11.
3. Legacy AdGuard Assistant does not work in IE11 and we're not going to change this.