Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that

:::

![App management](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/management.png)

In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.

Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
Expand All @@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

![App stats](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/stats_app.png)

## “Problem-free” and “problematic” apps
## How app filtering and routing work in AdGuard for Windows v8.0

AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.

There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.

To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.

:::note

“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.

:::

Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).

These are determined by three sources:

- _Compatibility list_

Apps that have been tested by our team and are confirmed to work correctly with filtering.
This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).

Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
- _Exclusion lists_

To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.

- _Filter unknown apps_

This setting defines how all other apps (not present in any list) are handled.

:::info

The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.

:::

## Filter unknown apps

![Filter unknown apps \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/app-management.png)

The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists

When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.

When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.

Here is a quick overview of how different app categories behave depending on this setting:

| App category | Toggle on (default) | Toggle off |
| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
| Compatible, or problem-free (e.g., browsers) | · Routing ✅ <br /> · Filtering ✅ <br /> · HTTPS filtering ✅ | Same behavior — does not depend on toggle |
| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌ <br /> · Filtering ❌ <br /> · HTTPS filtering ❌ | Same behavior — does not depend on toggle |
| Others / (newly detected, unknown, not in lists) | · Routing ✅ <br /> · Filtering ✅ <br /> · HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |

:::info What happens on reset

If you click **Reset to default**, two things happen:

1. All app-specific permissions are cleared (set to “not configured”).
2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.

:::
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that

:::

![App management](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/management.png)

In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.

Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
Expand All @@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

![App stats](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/stats_app.png)

## “Problem-free” and “problematic” apps
## How app filtering and routing work in AdGuard for Windows v8.0

AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.

There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.

To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.

:::note

“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.

:::

Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).

These are determined by three sources:

- _Compatibility list_

Apps that have been tested by our team and are confirmed to work correctly with filtering.
This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).

Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
- _Exclusion lists_

To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.

- _Filter unknown apps_

This setting defines how all other apps (not present in any list) are handled.

:::info

The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.

:::

## Filter unknown apps

![Filter unknown apps \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/app-management.png)

The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists

When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.

When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.

Here is a quick overview of how different app categories behave depending on this setting:

| App category | Toggle on (default) | Toggle off |
| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
| Compatible, or problem-free (e.g., browsers) | · Routing ✅ <br /> · Filtering ✅ <br /> · HTTPS filtering ✅ | Same behavior — does not depend on toggle |
| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌ <br /> · Filtering ❌ <br /> · HTTPS filtering ❌ | Same behavior — does not depend on toggle |
| Others / (newly detected, unknown, not in lists) | · Routing ✅ <br /> · Filtering ✅ <br /> · HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |

:::info What happens on reset

If you click **Reset to default**, two things happen:

1. All app-specific permissions are cleared (set to “not configured”).
2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.

:::
Original file line number Diff line number Diff line change
Expand Up @@ -9,24 +9,80 @@ Tento článek popisuje AdGuard pro Windows v8.0, multifunkční blokátor rekla

:::

![App management](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/management.png)
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.

V části _Správa aplikací_ můžete spravovat nastavení směrování a filtrování pro všechny aplikace nainstalované ve vašem zařízení.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.

Jakmile AdGuard zjistí, že se aplikace připojila k internetu, automaticky ji přidá do _Správy aplikací_ a její provoz je přesměrován skrze AdGuard.
By default, AdGuard filters all traffic, but you can choose what to exclude.

Ve výchozím nastavení AdGuard filtruje veškerý provoz, ale můžete si vybrat, co chcete vyloučit.
AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.

AdGuard také filtruje HTTPS provoz, protože většina webových stránek dnes používá HTTPS. To je obzvláště důležité pro blokování reklam na stránkách jako youtube.com, facebook.com a x.com, kde není možné odstranit reklamy bez filtrování HTTPS.
When routing and filtering are enabled for an app, the icons below each app will appear green.

Pokud jsou pro aplikaci povoleny směrování a filtrování, ikony pod každou aplikací se zobrazí zeleně.

Nastavení můžete ponechat beze změny, deaktivovat filtrování i směrování nebo je ručně doladit pro každou aplikaci. Můžete také přistupovat ke statistikám aplikace.
You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.

![App stats](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/stats_app.png)

## “Kompatibilní” a ”nekompatibilní” aplikace
## How app filtering and routing work in AdGuard for Windows v8.0

AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.

There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.

To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.

:::note

“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.

:::

Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).

These are determined by three sources:

- _Compatibility list_

Apps that have been tested by our team and are confirmed to work correctly with filtering.
This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).

Většina aplikací funguje po filtrování správně. Některé aplikace jsou považovány za “problematické“ a při směrování skrze AdGuard nemusí fungovat správně. Při pokusu o směrování nebo filtrování všech aplikací se může zobrazit následující varování:
- _Exclusion lists_

Pro zajištění správného fungování všech aplikací nainstalovaných v zařízení důrazně doporučujeme, abyste skrze AdGuard směrovali pouze kompatibilní aplikace.
Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.

- _Filter unknown apps_

This setting defines how all other apps (not present in any list) are handled.

:::info

The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.

:::

## Filter unknown apps

![Filter unknown apps \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/version_8/app_management/app-management.png)

The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists

When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.

When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.

Here is a quick overview of how different app categories behave depending on this setting:

| App category | Toggle on (default) | Toggle off |
| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
| Compatible, or problem-free (e.g., browsers) | · Routing ✅ <br /> · Filtering ✅ <br /> · HTTPS filtering ✅ | Same behavior — does not depend on toggle |
| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌ <br /> · Filtering ❌ <br /> · HTTPS filtering ❌ | Same behavior — does not depend on toggle |
| Others / (newly detected, unknown, not in lists) | · Routing ✅ <br /> · Filtering ✅ <br /> · HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |

:::info What happens on reset

If you click **Reset to default**, two things happen:

1. All app-specific permissions are cleared (set to “not configured”).
2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.

:::
Loading
Loading