版本歷史 | AdGuard

版本 v7.19 隆重登場！讓大家久等了。這次更新之後，使用者可以通過連結分享設定、體驗炫酷的使用者樣式、新的登入方式，並告別煩人的漏洞。

重要消息：這是最後一個支援 Windows 7 的版本。為什麼？我們在工作中使用幾個庫，其最新版本已不再支援 Windows 7。而最新版本對於使用者安全和應用程式的整體功能都是必要的。如果無法升級到新版本的 Windows，請繼續使用 7.19 版。

讓我們一起看看主要改進。

分享設定

我們相信分享是一種關愛，因此推出了一個新功能，讓使用者可以通過連結分享設定。如果您在桌面應用上設定得很完美，只需掃描二維碼，就能將這些設定遷移到行動應用中。使用者還可以分享連結給朋友們，分享這份愛吧！

升級瀏覽外觀設計

想要給沒有暗黑主題的網站設定一個？通過使用者樣式，一切皆在掌控之中！

使用者樣式是自訂的主題，它讓使用者在不修改網頁內容的情況下改變其外觀。使用者樣式透過新增 CSS 樣式來覆蓋網站原有的樣式。

新增使用者樣式的方法：進入「設定」→「擴充功能」→「新增」→「從檔案或 URL 匯入」。如果您想自己動手設計，點選「新增」→「創建使用者樣式」。使用者也可以網上找到現成的使用者樣式。安裝好後，開啟瀏覽器，網頁立馬煥然一新。

新登入方式

現在，當使用者選擇使用信箱登入時，將跳轉到瀏覽器進行登入，綁定 AdGuard 帳戶。雖然一開始可能不太方便，但使用者可以使用密碼管理器，在瀏覽器中啟用自動輸入功能。這樣就不用每次都輸入登入資訊了。此外，這種方式也更方便我們維護服務，讓我們能更快修復錯誤。

使用者還可以選擇一次性驗證碼登入。我們會將驗證碼傳送到您的信箱，從此不必再為記住密碼煩惱。

最後

您了解應用左側的設定清單嗎？我們對它們的名稱進行了更新，使其更加直觀。比如，隱身模式現在叫追蹤保護。這更符合實際功能，畢竟它不能讓使用者隱身，但可以保護您免受追蹤。

每次新版本都會修復一些大大小小的漏洞，比如那個讓人討厭的藍屏問題。這次我們盡力解決了它，並更新了 WFP 和 TDI 網路驅動程式，讓一切運行如常。

此外，我們還更新了 Scriptlets 和 DnsLibs，確保使用者能夠享受高質量的過濾和安全、“整潔”的瀏覽體驗。

更新記錄

改進

新增了使用者樣式的支援 #5179

新增了 Floorp 瀏覽器的支援 #5164

更新了 Fanboy's Annoyance List 的翻譯說明 #5205

修復

AdGuard 導致與 Microsoft 驅動程式 netio.sys 有關的 BSOD #5169

AdGuard DNS 過濾器在重新啟用 DNS 模組後無法運作 #5146

右鍵選單搜尋方塊中缺少深色主題 #5157

「禁用 Windows 作業系統廣告」功能在 Windows 10 中出現 #5193

雙擊在封鎖清單和允許清單中不起作用 #5175

過濾編輯器中滾動條背景的深色主題使用者介面小問題 #4679

主視窗始終在系統啟動時開啟 #5227

阻止 HTML 元件時，過濾記錄顯示的是 $permission rule，而不是適當的過濾器名稱 #5231

如果存在帶有 $generichide 修飾符的規則，HTML 請求無法顯示在過濾記錄中 #5213

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.16.44 #5242

改進

在被過濾的應用程式使用後量子密碼時啟用它 #1916

修復

AdGuard 內容腳本在 uber.com 上被 CSP 阻止 #1903

GM_xmlhttpRequest 不支援 Referer 標頭 #1899

啟用 AdGuard 後，無法在 Firefox 中登入 sony.de 網站 #1867

將 Scriptlets（過濾規則的 JavaScript 改進）更新為 v1.11.27

改進

新增了 set-local-storage-item 的 allowed 和 denied 值 #445

新增了 abort-on-stack-trace 的 inlineScript 和 injectedScript 的行號支援 #439

新增了 set cookie 的 checked 和 unchecked值 #444

新增了 trusted-click-element 的 reload 選項 #301

修復

log-on-stack-trace 播放軟體無法在 deltabit.co 上運行 #384

將 DnsLibs（DNS 過濾引擎）更新為 v2.5.41

將 ContentScript 更新為 v2.0.6

將 UserscriptsWrapper 更新為 v1.2.24

AdGuard 具有不少語言版本！我們聽取了大家的回饋意見，在這次令人興奮的更新中，我們修復了與版本翻譯有關的錯誤。此外，我們還提高了應用程式的效能。

我們很高興推出全新的 Windows 版 AdGuard！開發 v7.18 的過程中，我們的主要目標是為使用者提供最好的廣告過濾體驗。我們相信我們已經完美達成了這個目標。

首先，讓我們給所有 Windows 11 使用者帶來一個好消息：現在 AdGuard 可以阻止 Microsoft 在 Windows 11 開始功能表中托管的廣告。功能將預設啟用，無需在設定中翻找，只需更新 AdGuard 軟體即可享受全面保護。

回到更“古早”的廣告類型：我們更新了 CoreLibs 過濾引擎和其他組件。這樣，我們引入了新的修改器和腳本，幫助過濾器開發人員針對廣告和追蹤器創建更好、更強大的過濾規則。改進後，軟體突然崩潰的不良情況也會減少很多！請大家相信 AdGuard 將始終如一地保護個人安全。

好消息還不止這些！我們還更新了網路驅動程式，以提高 AdGuard 與其他基於網路的應用程式的相容性。

更新記錄

修復

「繫統啟動時打開主視窗」選項不起作用 #5074

開始畫面上的深色主題問題 #4996

開啟隱身模式後出現延遲 #5104

過期過濾器無法從可用過濾器清單中刪除 #5083

安裝 Nightly 夜間版本後，預設設定為發佈更新通道 #5077

即使所有內容都顯示在熒幕上，滾動條仍然可見 #5054

任務管理器中的 adguard.exe 進程圖示已變形 #5110

視窗控制按鈕移位 #5043

無法安裝或啟動 AdGuard 測試版 #5129

檢查更新後，在過濾器編輯器中刪除相同的註解 #5118

無法通過 URL 安裝一些自訂的過濾器 #4801

改進

「封鎖 Flash」選項移至「高級設定」中 #4705

工具列選單主題現在與應用程式主題同步 #5012

在追蹤保護中新增了阻止 Windows 11 開始功能表廣告的新選項 #5103

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.15.47 #5139

修復

使用者腳本 API 中的錯誤導致某些第三方腳本無法運行 #1876

$all 修飾符不適用於非類域名 URL 部分 #1860

$generichide 修飾符使 URL 阻止規則無法正常工作 #1857

元件隱藏的規則不適用於一些網站 #1865

改進

新增 $urltransform 修飾符支援 #1364

新增 $xmlprune 修飾符支援 #473

現在可為 HTTPS 過濾生成 ECDSA 憑證 #360

增加了對圍欄框架的處理 #1853

新增對 uBO 的 /regex/(cosmetic rule) 格式的支援 #1844

將 ContentScript 更新為 v2.0.6

DnsLibs（過濾引擎）

將 DnsLibs 更新為 v2.5.33 #5128

修復

AdGuard 在過濾記錄中提示不正確的規則 #210

單擊 DNS 過濾器編輯器中水准滾動條上的任意位置無法滾動 #4715

Scriptlets（过滤规则的 JavaScript 改进）

將 Scriptlets 更新為 v1.10.25

修復

對於某些值，set-constant 無法正確工作 #403

Cookie 名稱在 set-cookie 中被編碼 #408

set-local-storage-item 轉換無法正常工作 #404

改進

新增 no-protected-audience scriptlet #395

增加了將 scriptlets 添加到允許清單的功能 #377

為 prevent-fetch 添加了 cors 反應類型 #394

為 set-cookie 添加了 domain 參數 #389

新增 href-sanitizer scriptlet #327

新增 json-prune-fetch-response scriptlet #361

新增 json-prune-xhr-response scriptlet #360

新增 trusted-suppress-native-method scriptlet #383

增加 set-cookie 的可能數值 #388

新增在 shadowRoot 的 trusted-click-element 中查找選擇器的功能 #323

某些重新導向資源現在也可用作 scriptlets #300

這就是補充上一次的技術更新。我們提高了應用程式的穩定性並修復了程式錯誤。

在這個修補程式中，我們解決了兩個關鍵問題。首先，我們修復了 CoreLibs 過濾引擎中出現的一個重大錯誤。其次，更新到 AdGuard v7.17 Windows 版後，如果在「透過輸入該完整的路徑，把應用程式排除在過濾之外」選項中輸入帶引號的單詞，應用程式就會崩潰。我們修復了這一問題，同時還更新了 DnsLibs。

更新記錄

修復

「透過輸入該完整的路徑，把應用程式排除在過濾之外」選項中的引號讓 AdGuard 無法運行 #5087

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.14.53 #5092

DnsLibs（DNS 過濾引擎）

將 DnsLibs 更新為 v2.5.19 #5093

繫好安全帶，因為 Windows 版 AdGuard v7.17 即將帶您進入一個新的數字維度！在新版本中，我們更新了 CoreLibs。這讓我們改進 Encrypted ClientHello 工作，並實施 on-the-fly DoH 連線過濾功能。

改進的 Encrypted ClientHello

AdGuard Windows 版支援 Encrypted ClientHello，但這是一個實驗功能。該功能可以幫助我們加密最後一個未加密的數據包，是修建數據保護城墻的最後一層。我們正在努力解決一些技術問題，使其成為用戶的預設啟用功能。更新後的 CoreLibs 是實現這一目標的又一步驟。

On-the-fly DoH 連線過濾

更新 CoreLibs v1.14 後我們還可以實現 on-the-fly DoH 纜線過濾。為什麼它如此重要？以前，如果使用者在瀏覽器中設定 DoH，但沒有在 AdGuard 中設定，我們就必須在瀏覽器中過濾請求並將其發送到系統 DNS（未加密）。這一過程降低了此類使用者的安全。現在情況完全不同了。用 on-the-fly DoH 連線過濾，我們可以在瀏覽器中過濾 DNS 請求，而無需將其發送到未加密的伺服器。

除此之外，我們還做了一些小修復，更新了 WFP 和 TDI 驅動程式以及 DnsLibs。請檢視下面的更新記錄，不要忘了更新哦！

更新記錄

改進

新增了 # 符號的解析 #4666

修復

選擇 WFP 網路驅動程式時無法啟動保護功能 #5055

編輯規則時，過濾器編輯器有時工作不正確 #5058

更新到 v7.17 Beta 3 後無法啟動保護功能 #5060

有時無法設定自訂的 DNS 伺服器，應變失敗 #5029

在安裝過程中更改原始安裝路徑 #4975

更新到 v7.16 x64 時，AdGuard 目錄未從 Program Files (x86) 中刪除 #4972

在過濾記錄中無法按類型搜尋 #4980

更新到 v7.17.0 Nightly 版 1 (4583) 後無法啟動保護功能 #5017

AdguardSvc.exe 分支成多個線程 #4874

Certificate Info顯示兩次 #4964

關閉/啟動網路後，「過濾記錄」中不顯示已過濾的 DNS 請求 #4941

過濾器更新的時間計數器不起作用 #4974

啟用「DNS 保護」中斷在地 Windows 域名連線 #4906

DNS 過濾器編輯器視窗中無法使用水平滾動條 #4715

第一次點選時「在系統啟動時啟動 AdGuard」復選框沒有回響 #4965

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.14.52

改進

在 $permissions 中新增了使用 | 作為分隔符的選項 #1850

新增了一項功能，可在請求已處理事件中指示是否使用了往外代理 #1385

新增將主機傳遞給往外代理的支援 #1386

在本機支援 :has() 的使用者代理清單中新增 Firefox 121.0+ #1840

修復

無法將 QUIC ClientHello 解析分成兩個數據包 #1861

VOT（嗓音起始時間）腳本無法在 Google 瀏覽器中運行 #1665

如果未指定內容類型，對所有請求套用 $permissions 規則 #1856

名稱中包含 [ and ] 的 Cookie 規則被視為無效 #1843

同時運行 AdGuard 和 AdGuard VPN 瀏覽器擴充功能時，在某些情況下不應用修飾符規則 #1791

$all 修飾符工作不正確 #1842

未在 mall.sk 上註入 AdGuard 內容腳本 #1834

在字符類中封鎖帶有轉義斜線的 regex 規則不起作用 #1831

如果在 doctype 宣告之前有標記（帶 embed 屬性），則無法註入內容腳本 #1825

$path 修飾符對查詢參數不起作用 #1817

有端口的 URL 上的 $removeparam 重新導向無端口的 URL #1818

AdGuard 破解 android-hilfe.de 網站 #1800

無法安全連線到 wiki.cemu.info #1821

Scriptlets（過濾規則的 JavaScript 改進）

將 Scriptlets 更新為 v1.10.1

改進

新增與 uBO 的 set-cookie 腳本程式的相容性 #332

新增新腳本程式 call-nothrow.js #333

新增新的腳本程式 spoof-css #317

新增新腳本 trusted-create-element #278

新增新腳本 trusted-set-attr #281

新增更多支援值改進了 set-cookie #379

新增 ga.q 屬性改進了 Google 分析功能 #355

新增 OmidVerificationVendor 屬性改進了 google-ima3 #353

DnsLibs（DNS 過濾引擎）

將 DnsLibs 更新為 v2.5.4 #5047

改進

支援嚮往外代理傳遞主機名，而不是 bootstrap #197

改進對 HTTPS rrtype 的處理 #215

使用 DoH 中 IPv4/IPv6 的 Happy Eyeballs #217

生命、宇宙和一切問題的答案是什麼數字？坦率地說，我們也不知道，但 AdGuard v7.16 Windows 版答案就是 64。我們很高興地宣布，我們的應用程式現在兼容 64 位系統。

這意味著什麼

現在大多數 Windows 電腦都是 64 位的，它們比 32 位的電腦擁有更多的資源，如處理能力更強和內存更大。AdGuard 一直忠於 32 位版本，但時代在進步。現在是時候接受 64 位兼容性了，我們希望這將為我們的使用者帶來更靈敏的體驗，並讓開啟和關閉過濾器感覺就像純粹的魔法。

但 AdGuard 仍能在 32 位電腦上正常運行，對嗎

值得信賴的 32 位電腦不會被遺忘。使用者無需下載單獨的安裝程式：我們的系統會自動檢測您電腦的位數，讓您安裝相應的版本。

這個版本有什麼新的過濾功能嗎？

當然！另一個重大改進是 HTML 過濾功能。我們在 HTML 過濾規則中新增了選擇器的支援，這有助於更有效地封鎖廣告。

還有什麼改進

我們最新的 DnsLibs 為 AdGuard Windows 版帶來了一項新功能：基本 HTTP 身份驗證。這有什麼用？

使用 DNS-over-HTTPS 協定的使用者還能從 HTTP 協定的功能中獲益。例如，在使用 DoH 時，您可以使用標準 DNS 伺服器所不具備的身份驗證選項。

但是，如果您有一個自訂的 DNS 伺服器，並想限制對它的存取權限，該怎麼辦呢？當然可以通過 IP 位址限制存取權。但是，行動裝置等會經常更換網路。如何解決這個問題呢？這就是 HTTP 身份驗證支援的用武之地。使用 AdGuard Windows 版中的這一功能，您可以包含驗證資訊來連線到自訂的 DNS 伺服器。

AdGuard Home 和 AdGuard DNS 目前不提供此功能，但一推出親愛的用戶們都會第一時間知道！

還有嗎

為了提高 HTTPS 過濾的透明度，AdGuard 提供通過「過濾記錄」檢查原始憑證的選項。現在，使用者可以查看任何網路請求的詳細資訊，檢查 AdGuard 使用的加密，並檢查原始憑證。

此功能源於 HTTPS 過濾的一個主要問題。AdGuard 能有效地驗證憑證，但在某些情況下，使用者可能希望自己檢查原始憑證。您可以在我們的知識庫中閱讀有關此問題的更多資訊。

從龐大的更新記錄中可以看出，自上次發佈以來，我們並沒有閑著。我們也沒有落下 WFP 和 TDI 驅動程式：都更新了。總之，讓我們廢話少說，直接更新吧！

更新記錄

改進

在過濾記錄中顯示 HTTPS 過濾狀態和原始憑證 #4812

改進卸載程式 #4428

改進了安裝程式中 Active 狀態按鈕的文字顏色 #4887

刪除了開始選單中檔案夾的應用程式快捷方式 #4834

根據深色主題調整了引導介面 #4583

從備份檔案存檔中刪除了擴充功能名為 .bak 的檔案 #540

刪除了「關於」部分中第二次提到的版本號 #4836

更新了更新介面上的芬蘭語翻譯 #4761

修復

過濾器編輯器中的 Enable all 選項會導致應用程式崩潰 #4857

由於簽名無效，AdGuard 無法運行 #4864

在 Windows 7 上完成安裝並重新啟動後，應用程式不會自動啟動 #4760

封鎖清單和允許清單在家長控制中無法正常工作 #4189

在通過全路徑輸入排除過濾的瀏覽器中，瀏覽器助理繼續工作 #4723

如果應變伺服器模式不是系統預設模式，DNS 排除不起作用 #4822

如果某些域名/端口被阻止，啟動時間較長 #4894

應用程式崩潰後出現多個分隔符 #327

自 7.15 版起，如果服務無法通過 UDP 連線到 20.189.79.72:123 則無法正常啟動 #4868

Web of Trust 簡體中文版描述中的繁體中文詞語 #4739

Crowdin 過濾記錄中缺少字符串 #4825

編輯過濾器時無法選擇多個規則 #4474

已被剪切的規則不能再插入被剪切的字段中 #4859

如果位址包含端口號，則無法新增自訂的 DNS #4945

在網路報告期間無法傳輸與 DNS 過濾器和授權類型相關的參數 #4931

更新時未刪除 AppData 檔案夾中的舊目錄 #4939

在 Windows 11 上升級到第一個測試版後，x32 檔案夾沒有被刪除 #4940

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.13.115

為韓國電信新增了反 DPI 功能支援 #1789

改進了 ECH retry_configs 的用法 #1793

刪除了行動憑證的選項 #277

改進

已新增 !#else 預處理器指令支援 #1806

采用新的規則優先權方案 #1768

更改了 sec-ch-ua 標頭，以便在啟用隱身模式時匹配使用者代理 #1764

改進 HTML 過濾性能 #1772

修復

在 Windows 上啟動保護時關閉活動 QUIC/H3 連線 #1815

在 Edge Bing Chat 中不顯示圖片 #1744

使用 SXG 的網站從 Google 所尋開啟時沒有修飾過濾功能 #1812

macperformanceguide.com 網站上的過濾功能不起作用 #1810

TcpIpStack 中的 UDP 超時太短 #1796

最近更新憑證的網站無法驗證憑證 #1833

使用 Windows 版 AdGuard 無法加載 unicode.org #1830

由於網站憑證不同，其中一個子域未被過濾 #1839

在 Firefox 中瀏覽 smartstore.naver.com 時出現連線錯誤 #4960

DnsLibs（DNS 過濾引擎）

將 DnsLibs 更新為 v2.4.37

改進

為 DoH 端點新增了基本驗證功能 #189

允許在精確域名規則中使用 # 註釋 #196

允許指定僅 TCP 和僅 UDP DNS 上遊 #208

即時過濾 DoH 連線 #198

修復

本機 DNS 代理在使用普通 DNS 上遊時可能受到 DoS 攻擊 #202

127.0.0.1 local 被錯誤地解釋為所有 .local 地址，從而破壞 mDNS #207

DoH 試圖用陳舊的連線，時間太長了 #200

正確過濾 type=HTTPS 請求 #199

過濾器改進

在過濾記錄中新增了 User rules 選項 #4560

創建 DNS 規則時，刪除模式中不必要的句號 #4872

過濾器編輯器：編輯/鍵入時不應更改規則狀態 #4910

完成編輯後的不正確行為 #4850

使用者規則過濾器中第一條規則的行為不正確 #4885

根據 HTML "lang" 屬性和語言請求 HTTP 頭信息檢測網站的地域 #1736

增加 $replace 規則的限制 #1802

已新增 $extension 修改器禁用特定使用者腳本 #1706

添加了 cap_html_filtering 狀態的支援 #1758

$denyallow 不允許阻止檔案 #1809

$stealth 例外在 TCP 棧層不起作用，我們在此阻止 STUN/TURN #1737

未將內容腳本注入 object 標記中加載的元件 #1769

改進 HTML 過濾規則 $$，允許使用類似 CSS 的選擇器 #94

修復

計數器可能無法識別新增的規則 #4922

編輯過濾器時無法選擇多個規則 #4918

Scriptlets（過濾規則的 JavaScript 改進）

* 將 Scriptlets 更新為 v1.9.101

改進

處理 uBO 的語法 $redirect 優先級 #59

改進了 xml-prune，支持 xpath 文本內容匹配 #325

改進了 json-prune 的 stack 工作 #348

改進的 prevent-xhr #347

新增了根據名稱轉換重新導向的 API 方法 #346

新增了新的受信任腳本 trusted-prune-inbound-object #372

為 set-cookie 新增了更多支援值 #375

改進了 set-local-storage-item 和 set-session-storage-item，增加了對「開」和「關」的支援 #366

改進了儲存項目腳本，為刪除項目新增 regexp 支援 #256

改進 prevent-fetch #364

使用過的程式庫版本現在會顯示在「關於」頁面上 #2237

修復

set-constant 腳本小程式突破 vimeo.com #380

修正了超出最大調用堆棧大小時的 set-constant 腳本程式 #373 * 修正了 set-constant 值的問題 #330

修復了 music.youtube.com 上的 trusted-replace-xhr-response 錯誤 #359

改進了 m3u-prune，如果存在 \r 則不會裁剪內容 #354

改進了 trusted-replace-fetch-response，如果 URL 由 Object.defineProperty 設定，則不替換內容 #367

在將參數轉換為 uBO 規則時，參數中的逗號被刪除 #343

googletagservices-gpt 缺少 setPrivacySettings 方法 #344

UserscriptsWrapper

* 將 UserscriptsWrapper 更新為 v1.2.21

网盘直链下载助手 使用者腳本無法與 AdGuard 運行 #1780

在 AdGuard v7.15.1 Windows 版的更新中，我們解決了影響 Firefox 使用者的一個嚴重問題。啟用 AdGuard 後，某些網站將無法載入，並顯示與安全憑證有關的錯誤。與 7.15 版相比，新版本的 CPU 消耗也更少。

更新記錄

修復

Firefox 中的 HSTS/SSL 錯誤 #4866

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.12.83 #4866

「太空戰士一飛沖天」可以作為 AdGuard 團隊努力工作的座右銘。這次我們很高興給大家介紹 AdGuard Windows 版的新版本。

新 HTTP/3 過濾

該版本的主要更新之一是，改進了 CoreLibs v1.12 以後新增的 HTTP/3 過濾。HTTP/3（HTTP-over-QUIC）是使用 QUIC 而不是 TCP 的 HTTP 協定的最新版本。與 TCP 傳輸控制協定相比，QUIC 網路協定具有許多優勢，如更高的隱私性和安全性、更快的網際網路連線速度以及以任意順序處理數據包的能力。啟用 HTTP/3 過濾還意味著更有效的廣告封鎖效果。

目前，HTTP/3 過濾僅適用於 Safari 和 Firefox 瀏覽器。原因是，Chrome 瀏覽器驗證 QUIC 和 TCP 憑證的邏輯不同，不接受 AdGuard 憑證。不過，使用者可以在進階設定開啟此功能，用於測試和調試，以確保無縫運行。

把錯誤留在過去

我們解決了環境選單中的一個小問題，現在深色主題看起來完美無瑕。此外，安裝後，使用者可以隨時使用五個推薦的廣告封鎖過濾器，而不是一個。這一升級將使您的生活更輕松，更好保護使用者免受惱人廣告的困擾。

除此之外，我們還進行了其他改進，以提高 AdGuard Windows 版的整體性能。以前，應用程式有時會因內存占用過高而崩潰。不過，我們已經解決了該問題。此外，當網際網路連線不穩定或速度非常慢時，應用程式會出現不可預知的行為，甚至崩潰。現在，一切都運行得更流暢了。

最重要的是，我們更新了 WFP 和 TDI 驅動程序，並按照慣例更新了 CoreLibs、DnsLibs 和 Scriptlet，以確保更穩定的運行。

更新記錄

功能

新增了 HTTP/3 支援（IETF QUIC） #487

改進了通知使用者必須重新啟動的功能 #4817

新增了使用空格鍵按下對話框中的按鈕的功能 #4677

更改了設定過濾時過濾記錄中的設定圖示 #4656

在過濾記錄中新增了有關 TLS 屬性的更多資訊 #1171

新增了 $referrerpolicy 修飾符 #135

修復

將應用程式的環境選單調整為深色主題 #4587

無法在過濾器編輯器中的特定情況下新增新規則 #4684

Web of Trust 簡體中文版描述中的繁體中文內容 #4739

應用程式只安裝了一個非推薦的惱人的事物過濾器，而不是五個推薦的過濾器 #4764

在通過觸摸板預覽的過濾記錄中，向左/向右滾動不起作用 #4638

雙擊過濾記錄中的單選按鈕時未選擇任何元件 #4672

過濾器編輯器中「刪除過濾器」對話框的暗色使用者介面主題的小問題 #4664

允許使用空模式的 $stealth 規則 #1762

不支援 uBO 媒體查詢 #1707

使用 ipTIME 家庭路由器時出現幾秒鐘的延遲 #1756

AdGuard 會減慢網頁載入時間 #1522

「隱藏您的搜尋查詢」選項運行不正確 #1766

運行 Cloudflare WARP 時，系統 DNS 是環回的 #4692

如果 ExtendedCss 的使用不受限於 #?# 規則標記，可將 :has()、:not()、:is() 視為標準偽類 #1683

啟用 network.https.ech.enabled 設定後，不支援 ECH 的網站將啟用 ECH GREASE #1781

處理腳本 text decryption key not found 時出錯 #1750

有時備援 DNS 助理返回 127.0.0.1，而不是供應商的伺服器 #1687

TCP/IP：新增了新的拒絕模式，因為行政禁止 ICMP #1774

使用者腳本 SaveFrom helper 從 ok.ru 網站下載影視時出錯 #1776

在 mypikpak.com 無法使用修飾規則 #1767

過濾器的改進

功能

為基本規則新增了 $method 修飾符 #1713

新增了 $to 修飾符 #1714

修復

$jsonprune、$replace、$hls不適用於 non-GET-POST HTTP 方法 #1743

使 Windows 版 AdGuard 的 $app 修飾符不區分大小寫 #1755

$path 修飾符在路徑 market.yandex.ru/? 上不起作用 #1726

例外規則相互幹擾 #1749

過濾器編輯器中文本光標的位置錯誤 #4702

在 DNS 過濾器編輯器中執行某些操作（如刪除規則）後充分設定焦點（用於使用上/下箭頭鍵） #4362

$jsonprune 修飾符應能處理 jsonp 的引號 #1734

DnsLibs

將 DnsLibs 更新為 v2.2.24 #4826

CoreLibs

將 CoreLibs 更新為 v1.12.78 #4832

Scriptlets

將 Scriptlets 更新為 v1.9.58

功能

新增了新 evaldata-prune scriptlet #322

改進了 trusted-replace-fetch-response/trusted-replace-xhr-response，增加了替換所有匹配內容的功能 #303

新增了新 remove-node-text scriptlets #318

新增了新 trusted-replace-node-text scriptlet #319

修復

為 prevent-xhr 和 trusted-replace-xhr-response 模擬 getResponseHeader() 和 getAllResponseHeaders() 方法 #295

刪除記錄 scriptlets 的 cannot apply rule 資訊 #313

新增了返回 set-constant scriptlet 支援值的新方法 #316

應用程式顯示支援 scriptlet 或重新導向 #273

在調用 m3u-prune 和 xml-prune scriptlet 中的 send() 方法之前使用 addEventListener 時出現的收縮問題 #315

為 prevent-element-src-loading scriptlet 添加了防止內聯 onerror 和匹配 link 標記的功能 #276

trusted-set-cookie-reload，如果使用 $now$ 值，網站不會重新加載 #291

Cookie 設置 scriptlet，名稱和值編碼問題 #311

scriptlet 和重新導向中的 Response 實例屬性問題 #297

trusted-set-cookie 和 trusted-set-cookie-reload scriptlet 的值編碼問題 #320

修正了 log-addEventListener 操作中的錯誤 #335

如果請求/網域被 DNS 過濾阻止，prevent-fetch 和 prevent-xhr scriptlet 無法提供幫助 #334

修復 googletagservices-gpt — updateTargetingFromMap() #293

Scriptlet 應正確處理轉義引號 #286

為 set-cookie 新增了 Accept 和 Reject 值 #336

為 set-cookie 設定了不區分大小寫的值 #342

修改了 google-ima3 以避免與 DAI SDK 沖突 #331

修改了存儲項目 scriptlet，增加了按鍵刪除項目的功能 #338

在將規則轉換為 uBO 規則時，AdGuard 將逗號考慮在內 #343

UserscriptsWrapper

將 UserscriptsWrapper 更新為 v1.2.20

修復

imdb.com 的使用者腳本不起作用 #1729

In this release, we have improved the efficiency and compatibility of our app by updating the WFP and TDI drivers. We have also redesigned the tray icons to give them a fresh new look. Finally, we have fixed some bugs and updated Corelibs.

Changelog

Fixes

The CPU usage is high when using AdGuard VPN in Selective mode with Ad Blocker and system DNS enabled #4750

Incorrect detection of filtered apps when Browser Assistant is used #4680

An incorrect rule is suggested when attempting to unblock Stealth Mode for a request #4675

Unnecessary filter localhost notification when connecting to AdGuard VPN #4687

The context menu theme for Filtering log does not change when switching the app theme #4628

Finished translating Advanced settings to Russian #4704

Design

Updated the uninstaller icon #4599

Improved the settings icon in the Filtering log to appear when filtering criteria are set #4656

Versions

Updated CoreLibs to v1.11.118 #4762

這次更新我們修復了在一些裝置上發生的與藍白當機畫面（BSoD）有關的錯誤，更新了 CoreLibs。

更新記錄

修復

processUdpPacket 導致 BSoD #4733

版本

將 CoreLibs 更新為 v1.11.114 #4734

在這個版本中，我們修復了上一個版本中出現的一些錯誤，包括與 NordVPN 和 Cloudflare WARP 的相容，以及 BSOD 外觀的問題。當然，我們還更新了 CoreLibs 和 DnsLibs。

更新記錄

修復

Cloudflare WARP 在啟用 AdGuard 的 DNS 模組時不起作用 #4692

adgnetworkwfpdrv.sys 導致 BSOD #4691

如果啟用 DNS 模組，NordVPN 會幹擾 AdGuard #4673

如果啟用「使用 Encrypted Client Hello」並且運行 AdGuard VPN 瀏覽器擴充功能，AdGuard 會阻止對網域的存取 #1751

版本

將 CoreLibs 更新為 v1.11.111#4717

將 DnsLibs 更新為 v2.1.44 #4710

隨著春天的到來，AdGuard Windows 版也推出了最新版本。我們成功完成了許多新功能和改進。

實驗性 Encrypted ClientHello 的支援

值得使用者注意的功能是，我們新增了實驗性 Encrypted ClientHello（ECH）的支援。新技術全面加密 HTTPS 連線，避免 ISP 查看使用者連線的伺服器名稱，保證強制隱私保護。

為了讓所有使用者享受新使用體驗，我們將「使用 Encrypted ClientHello」功能新增到「進階設定」部分，並預設為所有新老使用者啟用了「DNS 防護」。

請注意，僅在禁用低級別的「封鎖 ECH」設定和啟用「DNS 防護」後，「使用 Encrypted ClientHello」功能才能起作用。原因是，ECH 依賴於通過 DNS 取得的數據，所以為了讓 AdGuard 接收這些數據並在全面範圍內為使用者啟用 ECH，DNS 過濾是必要的。

為了使 Encrypted ClientHello 起作用，用戶端和伺服器雙方都應該支援它。目前，只有少數應用程式支持 ECH。例如，Chrome 和 Firefox 在新增新技術的過程中。說到瀏覽器，先要等待它們處理好，沒有其他辦法。不過，由於 AdGuard 軟體，ECH 支援將自動在使用者裝置上的所有應用程式和瀏覽器中運作。

為了確保 ECH 工作正常，請使用以下方法：

前往 https://crypto.cloudflare.com/cdn-cgi/trace/ ，應該被顯示 sni=encrypted

前往 https://defo.ie/ech-check.php，應該被顯示 SSL_ECH_STATUS: success

「使用 Encrypted ClientHello」功能是實驗性的，因此可能會降低網頁加載速度。不過，我們正在努力解決這個問題。

新進階設定

我們還在「進階設定」部分增加了16個功能。每個功能的詳細描述可以在我們的知識庫上查找。以下可以了解新功能的名稱：

所有進階功能可以分為六個類型：

反 DPI 影響的選項允許對過濾請求進行低級別的修改，以保護使用者流量不受深度封包檢測（DPI）的影響

調整初始 TLS 數據包的分片大小

在一般 HTTP 請求中增加一個額外的空格

一般 HTTP 請求的片段大小

Keepalive 設定讓用戶配置與 Keepalive 連接有關的設置

啟用 TCP keepalive

TCP 保持通話的時間間隔

TCP keepalive 超時

過濾例外設定允許從 DNS 過濾中排除 Wi-Fi 網路和特定子網（用 CIDR 符號指定）

從過濾中排除指定的 IP 範圍

從過濾中排除的 IP 範圍

從 DNS 過濾中排除指定的 Wi-Fi 網路名稱（SSID）

DNS 相關選項幫助使用者微調 DNS 設定

使用應變 DNS 上遊

為 DNS-over-HTTPS 使用 HTTP/3

並行查詢 DNS 上遊

始終回應失敗的 DNS 查詢

憑證安全選項允許使用者按各種標準檢查網站和網路服務的憑證

檢查網站的憑證透明度

啟用異步 OCSP SSL/TLS 憑證撤銷檢查

於系統啟動時啟用過濾。現在預設情況下，如果禁用「在系統啟動時啟動 AdGuard」的選項，Windows 版 AdGuard 在作業系統啟動後不會過濾流量。如果使用者希望在 AdGuard 沒有啟動的情況下也能進行過濾，應該啟用該選項。

溫馨提示，在7.12版之前，AdGuard 的服務預設以過濾模式啟動（即使「在系統啟動時啟動 AdGuard」被禁用）。如果使用者對以前的行為感到滿意，請啟用該選項。

還有什麼改進呢？除了 CoreLibs 和 DnsLibs 更新之外，我們還更新了 WFP 和 TDI 驅動以及 ExtendedCSS。現在使用者還可以禁用「過濾本機主機（localhost）」進階功能。但請注意，禁用該功能將使 AdGuard 廣告封鎖程式和 AdGuard VPN 無法同時運作。

更新記錄

功能

增加了一個在選定的 Wi-Fi 網路上禁用 DNS 過濾的選項 #4578

增加了一個選項，如果 AdGuard VPN 被啟用，可以禁用「過濾本機主機（localhost）」進階設定 #4586

新增了 AdGuard 瀏覽器擴充功能庫中最新的 TLD-to-locale 映射 #4620

SafeVisit 被新增到過濾的應用程式清單中 #4618

當改變在過濾記錄中顯示查詢的預設設定時，過濾圖示會被高亮顯示 #4406

允許使用 Ctrl + E 組合開啟當前選定的 DNS 過濾器的進階過濾器編輯器 #4330

現在 AdGuard 可以備份使用者介面設定 4404

增加了使用 Enter 按鈕操作對話框的選項 #4526

修復

從休眠狀態恢復後 AdGuard 掛起 #4565

AdGuard 無法自動匯入 Firefox 的憑證授權 #4595

刪除應用程式後，AdGuard 憑證沒有從系統憑證存儲中刪除 #4610

系統啟動後，出現「該應用程式無法訪問 AdGuard 伺服器」的通知 #4590

從休眠狀態恢復後 WCF 通信中斷 #4551

安裝程式的黑暗主題的錯誤 #4584

一旦點擊過濾器編輯器按鈕超過一次，過濾器編輯器就會重新開啟，而不是聚焦 #4619

如果啟用「家長控制」並設定密碼，就不能通過「新增到 AdGuard」按鈕添加 DNS 伺服器或過濾器 #4272

不可能通過點擊 Esc 按鈕退出進階 DNS 過濾器編輯器 #4329

一旦 DNS 過濾器編輯器被開啟，點擊向下箭頭選擇的不是「使用者規則」部分，而是下面的過濾器 #4333

在 DNS 過濾器編輯器中，上/下箭頭鍵在某些操作後不能正確運作 #4362

當試圖用一個已經使用過的名字創建一個自訂的過濾器時，會出現「處理自訂的過濾器錯誤」 #4437

如果過濾規則編輯器已經開啟，點擊「使用者規則」中的「編輯」按鈕，將彈出一個窗口，用於編輯先前開啟的過濾器 #4438

在禁用應用程式的過濾功能後，瀏覽器助手繼續運作，就像沒有禁用過濾功能一樣 #4379

啟用或停用保護後，「計 30 秒禁用防護」功能的行為不正確 #4535

AdGuard 並不過濾 Craving Explorer 瀏覽器 #4544

如果使用者退出 AdGuard，並在服務運行時從助手中開啟其設定，AdGuard 將不會開啟 #4556

網路關閉後不應用 DNS 過濾規則 #4588

如果 AdGuard 的 DNS 模組被啟用，NordVPN 會幹擾 AdGuard 正常工作 #4673

在退出 AdGuard 時，助理顯示 AdGuard 沒有安裝或配置錯誤 #4663

更新窗口中的翻譯不正確 #4640

禁用「啟用流量過濾」選項並不能停止過濾 #4657

path 修飾符在 yandex.ru/images 上不起作用 #1738

$jsonprune 修飾符無法處理 jsonp #1717

過濾對結尾有點的網站不起作用 #1741

在某些情況下，過濾功能對 Google 相關網站不起作用（例如 youtube.com） #4480

AdGuard 瀏覽器助理在 Chrome 113 無法運作#4693

過濾器的改進

功能

jsonprune、badfilter、removeheader和hls應用的規則顯示在過濾記錄中 #4536

新增了 $permissions 修飾符 #419

為 $domain 修飾符新增了 regexp 的支援 #1550

新增了 $url 修飾符 #1551

改進了 $redirect 語法與 uBO 的整合 #1605

改進了 $jsonprune 修飾符的功能 #1710

$jsonprune 修飾符處理 jsonp #1717

修復

無法通過加號圖示或點擊空行來新增新的使用者規則 4519

當轉換後的 uBO-syntax HTML 的 ##^script:has-text() 規則被套用時，原始規則被新增到「過濾記錄」中 #1709

uBO 的 HTML 過濾轉換無法正常工作 #1708

當新增 $generichide 和 $generichide,badfilter 規則時，無法啟用/禁用保護 #1681

在某些情況下，$important 修飾符不起作用 #1695

$removeparam 例外情況不起作用 #1704

一個正確的規則被標記為無效 #1625

如果規則中包含 ~domain，元素隱藏異常就不起作用 #1673

版本

CoreLibs

將 CoreLibs 更新為 v1.11.59 4630

DnsLibs

將 DnsLibs 更新為 v2.1.26 4629

新增tplinkextender.net到應變網域 #183

ExtendedCSS

將 ExtendedCSS 更新為 v2.0.51

改變了IAffectedElement，使content成為可用選項 #163

小腳本

將小腳本更新為 v1.9.1

添加新的 m3u-prune 小腳本 #277

在 'set-attr' 小腳本中增加了更多可用的值 #283

改進了 'adjust-setTimeout' 和 'adjust-setInterval' 小腳本 #262

改進了 'json-prune' 小腳本 #282

修復了 'prevent-element-src-loading' 中的錯誤 #270

修復了與 'xml-prune'有關的錯誤 #289

修復了 'noopcss'重新導向的整合 #299

這次更新的主要改進包括保護的啟用和禁用速度更快，以及 DNS 保護現在是預設啟用的。此外，我們修復了錯誤，更新了 CoreLibs 和 DnsLibs，並且改進了 WFP 和 TDI 網路驅動。

更快啟用/禁用保護

我們在引擎蓋下進行了幾項重大改進，從而提高了應用程式的性能。現在首次或重新啟用和禁用保護的速度快多了。以前，由於保護功能啟用/重啟緩慢，我們面對一些問題，比如有些連線無法被過濾。從這個版本開始，這種情況就不會再發生了。

DNS 保護預設啟用

