You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Despite https://github.com/AdguardTeam/HostlistsRegistry having existed for quite some time now (Seemingly 17 months), AdGuard for Windows has yet to make any of that repo's approved lists show up in the DNS filtering settings, as can be seen in the screenshots below.
Expected Behavior
Lists that are added on "Hostlists Registry", which number around 40 thus far, becomes selectable as opt-in lists in AdGuard for Windows' DNS filtering settings.
Screenshots
Additional Information
Somewhat oddly, there doesn't seem to be any options to make AdGuard for Windows installations forget turned-off custom lists, as can also be seen in the screenshot above.
The text was updated successfully, but these errors were encountered:
adguard-bot
changed the title
AdGuard for Windows' DNS filtering still isn't utilising the "Hostlists Registry" lists
Add "Hostlists Registry" to AdGuard's DNS filter list
Dec 28, 2022
AdGuard version
7.11.3
Browser version
N/A
OS version
Windows 11 22H2 x64 22621.900
What filters do you have enabled?
No response
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
Despite https://github.com/AdguardTeam/HostlistsRegistry having existed for quite some time now (Seemingly 17 months), AdGuard for Windows has yet to make any of that repo's approved lists show up in the DNS filtering settings, as can be seen in the screenshots below.
Expected Behavior
Lists that are added on "Hostlists Registry", which number around 40 thus far, becomes selectable as opt-in lists in AdGuard for Windows' DNS filtering settings.
Screenshots
Additional Information
Somewhat oddly, there doesn't seem to be any options to make AdGuard for Windows installations forget turned-off custom lists, as can also be seen in the screenshot above.
The text was updated successfully, but these errors were encountered: