Skip to content

Commit b36cb0e

Browse files
el-termikaelgithub-actions[bot]
el-termikael
authored and
github-actions[bot]
committed
automatically update translations
1 parent c5adeed commit b36cb0e

File tree

31 files changed

+3879
-9
lines changed

31 files changed

+3879
-9
lines changed

‎i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md‎

Lines changed: 129 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,129 @@
1+
---
2+
title: Filtering issues in Chrome 142+ when using the TDI driver
3+
sidebar_position: 14
4+
---
5+
6+
:::info
7+
8+
This article covers AdGuard for Windows, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock).
9+
10+
:::
11+
12+
Some AdGuard for Windows users may notice that [the app stops filtering traffic in Chromium-based browsers](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). Starting from Google Chrome 142+, browser traffic simply does not appear at the TDI driver level, preventing AdGuard from inspecting or filtering it.
13+
14+
This behavior is not a bug in AdGuard, but a result of recent architectural and security changes in modern browsers.
15+
16+
## Why this happens
17+
18+
Chromium-based browsers (Chrome, Edge, Brave, Vivaldi, etc.) have been strengthening their security architecture. One significant change is moving sensitive internal processes into the [Windows AppContainer sandbox](https://learn.microsoft.com/en-us/windows/win32/secauthz/appcontainer-isolation), including the Network Service, which handles all browser traffic.
19+
20+
### What changed in Chrome 142
21+
22+
Starting from Chrome 142, the Network Service process is now launched inside AppContainer by default.
23+
24+
When this happens, applications running in an AppContainer do not use the legacy TDI networking interface; instead, their traffic is routed through the more modern WSK (Winsock Kernel) stack. As a result, the TDI driver cannot see, intercept, or process connections that go through WSK, and all browser traffic becomes invisible to the TDI driver used by AdGuard.
25+
26+
This behavior is controlled entirely by Chrome’s sandboxing policies and internal experiments (field trials), not by user settings.
27+
28+
## Why this affects AdGuard
29+
30+
The TDI driver is an outdated Windows technology that has been deprecated and unsupported by Microsoft for many years. It is not compatible with modern isolation and sandboxing models used by browsers.
31+
32+
Because of this, TDI-based traffic visibility becomes increasingly unstable. In some browsers, it has already disappeared completely, and it will eventually stop working altogether.
33+
34+
AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves.
35+
36+
## Temporary solution
37+
38+
Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic.
39+
40+
### How to modify the registry in Chromium-based browsers
41+
42+
:::warning
43+
44+
Administrator rights are required to edit the registry. Incorrect changes may affect system or browser stability and security. Always create a backup of the registry branch before modifying it.
45+
46+
Before proceeding, keep in mind that this solution reduces sandbox/AppContainer security, making the browser less isolated. It applies system-wide because it modifies `HKLM`, and should only be used for debugging, temporary workarounds, in controlled environments, or when TDI-based traffic interception is strictly necessary.
47+
48+
It should **not** be applied broadly across end-user machines. **Proceed only if you understand the implications.**
49+
50+
:::
51+
52+
You can apply the necessary registry changes automatically by using one of the pre-generated .reg files below. Each file disables AppContainer/Network Service sandboxing for a specific Chromium-based browser:
53+
54+
- [Download Chrome.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Chrome.reg)
55+
- [Download Chromium.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Chromium.reg)
56+
- [Download Edge.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Edge.reg)
57+
- [Download Brave.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Brave.reg)
58+
- [Download Vivaldi.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Vivaldi.reg)
59+
- [Download YandexBrowser.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_YandexBrowser.reg)
60+
61+
If your browser is not listed, follow the manual instructions below to create the necessary registry entries:
62+
63+
1. Determine its policy branch by checking the vendor’s official documentation or by opening the internal policy page. In Chrome, navigate to `chrome://policy`. Other browsers use a similar path.
64+
65+
2. Identify the correct registry branch for your browser. Different Chromium-based browsers use different policy paths under `HKLM`. It should follow the model `HKLM\SOFTWARE\Policies\<Vendor>\<Product>`.
66+
67+
3. Open the Registry Editor:
68+
69+
- Press _Win + R_
70+
- Type _regedit_ and press _Enter_
71+
- Approve the UAC prompt by running it as administrator
72+
73+
4. Back up the Policies branch:
74+
75+
- In the left panel, navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Policies`
76+
- Right-click _Policies_ → _Export_
77+
- Save the file as _Policies_backup.reg_
78+
79+
If something goes wrong, you can restore the backup by double-clicking this file.
80+
81+
5. Navigate to your browser’s policy key:
82+
83+
- Expand the path `HKEY_LOCAL_MACHINE` → _SOFTWARE_ → _Policies_.
84+
- Locate the folder corresponding to your browser.
85+
86+
If the key does not exist, you can create it manually. Example for Chrome:
87+
88+
- Right-click _Policies_ → _New_ → _Key_ and name it `Google`
89+
- Inside `Google`, create another key named `Chrome`
90+
91+
Repeat the same logic for Chromium, Edge, Brave, Vivaldi, Yandex Browser, etc. You should end up with a key that looks like `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\<Vendor>\<Product>`.
92+
93+
1. Add the required registry values:
94+
95+
- In the correct key, click the right panel → _New_ → _DWORD (32-bit) Value_
96+
97+
- Name it `RendererAppContainerEnabled`
98+
99+
- Double-click it and set:
100+
101+
- **Value:** 0
102+
- **Base:** Hexadecimal or Decimal (either is fine)
103+
104+
- Repeat the process and create a second DWORD `NetworkServiceSandboxEnabled`.
105+
106+
- Set its value to 0.
107+
108+
Both parameters must be `REG_DWORD` and have the value **0**.
109+
110+
2. Close the browser and apply the settings. To ensure the policy is loaded:
111+
112+
- Fully close the browser
113+
- Check Task Manager and make sure no processes such as _chrome.exe_, _msedge.exe_, _brave.exe_ remain running
114+
- Reopen the browser
115+
116+
3. Verify that the policies have been applied by opening the policy viewer for your browser.
117+
118+
You should see the following policies active:
119+
120+
- `RendererAppContainerEnabled` — **0 / false**
121+
- `NetworkServiceSandboxEnabled` — **0 / false**
122+
123+
If available, click _Reload policies_.
124+
125+
Done!
126+
127+
## Permanent solution
128+
129+
We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780).

‎i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md‎

Lines changed: 129 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,129 @@
1+
---
2+
title: Filtering issues in Chrome 142+ when using the TDI driver
3+
sidebar_position: 14
4+
---
5+
6+
:::info
7+
8+
This article covers AdGuard for Windows, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock).
9+
10+
:::
11+
12+
Some AdGuard for Windows users may notice that [the app stops filtering traffic in Chromium-based browsers](https://github.com/AdguardTeam/AdguardForWindows/issues/5771). Starting from Google Chrome 142+, browser traffic simply does not appear at the TDI driver level, preventing AdGuard from inspecting or filtering it.
13+
14+
This behavior is not a bug in AdGuard, but a result of recent architectural and security changes in modern browsers.
15+
16+
## Why this happens
17+
18+
Chromium-based browsers (Chrome, Edge, Brave, Vivaldi, etc.) have been strengthening their security architecture. One significant change is moving sensitive internal processes into the [Windows AppContainer sandbox](https://learn.microsoft.com/en-us/windows/win32/secauthz/appcontainer-isolation), including the Network Service, which handles all browser traffic.
19+
20+
### What changed in Chrome 142
21+
22+
Starting from Chrome 142, the Network Service process is now launched inside AppContainer by default.
23+
24+
When this happens, applications running in an AppContainer do not use the legacy TDI networking interface; instead, their traffic is routed through the more modern WSK (Winsock Kernel) stack. As a result, the TDI driver cannot see, intercept, or process connections that go through WSK, and all browser traffic becomes invisible to the TDI driver used by AdGuard.
25+
26+
This behavior is controlled entirely by Chrome’s sandboxing policies and internal experiments (field trials), not by user settings.
27+
28+
## Why this affects AdGuard
29+
30+
The TDI driver is an outdated Windows technology that has been deprecated and unsupported by Microsoft for many years. It is not compatible with modern isolation and sandboxing models used by browsers.
31+
32+
Because of this, TDI-based traffic visibility becomes increasingly unstable. In some browsers, it has already disappeared completely, and it will eventually stop working altogether.
33+
34+
AdGuard already treats the TDI driver as deprecated, and its complete removal is planned as the product evolves.
35+
36+
## Temporary solution
37+
38+
Certain Windows registry changes can force the browser to stop using AppContainer, causing its processes to run in a non-sandboxed mode again. Network Service stops using the WSK stack and falls back to a network path that the TDI driver can see. AdGuard then regains the ability to filter browser traffic.
39+
40+
### How to modify the registry in Chromium-based browsers
41+
42+
:::warning
43+
44+
Administrator rights are required to edit the registry. Incorrect changes may affect system or browser stability and security. Always create a backup of the registry branch before modifying it.
45+
46+
Before proceeding, keep in mind that this solution reduces sandbox/AppContainer security, making the browser less isolated. It applies system-wide because it modifies `HKLM`, and should only be used for debugging, temporary workarounds, in controlled environments, or when TDI-based traffic interception is strictly necessary.
47+
48+
It should **not** be applied broadly across end-user machines. **Proceed only if you understand the implications.**
49+
50+
:::
51+
52+
You can apply the necessary registry changes automatically by using one of the pre-generated .reg files below. Each file disables AppContainer/Network Service sandboxing for a specific Chromium-based browser:
53+
54+
- [Download Chrome.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Chrome.reg)
55+
- [Download Chromium.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Chromium.reg)
56+
- [Download Edge.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Edge.reg)
57+
- [Download Brave.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Brave.reg)
58+
- [Download Vivaldi.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_Vivaldi.reg)
59+
- [Download YandexBrowser.reg](https://cdn.adtidy.org/distr/windows/reg/DisableAppContainer_YandexBrowser.reg)
60+
61+
If your browser is not listed, follow the manual instructions below to create the necessary registry entries:
62+
63+
1. Determine its policy branch by checking the vendor’s official documentation or by opening the internal policy page. In Chrome, navigate to `chrome://policy`. Other browsers use a similar path.
64+
65+
2. Identify the correct registry branch for your browser. Different Chromium-based browsers use different policy paths under `HKLM`. It should follow the model `HKLM\SOFTWARE\Policies\<Vendor>\<Product>`.
66+
67+
3. Open the Registry Editor:
68+
69+
- Press _Win + R_
70+
- Type _regedit_ and press _Enter_
71+
- Approve the UAC prompt by running it as administrator
72+
73+
4. Back up the Policies branch:
74+
75+
- In the left panel, navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Policies`
76+
- Right-click _Policies_ → _Export_
77+
- Save the file as _Policies_backup.reg_
78+
79+
If something goes wrong, you can restore the backup by double-clicking this file.
80+
81+
5. Navigate to your browser’s policy key:
82+
83+
- Expand the path `HKEY_LOCAL_MACHINE` → _SOFTWARE_ → _Policies_.
84+
- Locate the folder corresponding to your browser.
85+
86+
If the key does not exist, you can create it manually. Example for Chrome:
87+
88+
- Right-click _Policies_ → _New_ → _Key_ and name it `Google`
89+
- Inside `Google`, create another key named `Chrome`
90+
91+
Repeat the same logic for Chromium, Edge, Brave, Vivaldi, Yandex Browser, etc. You should end up with a key that looks like `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\<Vendor>\<Product>`.
92+
93+
1. Add the required registry values:
94+
95+
- In the correct key, click the right panel → _New_ → _DWORD (32-bit) Value_
96+
97+
- Name it `RendererAppContainerEnabled`
98+
99+
- Double-click it and set:
100+
101+
- **Value:** 0
102+
- **Base:** Hexadecimal or Decimal (either is fine)
103+
104+
- Repeat the process and create a second DWORD `NetworkServiceSandboxEnabled`.
105+
106+
- Set its value to 0.
107+
108+
Both parameters must be `REG_DWORD` and have the value **0**.
109+
110+
2. Close the browser and apply the settings. To ensure the policy is loaded:
111+
112+
- Fully close the browser
113+
- Check Task Manager and make sure no processes such as _chrome.exe_, _msedge.exe_, _brave.exe_ remain running
114+
- Reopen the browser
115+
116+
3. Verify that the policies have been applied by opening the policy viewer for your browser.
117+
118+
You should see the following policies active:
119+
120+
- `RendererAppContainerEnabled` — **0 / false**
121+
- `NetworkServiceSandboxEnabled` — **0 / false**
122+
123+
If available, click _Reload policies_.
124+
125+
Done!
126+
127+
## Permanent solution
128+
129+
We’re planning to add support for the SockFilter driver in the upcoming versions. It will fix the issue by solving conflicts in the WFP stack. [More information](https://github.com/AdguardTeam/AdguardForWindows/issues/5780).

0 commit comments

Comments
 (0)