如果您剛剛安裝 AdGuard，DNS 保護會自動啟用。預設情況下，使用的是 ISP 提供的 DNS 伺服器。為了保持安全性，啟用 AdGuard DNS 過濾器：廣告、追蹤器和惡意域名的請求將被自動阻止。為了提高安全性，使用者還可以隨時從清單中選擇一個 DNS 伺服器，或通過「設定」→「DNS 保護」新增一個自訂的伺服器（比如，私人 AdGuard DNS 伺服器）。 DNS 過濾允許 AdGuard，在瀏覽器試圖連線到廣告伺服器器之前就檢測廣告和追蹤器。所以這次更新也幫助我們提高廣告封鎖的速度和質量。此外，使用「DNS 保護」，使用者可以有效地阻擋"隱藏的"追蹤器。

更新記錄

優化

預設情況下啟用 DNS 保護，使用 ISP 提供的 DNS 伺服器 #4534

新增

可以選擇在系統啟動時過濾流量而無需啟動應用程式 #4454

PIX-LINK 路由器/中繼器域轉為應變域名 #170

支援 Catsxp 瀏覽器 #4326

在重新安裝應用程式時，有一個刪除安裝記錄的選項 #4493

安裝程式的深色主題3048

修復

重啟後 AdGuard 無法啟動 #4502

過濾器更新後 AdGuard 凍結 #4456

如果在過濾記錄中選擇「被阻止」，所有的請求都會被顯示 #4525

在 Windows 7 上，應用程式無法在背景自動更新 #4494

無法安裝連結中包含 @ 的使用者腳本#4397

HaGeZi DynDNS Blocklist 的元數據更新錯誤 #4475

盡管復選框未被選中，但在系統啟動時主窗口仍開啟#4546

安裝了 Norton 360 後，過濾和使用者腳本無法運作 #1712

google-ima3 重新導向的相容性問題 #272

prevent-addEventListener和使用者腳本之間的相容性問題 #271

isEmptyObject() 的問題 #268

更新/重新安裝 AdGuard 彈出式窗口封鎖器的使用者腳本時出錯 #4574

更新

將 CoreLibs 更新為 v1.10.189 #4563

將 DnsLibs 更新為 v2.0.75 #4562

小腳本 v1.7.20

有一部分使用加密 DNS 的使用者遇到問題，即應用程式無法啟動。我們快速檢測到該問題，並發佈了熱修復。此外，我們更新了 DNSCrypt 的 DNS 戳記、CoreLibs 和 DnsLibs。

更新記錄

[優化] 將 CoreLibs 更新為 v1.10.139 #4490

[優化] 將 DnsLibs 更新為 v2.0.58 #4489

[修復] 啟用加密 DNS 時，無法啟動 AdGuard v7.11.2 #4488

In this patch we've fixed the import of settings as well as minor bugs and updated CoreLibs and DnsLibs.

Changelog

[Enhancement] Updated CoreLibs to v1.10.135 #4482

[Enhancement] Updated DnsLibs to v2.0.56 #4483

[Fixed] Error when importing settings #4473

[Fixed] Rules with $dnstype aren't possible to add #4477

本次熱修復我們解決了與網路過濾有關的問題，修復了程式錯誤，並且更新了 CoreLibs。

更新記錄

[優化] 將 CoreLibs 更新為 v1.10.119 #4465

[修復] 無法啟動網路過濾 #4455

[修復] 實驗性過濾器在更新應用程式後自動啟用 #4457

[修復] 導入過濾器時元數據處理不正確 #4452

AdGuard v7.11 Windows 版包含不少很好用的改進。現在，AdGuard 可以在基於 ARM 的電腦上運行了，並且可以過濾加密的 DNS-over-HTTPS 請求。此外，我們改進了 CoreLibs 和 DnsLibs，讓應用程式外觀和功能更加美麗便捷。

[優化] ARM 的 Windows 支援 #3067

我們新增了允許 AdGuard 在基於 ARM 的 Windows 裝置上運作的驅動程式。現在，如使用者在 64 位 ARM 中央處理器的電腦上安裝 AdGuard，我們會自動檢測到並安裝匹配的驅動程式。使用者都可以放心。

[優化] 加密 DNS 請求的過濾

現在，AdGuard 可以在無加密的 DNS 請求上過濾加密的 DNS-over-HTTPS 請求。為了開啟本功能，在進階設定中點擊「啟用安全 DNS 請求的過濾」核取方塊。

對過濾器開發者很重要

[優化] 改變了從 JSON 回應中刪除元件的語法 #1447

[優化] 新增了一個新的修飾符，用於處理 HLS（M3U8）文檔格式 #1434

[優化] 新增了對空 $path 修飾符的支援 #1591

[優化] 在 POST 請求中套用 $removeparam 參數 #1573

[優化] 實施 DNS-over-HTTPS 過濾 #1563

[修復] 在請求被阻止時 $removeparam 不起作用 #1580

更新記錄

[優化] 為過濾器清單中的自訂的過濾器新增了一個標題 #4190

[優化] 提高了深色模式下"管理密碼"窗口中輸入的字符的可見度 #4178

[優化] 改變了 AdGuard 啟動設定後系統啟動時的應用運作邏輯 #2489

[優化] 增加了複製過濾器清單 URL 的功能 #3790

[修復] 現有的過濾規則可以重復新增 #4210

[修復] 在過濾器編輯器中 Ctrl+Shift+Z 不起作用 #3756

[修復] 當應用程式關閉時，過濾功能無法在背景運作 #4344

[修復] 通知中的簽名不正確 —— AdGuard VPN #4323

[修復] 設定和過濾記錄窗口在背景開啟 #4230

[修復] 齒輪在 AdGuard 助手中不起作用#4270

[修復] 查看憑證時 Yandex 瀏覽器凍結 #3256

[修復] 重新啟動計算機後，當使用者試圖關閉應用時，AdGuard 會掛起 #4339

[修復] 在應用程式更新時過濾器也被更新 #4159

[修復] 當 AdGuard 和 Kaspersky Internet Security 同時運行時，過濾功能不起作用 #4200

[修復] 請求類型不適合過濾記錄中的欄目 #4277

[其他] 睡眠模式喚醒後，網際網路無法連線 #4293

[其他] 在刪除過濾器和擴充功能時，在通知中增加了深色主題 #4273

[其他] 更新巴西葡萄牙語 #4259

將 CoreLibs 更新為 v1.10.106

[優化] 廣告封鎖程式的名字不計入過濾器清單中 #1667

[修復] 檢查 :xpath 規則的有效性 #1606

[修復]@@||example.org^$important,document,app=firefox.exe 規則沒有被顯示為允許清單 #1546

[修復] 包含 :where() 偽類的規則被拒絕 #1609

[修復] 安全瀏覽/OCSP 無法在 Parallels 上運行 #1079

[修復] 網站 console.cloud.google.com 損壞了 #1593

[修復] 轉化 uBO 小腳本出錯 #1604

[修復] AdGuard 瀏覽器助理無法識別新網站憑證 #1619

[修復] 小米路由器的管理頁面上不顯示 QR 碼 #1538

[修復] `$removeparam' 導致預檢請求的阻塞 #1632

[修復] 網站 tickets.karls-shop.de 損壞了 #1630

[修復] 啟用 HTTPS 過濾後，網站 www.collierappraiser.com 無法加載 #1631

[其他] 改變硬編碼的 local.adguard.org 地址 #1608

將 DNSLibs 更新為 v2.0.27

[修復] 搜尋 DNS64 出錯 #1142

[其他] 在進階設定中增加了「封鎖 ECH」選項 #161

這次技術更新，我們提高了應用程式的穩定性並修復了一些程式錯誤。

這次我們發佈修補程式版本。手動過濾的更新存在了一些問題，因此我們修復它。

夏天即將來臨。現在是時候感受一下新體驗，高光時刻和新成就。我們決定以 Windows 版 AdGuard v7.10 更新迎接愉快的夏季。這個夏天還有更多驚喜！

本更新裡一個最重要的改進之一是「保護免於深層封包檢查（DPI）」功能的補充。

[優化] 在 AdGuard 隱匿模式裡新增了繞過 DPI 的功能。 #4175

深層封包檢查技術是指深度分析及過濾通過數據包內容流量的系統。使用本技術，網際網路服務供應商有機會監控經過的流量並限制客戶訪問某個內容。

現在，AdGuard 能夠修改發出的數據包，因此用戶端不會陷入 DPI 阻止的標準。這意味著，使用者可以更自由地訪問自己所喜歡的內容。不過，目前我們還無法繞過所有的 DPI 系統。我們還在繼續優化這一問題。

[優化] WFP 和 TDI 網路驅動

我們更新並改善了我們的網路驅動，改進了應用程式的運行效率，以及與其他軟體相容等問題。除此之外，我們還修復了一些與 WFP 驅動有關的錯誤。

[優化] 在更新視窗新增了深色主題#4156

一個精巧的小改進。我們在更新視窗上新增了暗黑主題。現在，深色主題的粉絲得償所願了，希望大家都會喜歡!

這次更新我們改進、修復並改善了不少功能。此外，我們還更新了 Corelibs 和 DNSlibs。所有的改進項目都可以在下述中查看。

更新日誌

[優化] 把 CoreLibs 更新為 v.1.9.76 #4274

[優化] 在 DNS 分頁的"常規" DNS 伺服器說明上新增了"無加密"圖示#4121

[優化] 完成了 WebRTC 功能的說明 #4104

[優化] 現在保護免於深層封包檢查（DPI） 狀態發送給 ReportsWebApp #4248

[優化] 我們在廣告封鎖模組上新增了讓使用者新增 DNS 過濾器的選項。

[修復] 當廣告封鎖模組被禁用時，修飾規則顯示在過濾記錄裡#4185

[修復] 進階設定中的自訂的 DNS 地址發生崩潰#4195

[修復] 關閉 AdGuard 後，DNS 過濾器不更新 #4118

[修復] 在更新期間沒有完全下載過濾規則 #4165

[修復] 在 Windows 10 上當啟用音效通知被關閉時，依然有通知聲響 #4127

[修復] 自訂的過濾器在刷新網頁後不工作 #4170

[修復] 瀏覽器助理對 HTTPS 例外中的www前綴很敏感 #4240

[修復] 通過 filterlists.com 訂閱時，過濾器名稱沒有被傳送#4193

[修復] 糾正更新標題的翻譯#4154

[修復] 如果一個過濾器有個很長的名字，"受信任"的標簽不顯示#4126

[修復] 過濾記錄中的文本標題重疊#4186

[修復] 家長監控的密碼輸入窗口中的交叉按鈕不起作用 #4266

有些使用者在使用 AdGuard 7.9 禁用「流量過濾」時可能遇到一些問題。我們提供此熱修復程式。而且我們還把握機會更新了 DNSLibs，並進行了一些小的錯誤修復。現在，應用程式的性能會更加穩定。

更新日誌

[新增] CoreLibs 升級為 1.9.43 #4150

[新增] DnsLibs 升級為 1.7.12

[修復] 禁用流量過濾會導致 AdGuard 重啟後崩潰4142

[修復] 檢查過濾器更新出錯#4143

[修復] 在我們重新啟動過濾日誌前無法禁用「顯示快速 UDP 網際網路連線（QUIC）」#4133

現在我們知道了，我們可以創造出跟希區考克一樣好的懸念！從上次更新以來，我們已經發布了三個新版本（一個測試版和兩個最終測試版本）。但是，這已經足夠了! 大家一起來迎接 Windows 版 AdGuard 7.9！我們大家等待這個版本已久。讓我們一起看一下主要的創新功能及優勢，給大家嘗嘗鮮。

請讓我們先說，我們致力於改進應用程式的性能和使用者介面。現在，用戶將會有更好的 Windows 版 AdGuard 的使用體驗。此外，我們新增了 Bootstrap 功能，改善了進階 DNS 設定。不想要使用系統 DNS 解析器作為 Bootstrap？沒問題！現在你可以自己指定用於加密 DNS 伺服器地址的 DNS 伺服器的 IP 位址。

還有什麼呢？我們修復了各種錯誤，包括自動啟用語言過濾器的問題。因此，現在 AdGuard 更穩定。當然，我們也沒有偷懶避開 CoreLibs 和 DNSLibs 的改進。大概就是這樣吧！我們希望親愛的使用者都會喜歡 Windows 版 AdGuard 的新版本。

更新日誌

[新增] 新增了進階選項以設定自訂的 DNS Bootstrap 地址 #4080

[新增] 新增了按請求的連線類型進行排序的功能 #3830

[新增] 當 AdGuard 禁用時瀏覽器助理過濾日誌無法被啟用，但它會繼續過濾3335

[修復] 當廣告封鎖模組被禁用時，針對特定語言的過濾器自動啟用 #4098

[修復] 使用者腳本的偽更新 4050

[修復] 在使用者規則設定中轉到首頁的連結 #4068

[修復] 當使用者通過過濾日誌新增新規則時，預設規則包括過濾器的名稱 #4045

[修復] 過濾器編輯器裡過濾器名稱下的填充錯誤 #3553

[修復] 安裝程式裡授權協定文本上的一個錯誤 #4060

[修復] $$規則在過濾日誌裡無法看到 #4113

[修復] 在過濾日誌中，家長監控所阻止的請求會顯示為隱匿模式的請求。 4074

[修復] 主畫面上的規則計數器將評論定義為活動規則 #3994

[修復] 無法滾動 DNS 例外畫面 #4024

[修復] 當在一個瀏覽器窗口裡啟用/禁用"在此網站”的保護時，助理圖示在另一個開啟的瀏覽器窗口裡不改變顏色

[其他] AdGuard 在 Netflix.com 上使用約 10% 的 CPU，具有該網站的保護功能被禁用 4003

[其他] 重新制作了隱私保護幻燈片上的入職動畫

[其他] 當自訂的過濾器被錯誤新增時出現的錯誤文本沒有被翻譯 #4026

[其他] 刪除後註冊表中留下關於 AdGuard 的資訊 #4064

將 CoreLibs 升級為 v1.9.34

[新增] 新增了針對特定 URL 應用修飾規則的功能 #124

[新增] 改進了對使用 Sec-Fetch-Dest 頭的內容類型的檢測 #1382

[新增] 改變了隱藏你的 IP 的預設地址 #1516

[新增] 當 AdGuard 啟用時，TLS 指紋不應改變 #1503

[新增] 改進了 HTTPS 過濾器的憑證快取算法#1402

[修復] 當使用者啟用自毀第三方 Cookie 檔案功能時，kinopoisk.ru 上的授權不起作用。#1502

[修復] 如果實施帶有$all修飾符的規則，日誌中會出現錯誤的規則 #1535

[修復] AdGuard 破壞 danawa.com 的編碼。 #1534

[修復] 在 www.adorama.com 上出現的 net::ERR_HTTP2_PROTOCOL_ERROR 錯誤 #1518

[修復] 帶有$third-party修飾符的規則在 worldvision.de 上不起作用#1523

[其他] AdGuard 在 pinning-test.badssl.com上的 pinning 檢測失敗。#1526

[其他] RegEx條目驗證錯誤 #1544

DnsLibs 升級為 v1.7.4

[其他] 開始在 DnsLibs 中使用 NativeLibsCommon #128

We once again reviewed GitHub repo and realized that we had been working for almost six months on version 7.7. And less than two months on version 7.8. Yes, there were fewer tasks in this version, but we did a good job on improving everything: Browsing Security, network drivers, CoreLibs and DNSLibs, other minor features, and – hopefully – your user experience.

[Enhancement] Browsing Security

Browsing Security is a module that blocks requests to malicious and phishing websites. You might have seen a nice looking banner caringly stating "AdGuard has blocked access to this page": that's what Browsing Security does. Now it's working a way better: requests for information about malicious domains are not sent to a server, but to a periodically updated database stored locally on your computer. This is faster and safer.

[Enhancement] WFP and TDI network drivers

We've also updated and enhanced our network drivers for Windows – WFP and TDI. Both have been helpful, among other things, to improve compatibility with other applications.

Other good stuff

And of course, there is no release without updating CoreLibs, our main filtering engine, and DNSLibs. Meet their new versions: more flexible, more powerful. As always: minor bugs have been fixed. As always: perfection has no limits.

Hope that your holidays will be safer with AdGuard.

Changelog

[Enhancement] 360 browser has been added to the list of apps filtered by default #4018

[Fixed] Browser assistant is still available after the license expires #4020

[Fixed] Update info is incorrect after manual update #3997

[Fixed] QUIC requests are blocked and shown as TCP when app is excluded from filtering

[Fixed] Different type of dialog window opens when adding a custom DNS server

[Fixed] Right click on the tray menu icon opens the main window #3908

[Fixed] AdGuard defines the Chromium browser as the Sidekick browser #4008

[Fixed] AdGuard crashes when trying to use an occupied port in proxy mode

[Fixed] Once a custom DNS server is added, in some cases it remains inactive #4042

[Fixed] The filter is not displayed in the filtering log when its rule is applied #3992

[Fixed] Bandizip is not filtered #3334

[Other] Add handling of adguard:add_dns_server URLs

Updated CoreLibs to v1.8.274

[Enhancement] QUIC SNI decoder logic #1554

[Fixed] The rule @@*$network,app=chrome.exe causes AdGuard to crash #4015

[Fixed] Failed to install a custom filter list with #include directive #1553

[Other] Support Safebrowsing V2 in the new version of CoreLibs

Updated DnsLibs to v1.6.71

[Fixed] Crash when parsing an invalid SDNS stamp #127

We’ve come a long way through ~~bugs~~ thorns to the stars and finally reached the finish line (we hope so!) Many apologies for the last few versions of AdGuard for Windows: they had to be really good, but something went wrong. In one week since the last release, with your help we have found and fixed several disappointing flaws, as well as bugs in the application drivers, which turned out to be the main issue of v7.7.1. And of course we’ve updated CoreLibs — it couldn't happen any other way!

Changelog

[Fixed] Driver installation failed on v7.7.1 #3986

[Fixed] New tab in Edge is broken when AdGuard is on #1541

[Other] Update CoreLibs to v1.8.240 #3996

Unfortunately, the larger the update, the more the risk of letting some bugs through. The latest release of AdGuard for Windows exposed several of those so we’re ready with a hotfix. Thanks to all users who sent reports to us — it wouldn’t be possible without your help! As a result, we fixed the bugs that some of you had encountered. For instance, we fixed a network filtering bug that prevented the application from working correctly. We also solved the problem with incorrect work of the tray menu icon. In addition, we slightly redesigned the “Advanced settings” block for easier navigation.

Changelog

[Enhancement] Advanced settings redesign

[Enhancement] “Disable IP” and “Fallback” text fields become inactive when no input is required

[Fixed] Clicking the desktop icon doesn’t open AdGuard UI #3956

[Fixed] "Launch AdGuard at system start-up" doesn't work correctly #3968

[Fixed] Right click on the tray menu icon opens the main window #3908

[Fixed] Service stops with a "Network filtering is absent" error

[Fixed] Downloads slow down if the server uses HTTP/2 #1533

[Fixed] “Adguard Service” causes ERR_SSL_VERSION_OR_CIPHER_MISMATCH on some sites in Chrome #1537

[Other] Upgraded CoreLibs to v1.8.227

[Other] Upgraded DnsLibs to v1.6.58

One beta and two RCs — and here comes AdGuard v7.7 for Windows! This time we didn't encounter significant difficulties on our way to the release stage, so the development cycle turned out to be fast. Hope you'll enjoy the way the new version of AdGuard for Windows works, meanwhile we'll keep moving to the top — v8.0.

The main focus of this release was to fix bugs and improve user experience. We performed tough tests and were unable to crash the app! But you can surely fix it, right? 🙂

For starters, we implemented low-level DNS settings, added the Finnish language and updated other translations.

There are not many significant changes in this version but we’ve put our energy into something no less important. We updated CoreLibs and DNSLibs, fixed various issues along the way, and did some magic with the filtering log to make it more user-friendly.

[Enhancement] Added low-level DNS settings

There is a new section named Blocking mode for DNS in low-level settings. Now you can select the response type if you've requested a DNS domain blocked by a DNS filtering rule. There are three response types to choose from.

Besides, settings with fallback servers were modified. In the previous v7.6.1 there was a simple option Enable DNS Fallback. Now users not only can enable it, but also select whether they want to use the system or custom fallback DNS. By the way, you can add several fallback servers at once.

And finally, there are DNS exclusions — domains in this list will be resolved through the system DNS.

Changelog

[Fixed] Cannot install CA certificate when "Use Unicode UTF-8 (beta)" is enabled in Windows settings #3763

[Fixed] Parental control can be bypassed with AdGuard Browser Assistant #3815

[Fixed] Conflict with Sophos Endpoint Security and Control #3791

[Fixed] Filters don't update if the Default update interval is set #3825

[Fixed] Opening extra window with a Chinese language proposition while selecting Czech language #3877

[Fixed] Filtering completely stops working for some time #3880

[Fixed] The rule must be disabled after adding the comment symbol ! but it still exists #3766

[Fixed] Ctrl-Shift-Z is not working in Filter Editor #3756

[Fixed] DNS requests don't reach client server after update #3757

[Fixed] ExtendedCSS misbehaves on images.google.com #135

[Enhancement] Finnish translations are missing yet they've been 100% completed for a long time #3898

[Enhancement] Compatibility with the Cent Browser #3342

[Enhancement] Added Sidekick to the list of default browsers #3769

[Enhancement] Make items in the tray menu inactive when we AdGuard's license is not activated #3817

[Enhancement] Change tooltips in filters editor to multiline #3870

[Enhancement] Updated translations

[Other] Unable to activate the app if the old license is outdated #3811

[Other] Browser assistant async #3824

[Other] New tray icons for AdGuard

Updated CoreLibs to v1.8.199

[Fixed] Some :xpath rules do not work #1479

[Fixed] Allow to apply $removeparam rules to all resources #1492

[Fixed] Rule with $important modifier should have higher priority than rule with $all modifier #1440

[Fixed] Browser Assistant can’t view website’s original security certificate #1422

[Fixed] CSS rules with url shouldn't be allowed #1431

[Fixed] blockchain.com is broken #1411

[Fixed] dsp-wiki.com is broken #1420

[Fixed] hepsiburada.com - HTTPS filtering issue #1406

[Fixed] hydrogenaud.io is broken in Firefox #1361

[Fixed] scarlet.be - page cannot be loaded completely #1424

[Fixed] superonline.net is broken #1413

[Fixed] CL reports incorrect errors on duplicate rules like /ads_google_ #1517

[Enhancement] Added an option to send Global Privacy Control's Do Not Sell signal to Stealth Mode #1451

[Enhancement] Added $denyallow modifier #1304

[Enhancement] Added $redirect-rule modifier #1303

[Enhancement] Added $removeheader modifier #1427

[Enhancement] Added $specifichide modifier #1166

[Enhancement] Add full regex support for $network rules #1394

[Enhancement] Allow *## cosmetic rules #1437

[Enhancement] Rules with $ in path don't work #161

[Enhancement] Add SNI scanning option for QUIC #1467

[Enhancement] Figure out why some rules haven't been parsed successfully #1472

[Other] Cannot load joongang.co.kr #1509

[Other] Improve invalid CA cert or key detection #1455

Updated DnsLibs to v1.6.52

[Fixed] SERVFAIL/timeout issue on iOS #108

[Fixed] Increase DNS timeout for DnsProxy.testUpstream #112

[Enhancement] Upgrade to QUIC version 1 #111

[Enhancement] Truncate reply to size expected by client #103

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 unlucky ones to have this problem, AdGuard will not update automatically for you. You need to check for updates manually or reinstall the app.

[Fixed] AdGuard cannot connect to the Internet to check filters updates / license status #3758

The explanation for this problem is quite technical. No reason to cite it here, you can find the detailed explanation in this comment by AdGuard's CTO.

Changelog

[Fixed] No filtering until "Filter localhost" is enabled after updating from v7.5 to v7.6 #3762

[Other] Minor fixes & improvements

Usually, it takes us north of 2-3 beta versions to prepare the next AdGuard for Windows release. But not this time: the first (and only) beta for v7.6 carried enough impact on its own. We added custom DNS filters, DNS-over-QUIC support for AdGuard DNS, and, of course, made the app compatible with AdGuard VPN.

[Enhancement] Custom DNS subscriptions support #3641

In v7.5 we introduced DNS protection module. To refresh your memory: it offered the option to select any DNS server instead of the system default as another way to enhance your online privacy. What it didn't offer is any way to customize the DNS filtering. Once you selected the server and the preferred encryption protocol, you were set.

In this release, we give you a range of new options to shape the DNS filtering the way you want. It includes several tools, all of which can be found inside the DNS filters editor section.

DNS user rules — the most basic way to block/allow DNS requests. Works very similarly to the regular User rules. Note that it supports DNS filtering syntax, which is much less complex than the syntax for network filtering.

Importing a DNS filter — click on the 'plus' icon in the bottom left corner, and you'll see a new window pop up. Click on the Import filter button and then either enter a filter URL or browse a suitable local filter. You can find a lot of DNS filters on this website. AdGuard DNS filter is the only one available by default.

Adding a custom DNS filter — accesible by clicking the 'plus' icon and then choosing the Add custom filter option. Choose a name and a description and then treat the new DNS filter like any other: import rules, add or remove them manually one by one, disable and enable the filter at will in one click.

[Enhancement] DNS-over-QUIC support

When you choose AdGuard DNS server in DNS protection, you now have an option to select DNS-over-QUIC as your encryption protocol of choice. It's the newest protocol, with lots of advantages, and AdGuard DNS is the first public DNS provider to offer it.

[Other] Improved compatibility with AdGuard VPN

AdGuard for Windows was already compatible with AdGuard VPN, but in this release we pushed it even further. We fixed several bugs and now the two apps will work more smoothly alongside each other.

Changelog

[Fixed] DNS encryption stops working #3479

[Fixed] Incorrect hotkey behavior in Filter Editor #3652

[Fixed] IPv6 failure with DNS filtering enabled #3490

[Fixed] Filtering log work incorrectly after importing #3645

[Fixed] The AdGuard Browser Assistant extension is shown as incompatible #3606

[Fixed] HTTPS certificate failure after rebooting the system #3710

[Other] Reboot is now requested if TDI driver is active during its update #3706

[Other] System theme auto switch now happens in real-time #3464

[Other] Filters won't update if update interval is disabled #3755

[Other] Introduced new crash reporter

CoreLibs updated to v1.7.201

[Enhancement] CL now checks that trusted-types CSP does not break the content script #1320

[Enhancement] Added $noop modifier #1387

[Enhancement] Added filter lists downloader module #1279

[Enhancement] Improved the way negation works for $redirect rules #1388

[Enhancement] $removeparam syntax updated, $queryprune added as an alias #1384

[Enhancement] $domain modifier is now used for target domains only in non-domain rules #1354

[Fixed] Filtering log records don't contain the original remote address when an outbound proxy is set up #1330

[Fixed] AdGuard doesn't filter domains when HTTPS filtering is disabled #1343

[Fixed] Exclusions with $elemhide,jsinject,extension disable HTML filtering rules #1337

[Fixed] Filtering log doesn't show information about cookies #3406

[Fixed] Regexp rule doesn't match URL #1311

[Fixed] Foreign requests get into Filtering log with enabled DNS module #3411

[Fixed] URL contains extra slash while matching against filters and some rules are not applied #1338

[Fixed] Wrong filter is shown in Filtering log #1312

[Fixed] FTP pages are broken #1351

[Fixed] No action is suggested when AdGuard CA's key is damaged #1415

[Fixed] Userscript exclusions do not work as they should #1425

[Fixed] Valid rules do not pass validation checks #1419

[Fixed] min-length is not working in HTML filtering rules #1383

[Other] HTML is not detected on some sites #1308

[Other] local.adguard.org certificate is not re-issued when it expires #1348

[Other] ERR_HTTP2_PROTOCOL_ERROR on some websites #1374

[Other] Rules with $extension modifier unblock blocked requests #1350

DnsLibs updated to v1.4

[Enhancement] Added missing DNSCrypt info in DNS stamps of platform adapters #90

[Enhancement] Optimistic DNS #83

[Enhancement] DoQ/DoH/DoT queries are now retried before resorting to fallback #86

[Other] Encoding errors #79

[Other] Added DoQ support in DNS stamps #84

[Other] Added an option to pass custom filtering rules without file #30

[Other] Added an option to specify IP_BOUND_IF/SO_BINDTODEVICE for outgoing connections #78

Today we are launching a small but still very important hotfix. Namely, the compatibility with the new Chrome 87 was improved and the CoreLibs was updated.

[Other] ERR_HTTP2_PROTOCOL_ERROR on some websites #1374

This week Chrome 87 was released, which has a compatibility problem with AdGuard when using the HTTP/2 filtering protocol - some sites may experience regular hangs and download errors. In this update we have improved HTTP/2 filtering compatibility with Chrome 87, it is recommended to upgrade to the new stable version as soon as possible. :)

Changelog

Upgraded CoreLibs to v1.7.150

[Enhancement] Add $ping content type #1258

[Enhancement] Check that trusted-types CSP does not break the content script #1320

[Fixed] AGFDVSocket doesn't return original peer address in case of outbound proxy set #1330

[Fixed] AdGuard doesn't filter domains when HTTPS filtering is disabled #1343

[Fixed] Exclusion with $elemhide,jsinject,extension disable HTML filtering rules #1337

[Fixed] Filtering log doesn't show information about cookies #3406

[Fixed] Problematic userscripts #1273

[Fixed] Regexp rule doesn't match URL #1311

[Fixed] The foreign requests get into filtering log with enabled DNS module #3411

[Fixed] URL contains extra slash while matching against filters and some rules are not applied #1338

[Fixed] Wrong filter is shown in Filtering log #1312

[Fixed] hkclubs.samsung.com #1340

[Other] Fix errors encoding under Windows #79

[Other] HTML is not detected on some sites #1308

[Other] local.adguard.org certificate is not re-issued when it expire #1348

[Enhancement] Improve socket connect with hostname provided (for Proxy mode) #123

[Other] $generichide rule causes that assistant is showing that AdGuard is disabled #7

[Other] Connection error after waking computer from sleep mode #3412

This is mostly a bugfix patch yet it has some noteworthy changes. For instance, we fixed DNS-related bugs, Stealth Mode, and boosted our CoreLibs filtering engine.

Changelog

[Fixed] AdGuard ignores some of the Stealth Mode user settings #3516

[Fixed] DNS filtering blocks Internet connection #3526

Upgraded CoreLibs to v1.7.114

[Enhancement] Added $ping content type #1258

[Enhancement] #@# without any domains specified now disables the rule completely #1296

[Enhacement] Added $redirect-rule modifier #1303

[Enhancement] Trusted-types CSP does not break the content script #1320

[Fixed] AGFDVSocket doesn't return the original peer address in case of outbound proxy set #1330

[Fixed] AdGuard doesn't filter domains when HTTPS filtering is disabled #1343

[Fixed] Exclusions with $elemhide,jsinject,extension disable HTML filtering rules #1337

[Fixed] Filtering log doesn't show information about cookies #3406

[Fixed] Problematic userscripts #1273

[Fixed] Regexp rule doesn't match URL #1311

[Fixed] Path combining helper adds an extra slash #1338

[Fixed] The filter ID of the triggered rule for a blocked request is not defined correctly #1312

[Fixed] Issue with hkclubs.samsung.com #1340

[Fixed] Encoding errors #79

[Fixed] AGFDVSocket doesn't return original peer address in case of outbound proxy set #1330

[Fixed] OCSP checks aren't passed through the selected DNS #1328

[Fixed] Redundant errors when local.adguard.org accessed from non-HTTPS-filtered processes #1056

[Fixed] $badfilter rules are sensitive to domain lists #1331

[Fixed] Speed is capped at 400-500 Mbps #702

[Other] Partial HTML processing issues #1308

In this hotfix, we enhanced the filtering, fixed minor issues and updated the CoreLibs engine.

Changelog

[Fixed] Update from 7.4.2 to 7.5 - HTTPS exclusions are doubled in the list #3508

[Fixed] Parental Control exit issue #3511

Upgraded CoreLibs to v1.7.64

[Enhancement] Add $ping content type #1258

[Fixed] Problematic userscripts #1273

[Fixed] AGFDVSocket doesn't return original peer address in case of outbound proxy set #1330

This release incorporates all the best of two previous beta versions and two release candidates. Double-checking neve hurts, right?

There are four key changes, starring DNS filtering that will protect your DNS traffic from interception by ISPs and fraudsters. Another killer feature is an updated Stealth Mode. We’ve expanded its functionality by adding four new options that prevent Windows from collecting user data. Plus, license activation via social login and pausing protection for 30 sec. A good advanced toolkit for an ad blocker, we’d say.

DNS filtering

This feature has been long present in other AdGuard products. Not only will the DNS module protect your DNS traffic from the ISP’s and fraudsters’ interception, it will also block ads. However, it’s important to stress that the DNS doesn’t replace normal protection, rather it works best when coupled with it.

We have a wide and regularly updated database of domain names, and now you can set it up on AdGuard for Windows.

You can choose the server type (DNS-over-HTTPS/DNS-over-TLS, etc.) that suits your needs best or add your own custom DNS server. Also, here is a link to our Knowledge base, where we have collected the most popular DNS providers and added a quick setup option. One click, and your DNS is ready for use.

Disable Windows 10 Tracking

Windows Tracking has four options: you can disable Windows telemetry, turn off advertising ID, disable Windows Defender automatic samples submission and disable WAP push message routing service.

To illustrate the significance of disabling system telemetry, let’s take Cortana, a virtual assistant developed by Microsoft. Its feature set is enabled by default and periodically sends usage and performance data to Microsoft. This assistant helps, but it also gathers a lot of statistics. If you, as a user, have privacy concerns (which is completely understandable and even expected in this day and age), we’ll help to disable telemetry nice and easy.

As for removing an Advertising ID, if you checkmark this option, you will stop receiving Microsoft ads (in the action center, start menu, etc.).

Authorization and license activation via social networks

This function has already been available in our app for Android. We decided to add it here, too, because it’s truly a convenience feature.

Now, you have one more option of how to activate your license: not only via logging to your AdGuard personal account or manually entering your license key. If the email from your AdGuard personal account and the email you use for authorization in Google or Facebook are the same, you can simply authorize via these social networks. No more trying to remember email/password from your personal account and entering it! One click, and you are logged in and your license key is activated.

Pause protection for 30 seconds

In v7.4 we introduced the new BA – more independent, glorious and autonomous. But despite it’s good in many aspects, some users asked us to return one missing thing from the old Assistant. So we did.

The old Assistant had a menu option ‘Do not filter for 30 seconds’. For instance, this function will help when you need to visit a website that won’t work when an ad blocker is enabled. In this case it makes sense to briefly disable filtering and see its content. That’s what the returned back ‘Do not filter for 30 seconds’ is also used for. But we went further and made it more convenient by adding a new function called ‘Disable protection for 30 seconds’. It will disable filtering on all websites for the same time period. You can find it in the tray menu of the main app.

Four major tasks don’t seem like a big deal. Actually, we performed many more tasks, but some of them have been omitted.

Changelog

[Enhancement] Allow select several content types for the shown records in the filtering log #3392

[Fixed] Slow UI performance in the main window #3322

[Fixed] Filtering log shows wrong type of applied stealth-mode option #3423

[Fixed] Connecting to a DNSCrypt-protected DNS causes AdGuard to throw a connection error #3455

[Fixed] Assistant issue: AdGuard not installed or installed incorrectly #3469

[Fixed] Recently added filter won't show up in the filter editor #3340

[Fixed] List of built-in DNS servers is doubled on UI #3456

[Fixed] Selecting Simplified Chinese leads to problems with subscriptions #3457

[Other] Exit from "License" tab via clicking "Esc" #3385

[Other] Do not block Exit in context menu when service is failed #3403

[Other] "Not Found" icon carries over to other Settings sections #3413

[Other] Change the priority of languages for the situation without zh-TW translations. #3442

[Other] Wrongly use zh-CN encoding in zh-TW interface everywhere. (v7.5 beta 1) #3443

[Other] UI crashes during localization process for ZH-cn locale #3470

Upgraded CoreLibs to v1.7.54

[Fixed] Unhandled C++ Exception in finishWithResult() #939

[Fixed] Problematic userscripts #1273

[Fixed] Process name detection causes scary warnings in Windows Security #1316

[Fixed] Filtering log doesn't show information about cookies #3406

[Other] ERR_CONNECTION_RESET #3468

Upgraded DnsLibs to v1.3.10

Minor changes

Here we go - the Hotfix 2! A few more UI improvements, now it runs a lot smoother. Also, we paid special attention to the Firefox compatibility problem. Five quick stitches and AdGuard for Windows is patched up as good as new.

[Fixed] Date format view is invalid with some system language settings: #3136

[Fixed] The latest windows nightly version cannot automatically update local rules: #3347

[Fixed] Firefox policies page: #3336

[Fixed] Slow Filter Update which leads to UI hang: #3348

[Fixed] Disabling AdGuard Assistant will remove HTTPS certificate in Firefox when AdGuard is Closed into the background: #3352

Release rule №1 (or Murphy’s law, if you like): even when everything seems perfect, one or two hotfixes follow the new version.

This is a minor post-release fix. We’ve slightly tweaked UI trial windows, so now ‘I have a license’ option is not hidden anymore in some cases. Also, fixed the issue when a message can't be sent to support. And we also took our chance to polish a few other important things under the hood.

[Fixed] The trial window localization issue #3333

[Fixed] Unable to send a message to support #3337

There's a clear headliner for the new AdGuard for Windows update: AdGuard Browser Assistant. It's a browser extension to help manage filtering right from the web page that replaces the old Assistant. We also fixed a bunch of bugs and overall enhanced the app to work faster and better.

Browser Assistant

By developing this new product, we've resolved a couple of pretty important issues that the old Assistant had, without losing in functionality.

[Enhancement] Browser Assistant #2985

Meet our new AdGuard Browser Assistant! From a mere dependant userscript in AdGuard desktop apps it has evolved to become a full-fledged browser extension.

Obviously, new Assistant has the functions of the old one included but it’s far more cool and user-friendly. And it came in extremely handy, helping us solve three major problems at once:

Former AdGuard Assistant was a dependent userscript able to communicate with the app only using a certain protocol. On the contrary, new Assistant is independent: it’s installed in a browser, and you don’t need to wait while the script would be injected into the filtered web page. Putting it simply, it is more autonomous. Technically the new Assistant can be used without the app, although the app is required for the full capacity.

When AdGuard desktop app and our browser extension were used in so-called integration mode, the extension icon took over Assistant's functions. However, they could hamper each other’s work. Some websites would stop being protected by the desktop program and be backed up only by the extension which has less possibilities. With new Assistant being extension itself, there is no need to install our regular browser extension anymore, which means there is no risk of an incompatibility.

Some people didn't like seeing the old Assistant’s presence at webpages, plain an simple. New Assistant's icon resides safely next to the browser's address bar – zero chance to stand in the way of website's content.

[Enhancement] Own settings tab #3118

From now on, you can open this tab and get the Assistant for your default browser in one click. And in case your browser is a rare one, you can always lay on the legacy non-extension version – it works everywhere.

[Enhancement] Onboarding process #3119

During the installation, AdGuard determines your default browser and prompts you with a download link for Assistant. If your browser is not compatible with AdGuard, the legacy version is automatically enabled.

Changelog

[Fixed] Cannot report a website from Assistant when UI is not running #2138

[Fixed] Advanced Editor clears user rules #2142

[Fixed] AdGuard not responding after resuming from sleep mode on laptop #2861

[Fixed] Wrong date on statistics #3015

[Fixed] Crash on viewing request details in filtering log #3074

[Fixed] Wrong highlight for Stealth Mode exclusions in filtering log #3123

[Fixed] Some processes are active after AdGuard update bug installer #3126

[Fixed] Some windows are not centered #3127

[Fixed] Scroll issue with touchpad in language combobox #3129

[Fixed] Can't add apps from Blitz's subdirectory #3141

[Fixed] License activation dialog design issues #3145

[Fixed] Support button returns 400 Bad Request #3155

[Fixed] No longer able to add filters that do not have a .txt extension #3165

[Fixed] Unnecessary colon is displayed for Yandex-Turbo redirect userscript #3176

[Fixed] Individual userscript incompatibility #3201

[Fixed] Browsing security notifications don’t work #3203

[Fixed] Using extension w/app allows user to bypass Parental Control #3219

[Fixed] Screen is twitching after disabling the extension #3229

[Fixed] Pale buttons' text while starting the AdGuard #3236

[Fixed] Connection errors #3237

[Fixed] After reinstalling the application does not work #3238

[Fixed] "AdGuard Browser Assistant is not installed or configured incorrectly" error #3241

[Fixed] Some requests’ names are cut and not displayed in the filtering log #3249

[Fixed] Browser restart is required after AdGuard update #3250

[Fixed] Disabled userscripts reenable automatically after an update #3258

[Fixed] AdGuard starts in a windows instead of being minimized in the system tray #3276

[Fixed] "AdGuard installed successfully" window pops up after a reboot #3278

[Fixed] UI won't start after an update #3299

[Fixed] Statistic isn't incremented #3311

[Fixed] Native extension api GetOriginalCert returns wildcard cert if it is in cache #3315

[Enhancement] Filtering log is on pause while import #1997

[Enhancement] Update Advanced Uninstall Utility #2940

[Enhancement] Using the current browser for the webpage opening #2099

[Enhancement] AdGuard GUI unnecessarily raising Windows platform timer resolution #2734

[Enhancement] Enabling HTTPS filtering for a portable FF is now easier #2735

[Enhancement] An option to hide blocked QIUC records in the filtering log #2912

[Enhancement] Description about opening AG main window at system start-up has been reformulated #3016

[Enhancement] Description for the "Launch AdGuard at system start-up" option #3082

[Enhancement] Some items have been renamed or added in the tray menu #3103

[Enhancement] Get rid of double negative in "filter EV" section #3133

[Enhancement] Wizard's provided filters to the pre-downloaded defaults #3162

[Enhancement] Handling the well-known errors during installation is made more user-friendly #3163

[Enhancement] "What's new" screen after the major app update #3169

[Enhancement] Send Console and Host logs to the Sentry among with the Service logs #3172

[Enhancement] Add new Edge browser support #3217

[Enhancement] HTTP proxy mode's description is disabled #3227

[Enhancement] Update CoreLibs to 1.5.238 #3246

[Enhancement] Browser Assistant now supports Waterfox and Cliqz browsers #3264

Corelibs updated to v1.5.269

[Fixed] Rules with :style() are converted incorrectly #1149

[Fixed] Cosmetic rules can be used as CSS rules #1293

[Fixed] Basic rules with a wildcard in top-level domains aren't working #1298

One of the best things about Christmas is that everyone gives each other presents! So here’s our humble gift to you: AdGuard v7.3 for Windows. We hope you’ll like it, because we put a lot of effort into its development.

This version features improved ad blocking (thanks to added support for scriptlets and new modifiers), some major networking improvements and a new option to activate AdGuard via your adguard.com personal account.

[Added] Scriptlets support

Scriptlets is a powerful ad blocking instrument. You can say that scriptlet is an internal script (a mini-program) that we install with the app, and then execute that script with the help of filtering rules. Putting it simply, scriptlets allow us to modify how the code of the web page behaves. As for the practical use, this helps to fight adblocker circumvention, for example, and is also useful in some other cases.

[Added] $redirect and $rewrite modifiers support

They are practically the same modifiers, and they allow to substitute resources. If you are not a custom filtering rules aficionado, don't bother with it. Just know that it is yet another instrument in the hands of filter developers that helps to block ads more efficiently.
We should mention that both $redirect and $rewrite modifiers are still kind of working in test mode, but they are fully operational and you should feel free to use them.

[Improved] Proxy mode can now be used alongside automatic traffic filtering #2696, #3055

Previously, you had to choose between using AdGuard to filter all traffic on the current system, or setting it up as an HTTP proxy to funnel traffic of particular apps or devices through AdGuard (but without filtering it).
Now you can have the best of both worlds, and even more: filter application and browser traffic on the current PC and at the same time use AdGuard as a filtering proxy for other devices (yes, now their traffic will be filtered too). To select the configuration you want go to Network settings.

[Added] Activating AdGuard by linking personal Account #2931

Something we’ve tested in other AdGuard products and found positive feedback is an option to activate AdGuard by linking the app with your adguard.com account. In this case, instead of entering the license key, you put in your Account credentials (login/password). The app automatically looks for a valid license key in your Account and uses it to activate AdGuard.

Ad Blocking

[Added] Enable the HARs writing as an advanced option #2402

[Fixed] False link interception #3117

[Fixed] Disabling HTTPS filtering for an app works incorrectly #3111

[Fixed] Cookies time-to-live resets to zero #3115

[Fixed] Automatic apps filtering gets disabled after an app update #3076

[Fixed] Userscript working in pre version 7 releases not working in post version 7 releases. #2937

[Fixed]Error occurred while reloading protection, doesn't change the filtering status #2965

[Fixed] Cannot find the file specified #2969

[Fixed] Incompatibility between AdGuard and HTTP Debugger #2979

[Fixed] Cannot add executable from %Appdata% to the filtering #3023

[Fixed] Some problems with user filter #3044

[Fixed] Cannot add $network rules to the user filter #3058

[Fixed] Atom package installer doesn't work when protection enabled #2988

[Fixed] Firefox Private Network issue #2981

[Improved] Change the approach to the way how we start cert installer #2973

UI

[Added] Add HTTPS filtering step to the initial wizard #3125

[Added] Import-export advanced settings #2964

[Added] Trial period should be started explicitly #2980

[Changed] Checkbox for new rule is now shown as disabled in Filter editor #2893

[Fixed] Diagonal resizing by dragging the bottom corners is flawed #2943

[Fixed] Extra error entries in the log file #2875

[Fixed] Filter descriptions in Filter editor lack spaces in Traditional Chinese localization #2853

[Fixed] Main window now correctly reflects the time of the last filters update check and not the time of the last actual filters update #2982

[Fixed] Incorrect placement of proxy configuration warning #3065

[Fixed] UI performance drops when you use search on the “Add filter” screen #3090

[Fixed] Main window is shown next to the settings wizard #3100

[Fixed] Poor line break on Browsing Security screen #3101

[Fixed] Repeated clicks on “Debug mode” in tray menu bring up the slow filtering warning #2996

[Fixed]Buttons Collapse, Expand, Close look bad #2722

[Fixed] Userscript is reported as updated if version contains a letter #2819

[Fixed] Drag&Drop issue #2961

[Fixed]Filtering log doesn't show applied rules #2998

[Fixed] Dark theme inner window issue #3033

[Fixed] Wrong request type in the filtering log #3059

[Improved] Microsoft Edge Beta cannot be added to filtered app in AFW #3060

[Improved] Remove old strings from translations #2926

[Improved] Improve the license check window #2939

[Improved] AdGuard Personal CA keeps coming back #1306

[Improved] Re-design About" screen" #2675

[Improved] There is no link to the list of changes in the latest versions #2715

[Improved] The text is not centered on the main screen #2716

[Improved] Use custom adguard: scheme for adding userscripts #2838

[Improved] Hover on maximize button looks bad #2840

[Improved] Strip identifying information from the logs when doing export #3022

[Improved] Centering of icons in Settings #2727

Networking

[Changed] Legacy and regular Microsoft Edge executables separated in “Filtered Apps” #3061

[Improved] We should check the internet availability before sending a support request #2925

Other

[Added] New versioning system #2896

[Changed] Flag icons removed from the languages selector #2905

[Changed] “Too many filters” warning now requires more enabled filters to trigger #3056

[Fixed] Reset statistics feature works incorrectly #2923

[Fixed] Settings reset doesn’t set window mode to its default state #2924

[Fixed] Unable to remove Spotify from the list of filtered apps #3091

[Fixed] Several apps with the same name can’t be added to the list of filtered apps #3092

[Fixed] Crash after language change #3108

[Fixed] Filters metadata is not updated for some filters #3036

[Fixed] AdGuard occasionally doesn’t delete old log files #2874

[Fixed] AdGuard.Core.Tools crashes on the app uninstall #3097

[Fixed] File or folder is corrupted #2984

[Improved] AdGuard GUI unnecessarily raising Windows platform timer resolution #2734

[Improved] Transfer GM property when the user changes the userscript's name #2739

[Improved] Improve the Advanced Settings logic #2915

[Improved] Filter installer's crash report names #2971

[Improved] Pass the empty parameter's value in the query string #3038

[Improved] AdGuard now adapts its time&date format according to system settings #2945

Rarely there's a critical level bug that shows itself over 2 months since the last release, but here we are. We can't really call this update a hotfix, but it's certainly urgent. This patch fixes a bug that in some circumstances could break cosmetic filtering on all webpages.

Some users reported critical compatibility issues in AdGuard 7.2, mainly with Emsisoft software. This is a hotfix that will solve these problems, and we also seized the opportunity to update CoreLibs and make some other changes.

You can help us make sure such incidents won't happen again by joining our beta testing program. Millions of AdGuard users will thank you (and you'll even get a beta tester's license key for free)!

[Fixed] WFP driver incompatibility with Emsisoft software #2957

[Fixed] E-mail text field issue in Support window #2951

[Fixed] Issue on the protection startup #2952

[Fixed] Window buttons tooltip localization #2953

[Fixed] Couldn't enable the proxy mode #2974

[Fixed] The port field is always highlighted #2976

[Fixed] Advanced settings translation #2944

[Improved] Additionally inform users about required reboot #2946

[Improved] Added a data limit to the length of sent logs in the installer crash reporter #2968

It’s showtime: let’s welcome AdGuard 7.2 for Windows official release.

For several months, we have been working in full swing on everything - design, performance, compatibility issues with other programs, general filtering improvement and much more. And now it’s time to tell you in detail what the new version is capable of. So let’s take a look at all changes in this update.

[Changed] Installer redesign #2574

When the visual style of your app’s installer doesn’t fit the visual style of the app itself, it’s not good. Same as wearing sandals with socks. So we fixed it!

The new installer looks so good, sometimes we uninstall AdGuard just to look at it once more. Hope you like it just as much as we do! And if not, no big deal: you’re not going to come across it too often, hopefully.

[Added] Installer crash reporting tool #2566

One of the most annoying types of crashes, both for users and developers, is when the app crashes during the installation. Our usual crash reporting tool was useless in such cases. What’s the logical solution? Correct, to give the installer its own reporting tool!

As you can see, it looks almost exactly the same. Nothing will be sent without your consent, and you can also add a comment with the description of the problem to help our developers fix the crash faster.

[Added] “Filter localhost" advanced setting #2830

Some apps, for example antiviruses, may use localhost for interactions between their components. In rare cases it could lead to compatibility problems. Now it’s possible to manage filtering of localhost with the help of the new setting.

Be sure that you know what you’re doing before messing with any of the advanced settings!

You can find this setting among advanced settings. By default, it’s disabled. We advise to try to enable it only if you experience very serious issues, e.g. when web pages don’t load or there’s no internet connection.

Ad blocking

[Fixed] Stealth mode settings reset after the app update #2839

[Fixed] HTTPS filtering is disabled by default for the newly added applications #2846

[Improved] Automatic filters detection algorithm #2692

[Improved] Automatic detection of certificate issues in Firefox #2782

[Fixed] AdGuard does not filter Iridium browser #2918

[Fixed] Incompatibility with Epic Browser #2927

[Improved] Update Assistant and Wot to 4.3.18 and 1.1.16 respectively #2942

Networking

[Fixed] AdGuard closes connections after a reconfiguration #2841

[Fixed] Connection errors on Windows 10 #2843

[Improved] WFP/TDI drivers have been updated #2889

UI

[Changed] Selector color in dark mode #2749

[Changed] Now separate windows are used for Support and About dialogues #2619

[Changed] Blocked stun/turn requests now have a prefix in the Filtering log #2638

[Changed] Users can now access Settings, About and Support windows even when protection failed to start #2892

[Changed] “Use localhost for injections” setting has been renamed to “Intercept TCP connection requests" #2859

[Fixed] Minor interface issues #2761

[Fixed] Issues with accessibility for visually impaired users #2682

[Fixed] Cropped text on the filters update screen #2698

[Fixed] AdGuard GUI unnecessarily raises Windows platform timer resolution #2734

[Fixed] Some text is not visible in dark theme #2767

[Fixed] Date on the filters update screen goes beyond the frame #2849

[Fixed] Fixed support menu window (UI) #2910

[Improved] Check for email validation before submitting a support request #2911

[Fixed] Uninstallation via uninstall shortcut #2916

[Improved] UI elements should be aligned #2922

Other

[Changed] Atom browser has been added to the list of apps filtered by default #2688

[Changed] Localizations have been updated

[Fixed] Post-installation notification sequence #2750

[Fixed] Switching between update channels is carried out improperly #2806

[Fixed] The application doesn’t start after the update #2798

[Fixed] AdGuard hangs after the update #2856

[Fixed] Information about old installers is stored in %ProgramData% #2869

[Fixed] Filter update notification does not disappear on Windows 7 #2873

[Fixed] AdGuard does not handle alphanumeric versions properly #2876

[Fixed] Compatibility issues

[Improved] Handling of filter subscription detections #2517

[Improved] Translations update

Usually, new stable versions are preceded with a number of betas and take longer than a month to develop. But this one is a bit different, its purpose is mainly to fix some incompatibilities (such as Windscribe VPN), so it makes a lot of sense to release this version as soon as possible. It should also spark interest in Firefox users, as we addressed several certificate-related problems unique to that browser.

Ad blocking

[Fixed] Manual blocker options bug #2677

Network

[Fixed] AG certificate is not removed on the app uninstall or reinstall #2772

[Fixed] Certificate gets installed into the wrong system storage #2756

[Fixed] Compatibility issues with Sophos AV #2710

[Fixed] Cookies are getting removed even though self-destructing cookies options are disabled #2714

[Fixed] Windscribe extension compatibility #2703

UI

[Changed] Domain name is now shown in the filtering log in all cases when it's detected #2691

[Changed] Translations have been updated #2697

[Fixed] AdGuard settings respond slowly when Parental Control is enabled #2687

[Fixed] Release channel label is missing #2695

Other

[Fixed] "Hide User-Agent" flag state is not passed properly to web reporter #2732

[Fixed] AdGuard crashes randomly when you open settings #2685

[Fixed] Userscripts' update channels don't match app's release channel #2694

Finally, we're pretty sure we are done with eliminating bugs that were preventing us from sharing with you all the awesome new stuff that awaits you in the new version of AdGuard for Windows. So, welcome: AdGuard 7.0! From the very start you'll notice the difference, as you'll be greeted by renovated UI design. And the more you use the new version, the better you'll find it, hopefully: brand new CoreLibs filtering engine will make ad blocking better and faster. There are more goodies inside, so let's get to the gist.

[Improved] UI and installer redesign #2574

It is somewhat of a tradition by this point to have a UI redesign with each major AdGuard for Windows version upgrade. This time will not be an exception. AdGuard 7.0 for Windows will look very different from the current familiar version. Yes: AG for Windows now has a dark theme too! Love it or hate it, it's there, it's optional and you are free to embrace it or ignore it altogether.

The installation wizard follows the trend and gets a redesign too. It only makes sense, because the installer is the first thing new users see when they start their acquaintance with AdGuard, and it better be good! Hope you'll find it an upgrade too.

[Improved] Corelibs

Everybody knows what CoreLibs is by this point, but we'll remind anyway: it is a filtering engine that drives the whole process of ad blocking in most AdGuard products, AdGuard for Windows included. And with every new version of CL these products become better: the quality of ad blocking increases, they work faster and become more stable. This beta of AdGuard 7.0 for Windows features the most recent of CoreLibs version, which means this is as good as it gets. Well, at least until the next CoreLibs update :) ,In this beta we make an emphasis on UI changes but also fix several crashes. We also took this opportunity to introduce a new userscript — AdGuard Extra.,This is more of a hotfix than a beta. Some Firefox users reported problems with browser freezing. We determined that this behavior was a sequence of hanged connections, which in its turn was caused by a CoreLibs bug. It’s crucial to eliminate all such bugs before we release a stable version (which will be soon), so here we are.

[Added] Automatic crash reports #2298

Sometimes apps crash, and you can do nothing about it. Reasons can be very different, and so are solutions. To be able to investigate every crash individually and find a proper fix to it, we add integration with an automatic crash report system. If AdGuard crashes, upon the next launch you'll be asked if you want to send a crash report.

Nothing will ever be sent without your consent, and if you want to know what exactly is in the report, you can check out our Privacy Policy. We'll appreciate each and every report, as it will help us greatly in making AdGuard for Windows more stable.

[Added] AdGuard Extra extension #2648

In some complicated cases the usual approach with filtering rules just doesn’t work. In particular, in some cases of ad blocker circumvention/ad reinjection. So we came up with an alternative solution — a userscript. For those unfamiliar, userscripts are basically mini programs that modify web pages and augment browsing.

AdGuard Extra does it in a way that makes it harder for websites to employ the circumvention/reinjection techniques. AdGuard for Windows is the second AdGuard product to get this addition, we are thrilled to see it in action and read your feedback on it.

Ad blocking

[Changed] Сustom filters do not support powerful modifiers anymore unless allowed explicitly by user #2392

[Fixed] Custom filters are always displayed like they are up-to-date #2501

[Fixed] Issues with Firefox certificate #2390

[Fixed] Сustom apps with Cyrillic symbols in the path are not filtered #2542

[Improved] The list of URL parameters to strip in the Stealth Mode module has been made customizable #2396

Network

[Fixed] Service connection issues after hibernate/sleep #2438

UI

[Added] [Nightly] Filtering log - open url #2599

[Added] An option to add/remove filters from the General settings screen #2620

[Added] CoreLibs release version to the About section #2420

[Changed] AdGuard Assistant extension name #2643

[Changed] Notification text for the case when protection status is changed via the Assistant #2251

[Changed] UI changes on Trial period & License screens #2657

[Fixed] "BlockTypeRuleDescription" wrongly used as a rule in the filtering log #2663

[Fixed] AdGuard splash screen appears even when /nosplash is specified #2434

[Fixed] Date format for Arabic localization #2477

[Fixed] Filter name is displayed in the Rule column in the filtering log #2634

[Fixed] License activation window glitch #2628

[Fixed] Notification's text is out of its bounds #2662

[Fixed] Rule Editor suggest wrong exclusion for $$ rules #2630

[Fixed] Rules from disabled filter lists are accounted for in the statistics #2497

[Fixed] Scrollbar in the settings is too sensitive #2514

[Fixed] The displayed rules in Filter editor are not refreshed after clicking on the "X" button in the search bar #2451

[Fixed] The search in the "Settings" view doesn't work properly #2417

[Fixed] UI window can only be dragged when the left mouse button is pressed #2621

[Fixed] Update channel resets from "Nightly" to "Release" after settings get reset to defaults #2614

[Improved] Chinese date format is now used for filters' update time in Chinese localization #2496

[Improved] Descriptions for Stealth Mode options have been updated #2491

[Improved] Filtering log now indicates what cookies were modified #2387

[Improved] Filtering log search syntax has been extended #2651

Other

[Added] Chromium-based Microsoft Edge to the filtered applications list #2548

[Changed] Localizations has been updated

[Changed] Logging has been made less verbose where it's not necessary #2425

[Changed] The list of apps filtered by default has been updated

[Changed] Translations have been updated

[Changed] Unicode marker (BOM) has been removed from the userscript content #2601

[Fixed] AdGuard crashes

[Fixed] AdGuard doesn't automatically detect system language #2622

[Fixed] AdGuard hangs after exiting the sleep mode #2649

[Fixed] An issue with userscripts updates #2500

[Fixed] Application update resets Assistant settings #2505

[Fixed] Compatibility problems

[Fixed] Empty lines in custom filters are imported as rules #2473

[Fixed] Error deleting backup file #2582

[Fixed] Error while doing the update check #2654

[Fixed] Excluding an app from filtering also excludes all other apps with the same executable name #2453

[Fixed] Greasy Fork userscripts display an error when checking for updates #2447

[Fixed] Installer startup delay #2388

[Fixed] The English language is set by default #2664

[Fixed] User filter rule editing bug #2584

[Improved] Additional userscript parameters are now stored when you export settings #2367

[Improved] AdGuard now checks if the userscript is already installed before downloading it #2406

[Improved] AdGuard-related system settings (e.g. UI window's size etc.) can now be imported along with the app settings #2393

[Improved] CoreLibs has been updated

[Improved] The way to get userscripts' and filter subscriptions' content #2379

This version makes a strong accent on the Networking issues. This doesn’t mean everything else was abandoned, on the contrary, there’s been a lot of ad blocking- and UI-related fixes and improvements, just the network-related fixes happened to be the most important ones.

[Fixed] Unrelated TCP connections get reset when starting AdGuard service #2291

AdGuard needs to reset connections when it starts/restarts its service in order to properly filter them. What AdGuard doesn’t have to do is to reset connections that it is not going to filter anyway. So from now on, it won’t do it, as simple as that.

[Fixed] Avast Free prevents AdGuard from suppressing QUIC #2310

The current way of whitelisting apps from filtering for WFP driver has been extended to TDI driver. It allows to avoid compatibility issues with other software, especially with antivirus software.

[Improved] TLS version has been upgraded #2337

Up to this moment we were using a draft of TLS 1.3 technology (#2155), as we always want to be at the cutting edge. Now, as TLS 1.3 standard was officially accepted by IETF, we are happy to say that AdGuard supports the most modern encrypting standards.

[Improved] Popup Blocker has been updated to v2.5 #2295

Popup Blocker is an extension (userscript) that is added to AdGuard by default. As it’s clear from its name, it helps block various popup windows (most of which are all kinds of ads). It’s been around forever, but the new version for the first time features its own UI accessable from “Extensions” settings tab. You can whitelist websites there or disable notifications for certain websites. The blocking capabilities have been improved too, of course.

[Changed] TLS 1.2 is used by default if Avast is detected #2368

As we’ve said earlier, TLS 1.3 is the current standard, but some antiviruses still use v1.2, notably Avast. We would like to completely switch to v1.3 but have to take this into consideration.

[Fixed] Application update resets Assistant settings and restores deleted extensions #2365

There won’t be enough fingers combined on hands of all people in our office to count the number of times users complained about this issue. One of our current priorities is to make the process of updating AdGuard as smooth as possible, and certainly preserving users’ settings is a big step in that direction.

Ad blocking

[Fixed] Duplicate EV certificate messages #2282

[Fixed] Twitch desktop app is not filtered #2289

[Fixed] PopupBlocker is not updated alongside AG update #2354

[Improved] Popup Blocker extension has been updated to v2.5.8 #2351

[Improved] Custom filters URL parsing #2280

[Improved] URL exclusion blocking rules are now created with important modifier by default #2305

Networking

[Changed] AdGuard now asks for a reboot after TDI driver update on Windows 7 #2364

[Fixed] Firefox 64-bit handshake issues with some domains #2347

[Fixed] QUIC v44 is not blocked properly #2335

[Improved] AdGuard now checks on installation if the TDI driver is not registered yet #2321

UI

[Changed] Clickable area for “Close” button for AdGuard notification has been increased on Windows 7 #2319

[Changed] Highlighting color for the whitelisted requests in Filtering Log #2358

[Fixed] AdGuard remembers the last displayed settings tab after closing #2317

[Fixed] The Assistant icon appears in full screen mode on YouTube and Twitch #2309

[Fixed] Move the assistant icon back to the right corner #2314

[Fixed] “Hide your referer” checkbox state is not transmitted properly to web reporting tool #2286

[Fixed] Duplicate “Trial is expiring” message #2287

[Fixed] AdGuard fails to start service #2339

[Fixed] Crash on multiple tray clicks right after the installation #2340

[Fixed] “Service failure” tile and “Trial expired” tile appear simultaneously #2342

[Fixed] Crash upon opening the Filtering Log #2346

[Fixed] Update AG icon to high resolution version #2341

[Improved] Suppress the Alt-Svc header #2343

Other

[Fixed] AdGuardSvc process memory leak #2114

[Fixed] Crash while closing from tray #2252

[Fixed] Crash after auto-update on the application startup on Windows 7 #2290

[Fixed] An error while parsing the userscript metadata #2311

[Improved] A privacy-friendly protocol is now used for the parental control web service #2316

[Improved] Localizations have been updated, new languages have been added (Slovenian, Czech, Belarusian) #2361

While we are still polishing CoreLibs and are not ready to implement it just yet, we can sweeten the waiting with this new release. New "Nightly" update channel, added TLS1.3 support, improved performance and many more other changes.

[Added] Nightly update channel

The concept of a “Nightly” build is very simple. It literally means “a build that is released at the end of every day”, hence “nightly”. In reality, it may not happen every single day, but rather every 3 or 4 days, but the idea is there. All the latest changes made by developers will be included in the nightly build (yes, including possible bugs — be prepared!). If you feel that beta is not enough for you, and you need to be a step ahead of the rest, this is the choice for you. Just go to AdGuard settings and switch to Nightly update channel.

[Added] TLS1.3 Support (draft 28) #2155

TLS 1.3 is a new version of the cryptographic protocol used to encrypt messages sent via HTTP. It is faster, more secure and overall better than its predecessors. It has not been accepted by IETF as a standard yet, but it is only a matter of time. The process has already started, and we want to be at the forefront, and thus we have already added the TLS 1.3 (draft 28) support. As not everyone supports TLS1.3 yet, there can be problems on some websites potentially, so we added a new advanced setting to switch between TLS versions at will.

[Added] Option to subscribe to a filter by clicking a special link on a webpage #1945

Many filter developers put a special subscription link on their filters' homepage. Now AdGuard is able to detect these links when you click on them and will ask you if you'd like to subscribe to that filter right away. A minor thing, but it will save you just enough of extra clicks to be worthy.

[Added] A notice to inform about closed connections to websites with EV certificate #2015

Some websites have so-called EV (extended validation) certificates — basically, this means that the owner went through a very long and thorough process of validating their identity. In other words, these websites are generally the safest on the web. Filtering these websites is often extensive, as they rarely have ads anyway, but can sometimes lead to conflicts. AdGuard provides an option to disable filtering for such websites, and if it is enabled, a notification will inform you when you visit them for the first time. Clicking on the notification will allow to force filtering on the website anyway.

[Added] Stealth mode options applied to requests added to Filtering log #247

This is something a lot of aspiring filtering rules creators asked for. Knowing which Stealth Mode options affected this or that request is often crucial when working on a new rule. Now you can find it right in the Filtering log when you select a request. For sure, this sounds a little bit nerdy for an average user, but we try to take into account needs of all our users, casual and advanced alike.

[Changed] Default builder has been drastically reworked #1965

Basically, this is the change that caused the build size reduction that was advertised in the introduction. As the app accretes new features over the years and the code mounts up, this becomes more and more relevant. Thanks to this change, now we can add even more!

[Improved] Better support for visually impaired users #2068

AdGuard tries to provide the best online experience for all users alike, and visually impaired users are no exception. Starting with this version, AdGuard menus are much better suited to be read by NVDA Screen Reader and other screen reading programs.

[Improved] Filters update procedure's performance #2211

If you had the misfortune of a habit to update your filters often, you certainly noticed that it took quite a lot of time, as well as installing new filters. We addressed this problem, the situation should change drastically for the better now.

Ad Blocking

[Added] Option to subscribe to a filter by clicking a special link on a webpage #1945

[Fixed] "Block Flash" setting doesn't block Adobe Flash #2058

[Fixed] AdGuard cannot start protection after installing an update #2033

[Fixed] Cannot parse CSP from a meta tag #2207

[Fixed] HTML parser fails on cbc.ca #2221

[Fixed] Incorrect exception rule is created with Assistant #2265

[Fixed] Applications manually added to “filtered apps” get removed after an update #2195

[Improved] ExtendedCss has been updated to version 1.10 #2152

Networking

[Added] New approach to switching the update channel for default userscripts #2177

[Changed] Common API response format to use for XHR and WS APIs #2228

[Changed] HTTP headers with an empty value are not ignored from now on #2264

[Changed] Existing connections of filtered apps are closed now on AG startup #1977

[Changed] Problem with Github discontinuing TLS 1.0/1.1 support has been addressed #2098

[Changed] Symantec certificates have been deprecated #1634

[Changed] TDI, WFP drivers and libs have been updated #2089

[Fixed] CSP issue at github.com #2151

[Fixed] Invalid HTTP response header prevents a website from opening #2188

[Fixed] ipleak.net and other online tests show as if AdGuard does not block WebRTC #1995

[Fixed] The issue with FIPS security error on license check #1033

[Improved] Method for detecting untrusted certificates has been improved in accordance with Chrome policy #2171

UI

[Added] A notice to inform the user about closed connections to websites with EV certificate #2015

[Added] A "Beautifier" to the Filtering log and userscripts editor #1671

[Added] Stealth mode options applied to requests added to Filtering log #247

[Added] Swedish localization #2173

[Changed] Filtering log — long rules now collapse while in detailed mode #1845

[Changed] Several localizations updated #2088

[Changed] More details added to "AdGuard service" description #422

[Changed] Old links have been replaced with new ones #2102

[Changed] Parental control password is now hidden while typing #1816

[Changed] The first screen of the installer #2240

[Fixed] "Referer" field is now disabled unless "Hide Referer" is enabled #2025

[Fixed] AdGuard breaks encoding of a custom filter #2232

[Fixed] Can’t export/import configuration in Spanish localization #2018

[Fixed] Filter editor bug when pressing backspace #1439

[Fixed] Filter status change is not applied #2180

[Fixed] GUI hangs when enabling/disabling filter lists #2036

[Fixed] Incorrect "time updated" value is shown after filter remove/install #2220

[Fixed] Incorrect version of custom filter is displayed after an update #2206

[Fixed] Logo issue #2095

[Fixed] Parental control module doesn't save sensitivity level choice #2257

[Fixed] Toast notifications are broken in Windows Insider Preview #2278

[Fixed] Sometimes app crashes after adding an HTTPS exclusion #2024

[Fixed] The disclaimer in "About" window is hidden while updating #2165

[Fixed] The ~ symbol looks like - in Parental control settings #2219

[Fixed] Windows notification center is unavailable after first install #2268

[Improved] Handling of plural forms in localizations #2046

Other

[Changed] Digital signature and description #2045

[Changed] Restrictions on the length of non-script and non-style elements have been removed #2237

[Changed] Suppress browser cache on a GM storage state change #2258

[Fixed] "Traditional Chinese" language file title #2190

[Fixed] block\_third\_party\_auth parameter does not work #2073

[Fixed] App has crashed while being closed from tray #2019

[Fixed] Application update clears userscripts' storage even for the same update channel #2194

[Fixed] Cannot export settings in nightly builds #2204

[Fixed] Crash while closing from the tray #2252

[Fixed] MS Edge is not filtered in the Windows Insider Preview #2270

[Fixed] Tab and arrow keys can be used while in the password protected menu #2012

[Fixed] Userscript's require and resources parameters are not exported along with with its contents #2212

[Fixed] Windows notification center is unavailable #2181

[Fixed] Wrong folder is opened after the export operation is finished #2123

[Fixed] User script name being corrupted while export settings #2275

[Improved] AdGuard.tools can now be run as a "true" win64 process on 64-bit OS #1809

[Improved] Do not allow auto-switch update channel within the process of the upgrade #2269

[Improved] Traditional Chinese translations for filters have been updated #2245

Over the last weeks, we've received several reports about bugs that slithered in the latest release. They turned out to be both moderately important and relatively easy to fix, so we decided to release a new update off-schedule.

[Fixed] "Reinstall certificate" feature does not work in Firefox #2013

While not being the most important feature, the automatic certificate reinstall is more relevant for Firefox-based browsers than for any other ones. This fix eliminates the need to do it manually.

Networking

[Fixed] Connect to 66.ru failed: ERR_CONNECTION_CLOSED #1991

[Fixed] Can't send pictures in desktop Viber app #1990

Other

[Fixed] Fix the translation for the 'Get Premium' tile #1999

[Fixed] Baofeng video software compatibility issue #1993

[Fixed] Several userscripts compatibility issues #1986

Hello! The changelog this time is truly gigantic. Every time we thought we were going to release the current version, there was always something we felt was essential to fix, add or improve. How did it turn out?

Let's start with UI changes. Both Filtering log and Filter editor have been seriously redesigned. We need to say a big 'thank you' to everyone who has expressed his or her opinion because few changes depend as heavily on users' feedback as these.

[Changed] Filtering log rework #96

We know for certain that quite a few of our users are actively using Filtering log — both for creating new custom rules and generally knowing what's going on. So why not help them a bit? It has undergone a major renovation. New Filtering log overlaps with Filter editor a great bit, for example, you can create new rules and unblock blocked requests right therefrom.

There are more details to see about each request, too. The request details dialog window is very reminiscent of the Developer tools in Chrome browser. All in all, the new Filtering log is much more than a simple list of which requests are blocked and which are not.

[Changed] Filter editor rework #1293

Filter editor has also changed for the best. The addition of an 'Edit mode' allows replacing the data grid with a text area. This lets you copy/paste/delete many rules at once without having to bother with export/import.

Basic hotkeys are now available, which will speed up the process of working with the filter editor. There are many other quality of life changes, especially to the UI, which will draw your attention as soon as you launch the new version.

[Added] Integration with Windows 10 notifications center #1554

Many Windows 10 users find the Notification center to be helpful when it comes to tracking the activity of their apps. We have finally decided to take advantage of it and integrated AdGuard with the center. AdGuard has a surprisingly decent amount of various notifications. Just to name a few: notifications related to the license/trial period, automatic filter activations, new rules in User filter, Safebrowsing triggers, update checks results, etc. If you use Windows 10, you'll be able to find them all in one place now, thus making it much easier to keep up with what's going on with AdGuard.

[Changed] Network settings moved to a separate settings tab #1404

This one is rather straightforward. Previously, all network settings were crowding inside the 'General settings' tab making it harder to scroll up in down, searching for the one setting you need. Adding a separate first-level tab makes it easier to navigate through the app.

Assistant and other extensions

While not being an integral part of AdGuard for Windows, some extensions (or *userscripts*) have grown over time to become strongly associated with it. And we showed them some love!

AdGuard Assistant

A lot has been done in terms of improving AdGuard Assistant, and a lot more is planned for the future, so we decided to allocate it a separate, own GitHub repository: https://github.com/AdGuardTeam/AdGuardAssistant/

By the way, you may notice that the 'Report website' button now leads to a whole new page. Basically, what you see is a web reporting tool that allows you to easily send us a report on anything from a missed ad to a false positive. More about this later.

What else is done already? The biggest change is the ability to drag the Assistant icon across the page and place it wherever you see fit. Moreover, AdGuard will memorize the position of the Assistant icon for each website separately, so you can really customize it according to your taste and preferences.

The Assistant interface overall has become smaller but retained full functionality compared to earlier versions. There is even one new feature: a switch for toggling the filtering on the website on and off. Previously, the Assistant wasn't shown on websites with disabled filtering, and you had to go to User filter to enable it back.

Oh, and we could use your help with translating the new Assistant. Did you know that anyone can volunteer as a translator? If you feel confident, head right here and find your native language. Don't forget to read through the translator's memo.

AdGuard PopupBlocker

[Added] AdGuard PopupBlocker extension v2.1 #1883

For quite a while now, AdGuard works as a userscript manager — you can install any script via AdGuard to use it in any browser. PopupBlocker has always been one of the 'native' userscripts that are installed by default, alongside AdGuard Assistant. Its purpose is clear — to block any unwanted pop-ups.

Previous version (v1.0) was functional but very little beyond that. We have completely redesigned the PopupBlocker. It now has advanced pop-up detection, compared to its predecessor and its alternatives, restores the initial click behavior and is invisible to other scripts. All in all, new PopupBlocker is a solid addition to your online protection suite.

By the way, it is available as a standalone script that can be used on its own with any other userscript manager. To find more information about PopupBlocker, visit its GitHub repository.

Reports web app

[Added] Integration with Reports Web App #1964

When it comes to keeping our filter lists updated, we owe our users a big one. Thanks to their timely reports of missed ads, false positives etc., AdGuard filters are always up-to-date. We want to make the process of reporting a website easy for users and informative for filter developers, that’s why we decided to integrate AdGuard for Windows with a special web reporting tool.

When you see any problem like missed ad or annoyance, click on the Assistant icon and choose “Report this website”. You will be taken to a new page and asked to fill in some information about your AdGuard settings and the nature of the problem. Good thing is that AdGuard pre-fills most of the fields automatically, so most of the job is already done for you :)

We hope this change will strengthen the feedback from our users and allow AdGuard filters to stay at the cutting edge of ad blocking technology.

Userscripts handling

[Changed] The way AdGuard handles userscripts #1714

A lot of effort has been put into improving (better to say, rethinking) the way AdGuard works with userscripts. This actually has two different aspects:

First, from now on, the communication between AdGuard and Assistant is based on WebSocket, which results in better performance. This is also perfectly applicable to AdGuard Browser extension, when it is working in the integration mode with AdGuard for Windows.

Second, we have taken a whole complex of measures that allow for any external userscripts that you install via AdGuard to show higher speed and execution stability.

Other important changes

[Added] Settings export/import #1405

A lot of users were asking for this, and finally we deliver. Now you can save your settings configuration into a file and then use it to set up AdGuard on another machine exactly how you prefer. Another implication of this is to quickly switch between different settings profiles without having to feverishly click through a dozen of tabs and checkboxes.

[Improved] A complete "Exit AdGuard" functionality was added #1509

Now users have a choice between closing AdGuard as they usually do, and closing it completely. That means closing the Windows service as well as UI, and when UI is getting started again, the service will start as well (you may be asked for the admin privileges, though).

[Added] An option to create custom filters not backed with a file #1669

In addition to the usual option of adding any list by URL or loading it from a local file, you can now create independent new filters from scratch. It is possible to create several such filters, give each of them their own name and fill with any rules. As a result, you can create a set of specified filters which can be separately enabled, disabled and edited.

Full changelog:

Ad Blocking

[Added] "Block third-party authorization header" Stealth Mode option #698

[Added] "Pure URL" functionality has been added to the Stealth Mode #356

[Added] $app modifier support #1396

[Added] $extension modifier #1542

[Added] An option to hide Java and Flash support #1064

[Changed] $webrtc rules are being ignored now #1776

[Changed] Synchronous XMLHttpRequest got rid of #1503

[Changed] The $important modifier is now applied to rules created by enabling/disabling filtering via Assistant #1924

[Changed] The behavior of the ~third-party modifier #1564

[Changed] The range of $$ rules was increased #1464

[Changed] The script is not getting removed anymore if there is an $empty modifier in a rule #1789

[Changed] X-Requested-With is being used now to detect object-subrequest content type #1435

[Fixed] $replace rules are applied to HTTPS sites even when HTTPS filtering is disabled #1752

[Fixed] AdGuard can not recognize :empty+div selector #1687

[Fixed] Automatic update for disabled filters #1445

[Fixed] Chromium is not filtered by default #1956

[Fixed] Content filtering exception rules behavior #1560

[Fixed] content-length duplicate header issue #1982

[Fixed] Cosmetic filters are not applied to the pages whitelisted by a $document exception anymore #1574

[Fixed] Duplicate filtering rules #1686

[Fixed] Error while parsing filtering rules of a particular type #1558

[Fixed] No filtering with TCP Fast Open enabled in Firefox Nightly #1867

[Fixed] Notification API isn't blocked properly #1706

[Improved] "ExtendedCss" module has been upgraded to v1.0.8 #1823

[Improved] GM_openInTab to handle data URLs in chrome #1971

[Improved] Multiple filters can be automatically enabled as language-specific at once now #1758

[Improved] The way $network modifier works #1645

Networking

[Added] Brotli support #1545

[Changed] HasConflictWithWpf flag values have been updated #1976

[Changed] SHA1 deprecation process is finished #1325

[Changed] WoSign and StartCom Certificates have been completely deprecated #1359

[Changed] XMLHttpRequest in the API is now protected #1434

[Fixed] A page is broken in IE #1591

[Fixed] AdGuard 6.2.390 on Windows 10 stops browsing until user kill the process #1901

[Fixed] AdGuard breaks local HTTPS connections #1896

[Fixed] AdGuard cannot filter Edge HTTPS traffic when TCP Fast Open is turned ON #1093

[Fixed] AdGuard cannot handle huge chunks properly #1772

[Fixed] Disabling HTTPS filtering breaks local.adguard.com #1792

[Fixed] DNS is unreachable when using AdGuard #1918

[Fixed] Dropbox CSP messes with AdGuard scripts #1678

[Fixed] HTTPS filtering on dropbox.com does not work sometimes #1902

[Fixed] Impossible to set custom IP in Stealth Mode #1828

[Fixed] Incorrect encoding was being used for the preview purposes #1741

[Fixed] Invalid gzip causes connection to hang #1817

[Fixed] Requests blocked when HTTPS filtering is disabled aren't present in the filtering log #1639

[Fixed] Several userscripts do not work when installed via AdGuard #1562

[Fixed] SHA-1 intermediate issue #1702

[Fixed] Stealth mode settings may break filtering completely #1693

[Fixed] Warnings about synchronous requests #1688

[Fixed] Wrong ciphers order #1884

[Improved] AdGuard doesn't recognize userscript updates when the version string is too long #1541

[Improved] Custom filter updates are being validated now #1765

[Improved] The strong key exchange within secure connections has been enforced #1728

[Improved] WebRTC detection #1831

UI

[Added] "AdGuard service" description #422

[Added] "Start time" and "Time" fields in the log records #1677

[Added] "Storage" and "Reinstall" buttons on “Extensions” screen #1893

[Added] A "Preview" feature for the blocked requests in Filtering Log #1695

[Added] A "Reset to defaults" button to the Extensions settings #1473

[Added] A loader is shown while Filter Editor is being prepared to be opened #1638

[Added] A switch to change the filter list display mode #574

[Added] A tooltip has been added to the "Support" window #1432

[Added] A warning in the "Filtered apps" section when AdGuard is in the proxy mode #942

[Added] An option to disable all AdGuard popup notifications #1630

[Added] An option to disable pop-up text in the Filter editor #1082

[Added] Filtering log export feature #1662

[Added] Filtering log records context menu #1668

[Added] Search function was added to the preview textarea #1694

[Changed] "Applied rules" appearance #1676

[Changed] All elements in Filter Editor UI are now shown as disabled until rules are fully loaded #1638

[Changed] Dutch localization was updated #1663

[Changed] Expiration date in the 'License' section has been made more distinguishable #674

[Changed] Filtering log scrolling behavior #1791

[Changed] Graying out the disabled modules has been uniformed across the app #1827

[Changed] Hebrew localization was updated #1548

[Changed] Interface has been optimized for screen readers #352

[Changed] License key symbols in the 'License' section are hidden now #627

[Changed] More details have been added to the "AdGuard service" description #422

[Changed] Prevent closing the editor after editing a userscript #1632

[Changed] Program logo and "About" screen have been updated #1812

[Changed] Resizing the details pane was made more convenient #1675

[Changed] The EULA has been updated #1824

[Changed] The Filter Editor does not allow switching to other filters now when you're in the edit mode #1656

[Changed] The link to custom rules creation manual is added to the Filter editor #1410

[Changed] The maximum number of records in the Filtering Log was limited #1723

[Changed] UDP/TCP and HTTPS tunnel connections moved to the "Other" section of the filtering log #1670

[Changed] Update channel is now set to "Beta" if you install or update AdGuard to beta version #196

[Changed] Values in the details panel are now selectable #1667

[Fixed] "Connection" type records issues #1674

[Fixed] "Support" contact form is missing #1753

[Fixed] A “new line” symbol is added after copying a rule in Filter editor #1878

[Fixed] An incorrect message is shown upon checking for the updates w/o an Internet connection #1552

[Fixed] Can't use 0 as a value for self-destructing cookies setting #1642

[Fixed] Cancel button is missing #1899

[Fixed] Cannot close "validation error" dialog when editing a userscript #1894

[Fixed] Changing Advanced settings does not lead to network filtering restart #1800

[Fixed] Closing the right pane for a blocked request in Filtering Log does not highlight the entry #1729

[Fixed] Complete exit functionality bugs #1826

[Fixed] Crash after exiting AdGuard via the tray menu #1697

[Fixed] Ctrl + Z does not work in any input field #1960

[Fixed] Default filters could have been deleted in filter editor #1786

[Fixed] Disabling HTTPS filtering leads to duplicate entries in the filtering log #1793

[Fixed] Facebook response preview is broken as preview tool does not support Brotli #1657

[Fixed] Filter editor bug #1969

[Fixed] Filtering log and Filter editor windows have different styles #1920

[Fixed] Filtering log search does not show UDP requests #1658

[Fixed] Filters content is being written to the application log #1703

[Fixed] GUI can't start after changing language #1664

[Fixed] Log export does not work #1900

[Fixed] New filtering log does not display removed elements #1660

[Fixed] Remote address bug in Filtering log #1852

[Fixed] Search does not work in userscript editor #1814

[Fixed] Search tooltip bug #1830

[Fixed] Stealth Mode tooltip bugs #1520

[Fixed] There was a sequence of actions that could lead to the removal of User filter #1787

[Fixed] UI crash when disabling the service with opened Filtering Log #1751

[Fixed] User filter is always empty when "Filter editor" is opened for the first time #1970

[Fixed] User Filters search doesn't work in 'advanced editor' mode #1821

[Fixed] User installed disabled filters are enabled after checking for updates #1692

[Improved] More filter editor tweaks and fixes #1750, #1778

[Improved] Search criteria in the filtering log were extended #1513

[Improved] Speed of searching in Filter Editor and Filtering Log was increased #1725

[Improved] Support for the PT-PT localization has been added #1640

Other

[Added] AdGuard French filter #1596

[Changed] 'Adblock Protector' added to the list of filters available by default #1584

[Changed] Bandizip app has been added to the list of apps filtered by default #1680

[Changed] Localizations have been updated

[Changed] Several browsers and apps were added to the list of apps filtered by default #1182, #1563

[Changed] Spotify app has been added to the list of apps filtered by default #1904

[Changed] Swing browser has been added to the list of apps filtered by default #1769

[Changed] The list of HTTPS exclusions has been updated

[Changed] Whale browser has been added to the list of apps filtered by default #1770

[Fixed] "Add application" tool in “Filtered Apps” can't detect installed Viber #1559

[Fixed] A generic hiding rule in third-party filter is not being applied #1696

[Fixed] AdGuard crashes when you block a request in the filtering log #1868

[Fixed] Assistant settings are reset with the 3.0 -> 4.0 update #1738

[Fixed] Problematic userscript prevents others from working #1962

[Fixed] Several third-party userscripts compatibility issues

[Fixed] Stealth mode blocks Bitrix24 calls #1685

[Fixed] Typos #1825

[Fixed] Userscript is not injected #1958

[Improved] Data is now being preprocessed before the import/export #1691

[Improved] Log columns were reordered #1779

[Improved] The log file is now being validated before importing #1722

[Improved] Version check algorithm for filters added by URL #1431

This update might not be the biggest one, in a sense it doesn't feature any revolutionary additions or the immense number of changes. But it's surely a unique one, and it's because it is by far the most influenced by the user feedback. We sincerely thank everyone who has helped us!

It is super important for two big reasons, both concern networking/compatibility: we have *finally* fixed the compatibility issue with KIS/ESET and, also, we've fixed a certificate issue in modern Chrome versions (59+). Details below.

[Fixed] Compatibility with KIS/ESET #1565

AdGuard used to have compatibility issues with such antivirus software like Kaspersky and ESET. Users had to seek for compromises: disabling SSL scanning in antivirus, disabling WFP driver or even HTTPS filtering in AdGuard. The core of the problem was the WFP network driver incompatibility, and we had had plans to develop a new driver for what now seems like an eternity.

We'd already claimed to have this fixed in the previous releases, but things turned out to be more complicated. We've come through countless iterations, test builds, and driver updates, and now we are confident enough to say that this time the problem is fixed for real. No more BSODs and other funny stuff when you run AdGuard alongside with KIS or ESET.

And again, we can't thank enough everyone who was willing to cope with raw test builds and provided invaluable feedback in order to help us make things right. Just look at the task - it is blowing up with comments. We are happy to have such users, you are awesome.

[Fixed] Compatibility with Chrome 59+

With big news which WFP driver compatibility fix is it could be easy to neglect other changes. And that would be so wrong! This fix, in particular, is of utmost importance. It ensures AdGuard will run without problems on modern (v59+) Chrome versions. Otherwise, there would be troubles with AdGuard certificate validation.

Other

[Changed] The search criteria in the filtering log were extended #1513

[Changed] Connections are not allowed if DH1024 is in use #1616

[Changed] The default HTTPS exclusions list has been updated #1618

[Fixed] AdGuard Service keeps downloading data after closing the browser #1599

[Fixed] An error encountered when adding a filter by URL #1583

UPD: hotfix update 6.1.314 brings a fix for the bug #1569, messing with filtering when HTTPS filtering is disabled.

It was quite a while since the last AdGuard for Windows release. And there are other reasons for that apart from the Christmas/New Year holidays: we'd been extensively testing the new network driver before, finally, we felt ready to include it in the new release version. But what is there for me in this network driver, you might ask? Well, it fixes an old compatibility issue with several antivirus programs. For sure, there are other fixes and changes as well, and you will find the whole list below.

You can also find all relevant information about this release (and discuss it) in our blog.

Networking

[Improved] WFP driver was updated to fix compatibility issues with KIS and ESET #1497

Previously, it was not unusual at all that AdGuard would have compatibility issues with some antiviruses, and KIS and ESET being the most common ones. The workarounds existed but were far from ideal - you had had to sacrifice some parts of functionality on either AdGuard or antivirus side. With updated WFP driver these conflicts will be no more, allowing users to run AdGuard alongside with KIS and ESET.

[Improved] The way we respond to HTTP protocol violation #1452

It would take too long to explain technical nuances, but effectively this fixes the problem some users might have come across before: when you try to open a page and it is downloaded as a file instead.

[Fixed] $popup rule bug #1504

[Fixed] QUIC protocol issue when KIS is installed #1482

[Fixed] HideUserSearch option breaks the 'maximize' button graphics #1536

[Fixed] 'Disable Fast Open' setting doesn't work in latest Insider Preview builds #1487

[Fixed] Several issues in Firefox with the default value of 'Hide you user-agent' setting #1493

Ad Blocking

[Added] $network basic rules modifier to solve the issue with loading ads through WebRTC #1297

[Changed] Extra Steam executables removed from the list of filtered apps #1468

[Fixed] Invalid executable for CentBrower #1453

[Fixed] $replace rules aren't applied to .m3u8 files content #1428

[Fixed] Regular expressions with $ aren't processed properly #1475

[Improved] Cosmetic exception rules compilation speed #1533

UI

[Added] A new advanced settings property to change the injection method #1492

[Changed] Version history link in about section #1471

[Changed] Parental Control password protection is made separate for different Windows user accounts #1480

Other

[Changed] HTTPS exceptions list is updated #1532

[Changed] Opera Neon browser added to the list of filtered apps #1495

[Changed] Orbitum browser added to the list of filtered apps #1467

This version should be considered as a revision of the AdGuard for Windows 6.1 release. This is why you will not spot many 'major' changes - mostly bugfixes, small changes, improvements etc. More drastic changes will come eventually with 6.2 version.

Ad Blocking

[Added] $important modifier #1312

This new addition is an important one (no pun intended), but mostly relevant for creators of custom filter rules. With it's help you can give certain rules higher priority.

[Changed] Several apps and browsers added to the list of apps filtered by default #1230, #1236, #1274, #1280, #1344, #1347

[Fixed] Inconsistent $replace result #1358

[Fixed] AdGuard now filters pages with Content-Type:application/xhtml #571

[Fixed] HTTPS exceptions do not cover subdomains #1317

[Fixed] $replace rule can now be applied along with the other rules #640

[Improved] Filters update check period is now customizable #941

[Improved] AdGuard now can partially block encrypted ads without decrypting SSL protocol (if HTTPs filtering is disabled) #1233

Networking

[Changed] Switched to the DigiCert certificate #1268

[Changed] WoSign and StartCom certificates became unstrusted #1359

[Changed] Proxy mode will use IPv4 address when it is available from now on #1323

[Fixed] CSP is now handled in meta tags #797

[Fixed] Issue with invalid HTML #1222

[Fixed] "iframe" elements are not removed from the page code #1245

[Fixed] AdGuard.Tools.exe heavy CPU load issue #1229

[Fixed] Opera dev ad blocker compatibility issue with AdGuard Assistant #1173

[Fixed] Opera built-in VPN compatibility issue #1116

[Fixed] Certificate validity check order #1277

[Fixed] SSL exceptions aren't deleted on network API reinit #1304

[Fixed] AdGuard code is injected into a non-HTML document #1316

[Fixed] WFP driver impacting DPC latency #1156

[Fixed] $empty modifier behaviour #1360

[Fixed] Stealth mode ignores $stealth exception #1362

[Fixed] Inability to apply inline style #1331

[Fixed] An empty 'style' tag is added even if there's no element hiding #1336

[Fixed] $replace modifier breaks content charset #1378

[Fixed] Adsbypasser and some other userscripts do not work properly #1363

[Fixed] "Enable safe search" function in Parental Control breaks Google #1383

[Fixed] AdGuard doesn't filter HTTPs when Fiddler is switched on and in "decode https" mode #1372

[Fixed] Adding a URL to temporary HTTPs exceptions is suppressed now when connection is closed from the server side #1341

[Fixed] 'access-control-allow-origin' header console error #1381

[Improved] HTTPS is now used for safebrowsing service requests #1386

[Improved] Encrypted connection is used now with api.adguard.com #1369

[Improved] AdGuard styles are now protected from removing #1272

[Improved] Content type detection #1264

[Improved] Content injection algorithm was reworked #1099, #1305

UI

[Changed] WOT extension is now disabled by default #1364

Recently, an article was posted in one of the popular technology blogs, claiming that Web of Trust is selling its users' browser history to third-parties. WoT extension is preinstalled in AdGuard for Windows, and although it was developed by us and is not sending any of your data to WoT, we can not leave this without a reponse. For this reason we make WoT extension disabled by default in AdGuard for Windows. You can read our official stance regarding these news in our blog.

[Changed] You can now completely remove WoT extension #1364

[Changed] Unnecessary text in 'Import rules' dialog window is removed #1349

[Fixed] Filter's name isn't copied with the rest of request details #1318

[Fixed] Button size issue on the last step of AdGuard wizard #1352

[Fixed] AdGuard crashes if you try to close UI while editing a filter rule #1258

[Fixed] $replace rule is shown as applied to images #1392

Install/Update

[Fixed] Deleted records from HTTPs exclusions are not restored on app update anymore #904

Many other minor fixes and changes. The full list can be found in descriptions to prior beta versions in our repository on GitHub.

Briefly about new AdGuard for Windows version: Stealth Mode got new useful options, userscripts work better now, ad blocking became more advanced and our network drivers - more stable. All the details are below.

Stealth Mode

[Added] "Self destructing cookies" option in Stealth Mode #678

Previously Stealth Mode module provided only the option to completely block third-party cookies. Now you will not only have an ability to differ first- and third-party cookies, but also the ability to set the exact time which cookies will be kept alive for. Important note: you can still block cookies alltogether, just set the keep-alive time to '0'.

[Added] Added an option to block "Browser location API" #139

[Added] Added an option to block "Browser notifications API" #1121

Normally browsers may detect your location and use this information to prioritize specific search results or make other various suggestions based on it. With browser location API blocked this will be impossible.

Blocking browser notifications API feature works somewhat similar, but rather prevents browser from showing things like news or social media frames that pop-up in the corner of your browser.

Userscripts

[Improved] Content injection algorithm #1099

We completely redesigned content injection algorithm. First and foremost, this should solve issues with scripts that start when the page opens, resolve some of the known conflicts (AdsBypasser, YouTube+), and also optimize usage of scripts and ad blocker styles. Overall, a technical, but very important change.

[Added] Userscripts handling #1172

We adopted a new way of handling user.js (userscript) files. Now AdGuard will automatically detect when user.js file was processed. If it is a valid userscript, AdGuard will open a dialog window, offering user to install it. Of course, this setting will be optional and possible to turn off through settings.

UI

[Added] Hebrew localization, Dutch localization #1076, #1063

We continue to make AdGuard more easily accessible for users all over the world. This time we add two more new localizations and fix some mistakes in already existing ones.

Networking

[Improved] Network SDK was updated #1179

In reality, this implies many various fixes that concern our network drivers. It would be hard to list them all here, and most of them are rather technical anyway. For example, the WFP driver - Windows Defender compatibility issue was addressed.

Ad Blocking

[Added] Support for extended selectors #1225

This is a technical term, but what hides behind it? With extended selectors support, we can much more easily create some rules that were very, very hard to create earlier. Notably, this concerns rules required to block such things as 'Sponsored posts' on Facebook.

[Added] Extended CSS support

This is a very important addition in terms of future (and present) possibilities that it opens for ad blocking. Extended CSS is a module for applying CSS styles with extended selection properties. Basically, it means that we will be able to select and, therefore, block some elements that we would not be able to block otherwise. Currently we support following pseudo-classes: -ext-has (:has), -ext-contains (:contains), [-ext-matches-css (:matches-css).

Other

Dozens of minor fixes and improvements.

A hotfix after last weeks release. Previously there turned out to be several problems, including router page loading problem and other. These bugs are fixed with this version.

[Fixed] Indefinite loading of router page #1042

[Fixed] Rare problem when AdGuard crashes after clicking on tray menu icon #1045

[Fixed] AdGuard will not crash any more if you switch tabs while have active search on 'Settings' screen #1043

[Fixed] AdGuard now detects HTML correctly for all websites if there is an xml declaration at the document start #1011

Good news, everyone! We haven't seen any new bugs since the latest beta version, and it means nothing else but the new stable release is arriving. During the last couple of months that had passed since the 6.0 release we were able to track quite a lot of bugs and defects, which were crucial to fix. So we concentrated on them for a while. Finally, everything seems to be fixed and we are ready to turn on the autoupdate for all our users who still use Adgguard 5.10. We were looking forward to this moment! Even if you were already using AdGuard 6 and you are not as excited by these news, you should be. This release means we can finally put all our efforts into implementing cool new features you might have or have not seen in our roadmap. In case you missed last beta releases and respective release notes, you can catch up and read about all the fixes and additions below. Most important of them, as usual, are described in detail.

UI changes

[Changed] AdGuard uses native-style tray menu now #1006

[Changed] AdGuard window is now opened with a single click on tray menu #1030

[Fixed] 'About' window content is not flickering anymore #954

[Fixed] Empty strings are now removed when importing user filter #973

[Fixed] Error previously encountered while installing a userstyle #934

[Improved] Proxy name validator now recognizes domain names and not only IP addresses #931

Ad Blocker

[Improved] Added $stealth modifier that disables Stealth Mode for the specified website #339 As we already mentioned in our blog, separate whitelist for Stealth Mode is on our roadmap. It is a much needed feature for anyone who actively uses Stealth Mode. We are not quite there yet, but we made a big step in the right direction by implementing $stealth modifier. It works similar to all other modifiers, just add it to any exception rule and it will disable Stealth Mode for that website specifically, even if the module itself is enabled. For example: @@||example.org^$stealth You can find more information about rules formatting on our website: adguard.com/filterrules.html

[Changed] Facebook windows app added to default filtered apps list #974

[Changed] $replace rules should now have higher priority than other basic rules #1023

[Fixed] AdGuard does not try to filter data: URLs any more #1007

[Fixed] $domain modifier now does work for blocking WebSocket connections #998

[Fixed] AdGuard now doesn't ignore tag href attribute while constructing absolute URL #978

[Fixed] Error previously encountered while parsing a style tag with embedded svg #977

[Fixed] Language-specific filters are now detected properly from users keyboard layouts #401

[Improved] AdGuard now can process websites names in punycode when adding them to HTTPS exclusions #962

Languages and Translations

[Added] Support for complex language codes #808 We have completely reworked applications localization system. This allowed us to significantly increase number of languages we can potentially support (this mostly concerns various dialects, alternative alphabets etc.).

[Added] Croatian language

Networking

[Improved] HTML content detection #855 Content type detection was significantly improved. This effectively means that AdGuard will not interfere with those types of traffic which do not require filtering, decreasing the number of potential conflicts.

[Fixed] Web interface of TP-Link router is broken #844 Some of our users encountered problems with accessing TP-Link routers' interface with enabled AdGuard. Upon investigating this issue we discovered a serious issue with WFP driver which resulted in problems with displaying some websites. As a result, we have improved communication with some specific web-servers.

[Added] Support for HTTP method REPORT #1020

[Fixed] AdGuard can now detect HTML if there is an xml declaration at the document start #1011

[Fixed] ESET compatibility issue when Chrome browser would randomly hang #899

[Fixed] Data is now read to end after blocking a POST request #916

[Fixed] Issue with unexpected connection reset with TDI driver #1025

Install/Update

[Fixed] Blank dialog while updating from 5.10 to 6.0 #924

[Fixed] CMD window is no more shown on AdGuard update #935

[Fixed] An issue when update errors were shown as valid updates in tray notification #993

[Fixed] AdGuard now detects Chrome in 'Filtered apps' on Windows 10 insider build #972

Minor

#914, #927, #948, #946, #945, #944, #1014, #1029

[Fixed] Issues in Windows 10 Insider Preview build caused by SHA-1 certificate used for network drivers.

Let us elaborate a little on this one, since this change stands out as the most important one in this update. Recently we have noticed, with the help of our beta testers, that SHA-1 certificate previously used to sign our network drivers, was in a process of being deprecated. Effectively this means that users of Windows 10 Insider Preview were not able to enable AdGuard protection. We have signed our network drivers with new certificates, and now all users will be able to run AdGuard without any problems.

UI Changes

[Fixed] 'Upgrade license' notification is no more shown for licenses activated with beta key

[Fixed] Bug when some apps wouldn't show among 'filtered apps' until they are started

[Fixed] Latest update check time is not being updated

[Fixed] Pressing Alt-F4 while in AdGuard tray menu will no longer result in closing the main window

Ad Blocker

[Fixed] K-Meleon browser is now correctly detected as installed

[Fixed] Unnecessary language-specific filter activation

[Fixed] WebRTC will no more be blocked for applications which are not in the Filtered Apps list

[Improved] Default HTTPs exclusions list was significantly updated

Install/Update

[Changed] Auto update mechanism

[Fixed] AdGuard beta won't update after clicking on 'Install' button in 'About' section

[Fixed] MSI shows "remove settings" dialog on uninstall.

[Fixed] WFP driver is now uninstalled correctly on Win 10 x64

Languages and translations

[Fixed] "User filter" is not translated to Polish

Networking

[Fixed] AG code is no more injected into

Minor

, , , , , , ,

A new update to the recently released AdGuard 6 is available. It mostly contains fixes to some minor bugs we missed during the beta test. You are able to update to the latest version from your client.

[Fixed] WFP driver now can be used on Windows 7 x86 https://github.com/AdGuardTeam/AdGuardForWindows/issues/850

[Changed] 'Thank you' page removed from AdGuard https://github.com/AdGuardTeam/AdGuardForWindows/issues/842

[Fixed] Validation of Parental Control whitelist/blacklist domains is now working correctly https://github.com/AdGuardTeam/AdGuardForWindows/issues/830

[Fixed] Reset settings windows title now has a name separate from its description https://github.com/AdGuardTeam/AdGuardForWindows/issues/826

[Fixed] "User filter" translations are fixed and completed https://github.com/AdGuardTeam/AdGuardForWindows/issues/824

[Fixed] Bug encountered when setting TDI driver as default on Windows 7 https://github.com/AdGuardTeam/AdGuardForWindows/issues/788

[Improved] Tools for problem monitoring during installation process https://github.com/AdGuardTeam/AdGuardForWindows/issues/832

It is finally time to release AdGuard 6! We have put a lot of time and effort into its development, and you will see this reflected in the release notes. A lot was added, even more was improved compared to AdGuard 5. New version became much more intuitive in use, functional and diverse.

AdGuard user interface was completely redesigned. It will now have modern tile design. Compared to AdGuard 5, it is much better structurized and more visually attractive.

AdGuard was translated into many new languages. That includes UI, AdGuard Assistant and filter descriptions etc.

Window positions are now memorized and restored after program restart.

Tray menu is reworked, improved accessibility of different options through tray.

New versions interface is much more friendly to people with visual impairment. For example, now Windows screen reader sees almost all the elements of the program – tips, tuning, and more.

UI performance and boot speed were significantly optimized, memory consumption was greatly reduced. You can find respective graphs in blog (see the link below).

Now with the first launch of AdGuard a tutorial will be shown, familiarizing user with AdGuard and quickly introducing its capabilities.

Updating to new version from AdGuard 5 is now possible and will not lose any settings.

New possibility to change update channel to 'Beta' and receive all beta updates, including Assistant and other extensions. Useful for those, who wants to always be the first to know about all the new features.

A new module was added - Stealth Mode. Back in previous versions we only had a filter against spyware, counters and trackers to protect your online privacy. Stealth Mode serves to protect your online privacy in various ways, including blocking of third-party cookies, hiding IP address and many, many more.

Improved support for filtered apps. AdGuard now automatically finds software installed on your computer and offers to filter its traffic, this includes modern UI applications. Of course, you still can add any browser (or any app) manually. The mechanism for adding new applications to AdGuard itself is completely redesigned too, and now it is easy for any user to cope with it.

Filter editor and Filtering log were drastically changed. You will find both fresh design and improved functionality. In the Filter editor, you can see the rules created by the AdGuard Assistant, that is, all the rules that you added manually. Filtering Log displays all the requests sent.

You can now use new search feature to search the whole program for any keyword by entering it in the text field in the top right corner. We believe this is one of the most useful innovations. Now you do not have to go through the entire section of the program in search for the information you need.

Now it is possible to subscribe to any filter by URL or by choosing path to a local file, and AdGuard will automatically watch for changes.

Extensions were allocated to a separate module which can be enabled/disabled as a whole.

Userscripts security was significantly improved.

Plentiful additions and improvements to filtering process were made, notably introducing support for new rules modifiers and improving filtering speed.

Many more improvements, all of which are impossible to include in these release notes.

You can read about new version in detail in our blog: https://adguard.com/en/blog/adguard-6-official-release.html

Added Microsoft Edge browser support

Improved userscripts API speed

Fixed a bug with saving AdGuard Assistant settings

Userscripts API usage is now restricted by @grant metatag

Fixed AdGuard Assistant work in Opera 12

Fixed certificate automatic import in Opera 12

Fixed some issues with CSS/JS injection in the pages with invalid HTML code

Fixed issues with SSL interceptor (connections reset for servers working with TLS 1.0 only)

Fixed Logjam (AdGuard now does not filter connections with weak DH primes)

Fixed a bug with update cleaning AdGuard's start menu folder

Fixed SSL-filtering in old browsers (IE6, IE7)

Important notice about Logjam. We do not protect you from it, just ignore such connections. Browser decides what to do with it further. So make sure you are using the latest version of your browser.

You can discuss the latest version in our blog: here.

Important: AdGuard extensions API is now protected from misuse

Added notification about added and removed user rules

Web of Trust extension is updated - fixed an issue when website could hide reputation warning

Added server SSL certificates revocation check (OCSP)

Fixed compatibility issue with BitDefender and AdGuard's WFP driver

Fixed safe search for Yandex

Minor UI fixes

You can discuss the latest version in our blog: here.

SSL private key is no more pinned to your computer hardware. Every clean installation you get fresh private key

We now better handle TLS 1.2 connections

All certs and private keys are now encrypted and stored in a single file

You can discuss the latest version in our blog.

Added Spartan browser support

Significantly improved filtering speed of some heavy HTML pages

Fixed possible app crash (in case of logging error)

Fixed a bug with checking existence of AG certificate in Firefox-based browsers. Now if AG does not detect our cert it disables SSL filtering for Firefox

Changed AG certificate generation algorithm (you may need to reinstall it to Firefox after update or to simply reboot the computer)

Improved SSL filter, fixed FREAK vulnerability

Fixed some minor SSL filtering bugs

Several sites added to default SSL exclusions

Fixed compatibility issue with latest Bitdefender version and AdGuard WFP driver

Filtering speed has been slightly improved

Fixed Lunascape browser support

Minor UI fixes

You can discuss the latest version in our blog: here.

Parental Control is now available for any license type including Standard and Bonus

Fixed QUIC protocol filtering (that's a critical bug, sometimes we failed to filter Youtube because of it)

Added filter rules validation. Now AdGuard ignores rules with syntax mistakes

Added Vivaldi browser support

Added support of userscripts custom menu items (GM_registerMenuCommand function). Press Shift+Alt+M to bring up list of registered menu items (if any). Examples of userscripts with their custom menu items: Youtube Center, AdsBypasser, Anti-Adblock Killer

Added TLS v1.2 support

Improved userscripts API

Fixed work of several userscripts: AdsBypasser, Mouseover Popup Image Viewer, Context Menu Example (Firefox only), File Hosting Download Manager Disabler

Fixed compatibility issue with Home Media Server, Geforce Experience, Asus Control Center

Fixed incompatibility with ZenMate

Fixed a bug with short-living keep-alive connections in proxy mode

Fixed dependence on injections.adguard.com domain availability

Fixed AdGuard's network driver vulnerability

You can discuss this version in our blog.

Fixed a bug with random SSL exclusions

Fixed a bug with some URL filtering rules

Fixed a bug with AdGuard browser extension integration (in case if filtering is temporary disabled by AdGuard Assistant)

Added 2 domains to default SSL exclusions: eff.org and 8pecxstudios.com

Fixed a bug with SSL filtering in case if website use DES-CBC3-SHA cipher

Minor bugfixes

Added:

New version of AdGuard network drivers

Added Maxthon Nitro support

Added support for Regexp-rules

Added new API GreaseMonkey functions for better userscripts support

Fixed:

Fixed an issue with a long delay when adding rules by Assistant

Now, even when the Parental Control sensitivity level is disabled, black and white lists continue to work

Fixed program crashes when working with tray

When using TDI driver Teredo is no longer disabled

Fixed bug reports in IE8

Fixed several localization bugs

Parental control now blocks access to unsafe sites even when the sensitivity level is disabled

Improved ad filtering

New AdGuard webpages style (pages you see when request is blocked by Browsing Security or Parental Control)

Fixed tray menu position on PC with two displays

Fixed extensions work on websites using custom ports

Short list of important changes: greatly reduced memory usage, we introduced convenient addition of new ad filters, integration with WoT is now a separate extension, added support for new browsers, fixed conflicts with popular programs and defects in the processing of requests and more.

Memory usage reduction

We have significantly optimized memory usage in 5.10. Now, even if you use an old computer or a weak netbook, AdGuard will work silently in a background without slowing down your device. We compared memory footprint with the one of the preceding version. And we must say 5.10 showed a result several times lower.

More ad filters

In addition, AdGuard has became an even more comprehensive program. Now users can install any ad filters. What does it mean? In addition to the filters that are already installed in AdGuard by default, you can add third-party ones, such as a list of filters that allow AdGuard to block ads in different segments of the Internet - websites in different languages, in particular. All of this can be done directly in the program, simply by selecting a filter you want and clicking on the "Add selected" button.

Displaying the possible danger

Integration with Web of Trust is now brought out in the separate extension, which can be disabled. Also a warning when visiting a suspicious website has changed. With the help of WoT, our AdGuard is able to notify you instantly about the reputation of websites and show the reasons for which the site is considered to be suspicious. "Categories of suspicion" can be, in particular: scam, potentially illegal, misleading claims or unethical, poor customer experience, privacy risks and others.

Other changes in version 5.10:

Added support for CSS injection rules. It gives us more flexible options for high-quality elements blocking.

Ability to edit the source code of userscripts. Now you can customize any script you like, you can find more about what it is and how to install it here.

Updates are checked only for the enabled userscripts.Thus we update only those scripts that you actually use. Why spend the extra traffic?

Extensions that do not use external resources are returned to the "default." Now you have the opportunity to reset the extensions and return websites to their original state.

Added a configuration of exceptions for secure (HTTPS) sites filtering. Adding https websites to exceptions in order for AdGuard to not filter it, used to be impossible.

Increased time of filter updates up to 12 hours. Yeah, longer but of better quality.

Speeded up the work of extensions (including Youtube Center). Userscripts do not slow down websites now.

Fixed in new version:

Fixed conflicts with Visual Studio, Tor Browser, Keepass.

Fixed slow loading of large js files.

Assistant no longer interferes in work of RequireJs websites.

Updated network drivers, fixed some small remarks.

Fixed a defect with the processing of HTTP DELETE requests.

Fixed work of Twitch Chat Filter userscript.

Fixed a bug when using proxy authorization.

Fixed compatibility error of vk.com and Parental Control.

Fixed a defect with disabling AdGuard assistant via the context menu.

Fixed some minor defects of AdGuard assistant.

Speeded up filtering of some pages (fixed problem with octane-benchmark.googlecode.com).

Fixed API for usercripts (thanks to YoutubeCenter developer, Jeppe Rune Mortensen).

Fixed rules with the "~third-party" modifier.

New versions of TDI and WFP drivers. Fixed some compatibility issues.

Minor changes to the texts in the user interface.

Version 5.9 brings a large number of changes to AdGuard.

New features

AdGuard Extensions

In version 5.9, there is an opportunity to install extensions (userscripts). They are designed to extend the functionality of websites. How exactly will the functionality be extended depends on the particular userscript. This can be a pop-up blocking, blocking of flash requests, possibility to download music and video from social networks and much more.

You can learn more from this post in our blog.

Improved video ads blocking

In this version, AdGuard learned to recognize most of the video ads on its own without relying on filter databases.

Parental Control

During the existence of the program, we have received many requests from our users about implementing the "Parental Control" in it. Many parents found AdGuard helpful, because when using it the child didn’t see inappropriate advertising.

Finally, in the version 5.9 we are ready to introduce “Parental Control” - a separate module of the program.
You can learn more from this article.

Fixed and improved in this version

Fixed a problem with high load on the CPU and memory consumption when downloading large files

Fixed a problem with the occasional lack of HTTPS-connections filtering in Firefox and Opera

Fixed a problem with high load on the CPU and disk on system startup

Optimized and speeded up the work of AdGuard Assistant

Added support for rocket-script filtering

Fixed AdGuard compatibility issue with Kaspersky Internet Security 2014 for Windows 8.1 x64

Adguard 5.8 provides the following new features:

Improved initial setup wizard

Added "useful ads" filter

Tor browser support

What has been improved or fixed in version 5.8:

Protection level setting is removed

Fixed some minor compatibility issues

Improved filtered pages source code readability

Adguard 5.7 provides the following new features:

A more perfect way for filtration with a new network driver

Adguard now uses a network driver instead of an old filtering module. This helped us greatly with fixing all existing compatibility issues with other software products. In addition, it accelerates filtration and allows Adguard to filter secure connections.

The following compatibility issues have been fixed in Adguard 5.7: Internet Download Manager (video downloading issues) DrWeb (proper filtration was dependent on the installation order) Panda Antivirus (filtration was not possible)

Added support for secure connections filtration (https connections) Now Adguard can filter secured connections if you enable it in the network settings.

Added first run wizard

What has been improved or fixed in version 5.7:

Fixed "Connection error" that occurred if the Adguard windows service started too slow

Fixed Google Chrome filtration issues

Fixed some Adguard Assistant issues

GUI performance and responsiveness to user actions have been improved

Fixed icon for Pale Moon in the browsers settings

Added:

Completely new Adguard Assistant module

Automatic program updates

Adguard is divided into windows-service and GUI-client

Web Of Trust integration – know which websites to trust

Improved browsing security module

New filtration module for Windows 8 Modern UI applications Fixed:

Some websites rendering problems

Slow browsing security module updates

Attention, Adguard 4 is going out of support.

Added:

QT Web browser support

Sleipnir browser support

Extended logging

Filtration is enabled on big range of ports (not only 80)

In proxy mode Adguard automatically set system settings

Fixed:

Problem with no filtration of some ports

Conflict with ESET ssl filtration

Errors with HTTPS websites in Opera browser

Problem with Opera's periodical slowdown

Opera Link problem

Some problems with flash games

Maxthon favourites synchronization problem

Errors that occurred while loading some pages

Some minor fixes

Added:

Completely resolved the filtration speed issues

Simple SSL-traffic filtering

New network filtering algorythm

Extended filter rules

Waterfox browser support

Fixed:

Fixed the problem with the synchronization of bookmarks in Maxthon with an active protection

Fixed displaying issues with some of the web-sites: wix.com, pandawill.com, rakill.daportfolio.com & etc

Small bugfixes and optimizations

Added:

Automatic detection of the suitable filters

Japanese language and filter

German language and filter

Spanish language and filter

Portuguese language and filter

Dutch filter

Fixed:

Problem with very slow first request (just after Adguard has been started)

Increased filtration speed

Minor bug fixes

Added:

A completely reworked user interface with multilingual support

Added an experimental filter based on Collective Intelligence, a system that continuously collects and analyzes submissions from the community of Adguard users around the world

Now supports even more browsers: Palemoon, Nichrome, Yandex.Internet

Added ability to save user settings on uninstall

Added German filter

Added Windows 8 support

Ad Blocker and Browsing Security modules now keep their states between restarts

Users are now able to report false positive alarms in support section

The official site has moved to http://adguard.com/

Fixed:

Improved the filtration speed

Fixed critical flaws of the previous version

Fixed compatibility problems with third parties software

Fixed behavior of the “Skip” button in the messages about the new versions

Fixed encoding errors on some websites

Fixed positioning problems for the cases when system’s font is increased

Minor bug fixes

Fixed some bugs

Optimized:

Web pages loading speed

Filters updating speed

New features of Adguard assistant:

Can block almost any element selected on the webpage (in all modern browsers)

Fixed some minor bugs

Add new function: "Undo last added rule"

Fixes for bugs of version 4.2

Optimized:

Handling redirects and cached responses

Storing phishing and malware data, db is much smaller now

Fixed:

Problem with determining web page encoding when HTML is invalid

Problem with parsing some scripts

Minor UI fixes

Large update. New functional added.

New functional:

Phishing and malware protection. Includes multiple filters:

Adguard phishing and malware filters

Google Safe Browsing phishing and malware filters

Added:

64-bit browsers support

Improved traffic filtering

Improved edit subscriptions dialog

Fixed:

Problem with CSS-rules in Internet Explorer 9

Some problems with adguard assistant in Opera and Internet Explorer

Problem with adding empty rule to "My Filter"

Some minor UI fixes

Added:

Multi-user environment support

Checkbox for enabling/disabling My Filter rules

"Ignore this version" button in update dialog

Possibility to send system diagnostics report to our support service Fixed:

Problems with several flash games and applications

Improved support section of the program

Problems with encoding of depositfiles.com in Firefox

Minor fixes in html parser

Added:

Filters subscription mechanism

Added "Advanced settings" section

"Reset key" button Fixed:

Speeded up application startup

Some "Adguard assistant" bugs

Some popup blocker bugs

Fixed problem with using local proxy servers

Added:

Mozilla Firefox 4 Beta support

New filter rule wizard

MyIE browser support

Possibility to reset statistics (from the context menu)

Possibility to reset license key

Optimized "Support" section of Adguard window Fixed:

Minor UI fixes

Minor parser fixes

Added:

Orca browser support Исправлено:

Working through SSL in case of using external proxy server

Some minor fixes

Added:

Export and import of the user filter Fixed:

Problem with Opera with enabled Expect100Continue configuration setting

Uploading of big files

Optimized "Log" section work

Fixed:

Some minor fixes

Fixed:

Problems with POST http requests

Added:

"Adguard assistant" allowing user to add complex filter rules

Optimized filtration speed

Added support of five browsers: Flock, SRWare Iron, Lunascape, K-Meleon, GreenBrowser

Optimized HTML filtration rules

New options for exception rules

Added "Connection: keep-alive" http header support

Added bandwith saved counter

Added tooltips for Adguard window elements Fixed:

Problems in Adguard work in case of serveral users

Problems with chats (continious iframe)

Optimized filter rules for blocking social networks widgets and spyware

Problems with NTLM authorization

Added:

Blocking social networks widgets and spyware

New options for filtering HTML content Fixed:

Problem with Windows Media Player browser plugin

Problem with loading images in Internet Explorer

Added:

"Filters" section. Enabling/disabling of the standard filter.

Possibility to create your own filter rules

"Log" section

Optimized filtration speed

Blocking banners of standard sizes

Program files are signed with code certificate Fixed:

Problem with using online radio

Problem with applications on the facebook.com

Problem with Adguard application in case of sereral Windows users

Problem with opening several sites in Opera browser

Added:

Adguard filtration speed up

Now it can filter javascript files loading to the page Fixed:

Problem with uploading big files

Problem with filtering javascripts using regular expressions

Problem with bing.com

Fixed:

Error with deposifiles.com in Mozilla Firefox Added:

Adguard is now automatically activated after purchasing the license key (you just need to restart it)

Fixed:

problem with Internet Explorer

problem with UAC in Vista/7

problem with working through proxy server

error rendering sitez compressed with x-gzip in Opera Added:

program rendering speed up

feedback form on the "Protection" section of Adguard

The program is completely redesigned from scratch. New attractive design. Better filters database. Added two new blocking methods:

Element hiding

Filtering HTML content on the fly Computer does not need to be restarted after Adguard installation.

AdGuard for Windows – Release – AdGuard 版本

分享設定

升級瀏覽外觀設計

新登入方式

最後

更新記錄

改進

修復

CoreLibs（過濾引擎）

改進

修復

將 Scriptlets（過濾規則的 JavaScript 改進）更新為 v1.11.27

改進

修復

將 DnsLibs（DNS 過濾引擎）更新為 v2.5.41

將 ContentScript 更新為 v2.0.6

將 UserscriptsWrapper 更新為 v1.2.24

更新記錄

修復

改進

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.15.47 #5139

修復

改進

將 ContentScript 更新為 v2.0.6

DnsLibs（過濾引擎）

將 DnsLibs 更新為 v2.5.33 #5128

修復

Scriptlets（过滤规则的 JavaScript 改进）

將 Scriptlets 更新為 v1.10.25

修復

改進

更新記錄

修復

CoreLibs（過濾引擎）

DnsLibs（DNS 過濾引擎）

改進的 Encrypted ClientHello

On-the-fly DoH 連線過濾

更新記錄

改進

修復

CoreLibs（過濾引擎）

改進

修復

Scriptlets（過濾規則的 JavaScript 改進）

改進

DnsLibs（DNS 過濾引擎）

改進

這意味著什麼

但 AdGuard 仍能在 32 位電腦上正常運行，對嗎

這個版本有什麼新的過濾功能嗎？

還有什麼改進

還有嗎

更新記錄

改進

修復

CoreLibs（過濾引擎）

改進

修復

DnsLibs（DNS 過濾引擎）

改進

修復

過濾器改進

修復

Scriptlets（過濾規則的 JavaScript 改進）

改進

修復

UserscriptsWrapper

更新記錄

修復

CoreLibs（過濾引擎）

新 HTTP/3 過濾

把錯誤留在過去

更新記錄

功能

修復

過濾器的改進

功能

修復

DnsLibs