AdguardTeam / AdguardTeam/AdguardForWindows

Statistics ON causes 95–100% Disk 0 active time; OFF drops it immediately to 0% (8.0.5560.0)

Abierto
#6,162 8 comentarios 2 reacciones 1 asignado Asignado a @pakifev Ver en GitHub
Bug Priority: P3 Version: AdGuard v8.0.4
Lenguaje dominante
Sin datos de lenguaje
Estrellas
887
Forks
84
Merge medio
27 min
PR fusionados (30 d)
2

Descripción

### Please answer the following questions for yourself before submitting an issue

- [x] Filters were updated before reproducing an issue
- [x] I checked the [knowledge base](https://adguard.com/kb/) and found no answer
- [x] I checked to make sure that this issue has not already been filed

### AdGuard version

8.0.5560.0

### Browser version

Not applicable (system-wide disk I/O issue; reproduced independently of browser)

### OS version

Windows 11 25H2, build 26200.9168

### Traffic filtering

- [x] yes, I do

### Ad Blocking

_No response_

### Privacy

_No response_

### Social

_No response_

### Annoyances

_No response_

### Security

_No response_

### Other

_No response_

### Language-specific

_No response_

### Which DNS server do you use?

DNS protection disabled

### DNS protocol

None

### Custom DNS

_No response_

### What Stealth Mode options do you have enabled?

_No response_

### Support ticket ID

_No response_

### Issue Details

Steps to reproduce:
1. Run AdGuard for Windows 8.0.5560.0 with protection enabled.
2. Enable Statistics.
3. Observe Disk 0 active time increase to 95–100%; Windows becomes extremely slow.
4. Disable Statistics.
5. Observe Disk 0 active time immediately fall to 0%.
6. Re-enable Statistics and repeat; the pattern is reproducible.

The A/B result is immediate and consistent:
- AdGuard enabled + Statistics OFF: Disk 0 = 0%, queue = 0, read/write = 0.
- Statistics ON: Disk 0 = approximately 95–100%.
- Statistics OFF again: Disk 0 = 0% immediately.

During the affected state, Resource Monitor repeatedly shows activity against `C:\ProgramData\Adguard\statistics.db-wal`.

I searched the open issues before filing. #5620 is related, but it describes temporary disk usage after service/OS startup, not this persistent and immediately reversible Statistics ON/OFF pattern. #5809 is closed as Cannot Reproduce and did not isolate Statistics as the trigger.

### Expected Behavior

Statistics collection should operate without saturating the system disk or making Windows unresponsive. Disabling Statistics should not be required to keep disk latency and active time normal.

### Actual Behavior

With Statistics enabled, Disk 0 reaches 95–100% active time and Windows becomes extremely slow. Disabling Statistics makes Disk 0 fall immediately to 0%. The behavior returns when Statistics is enabled again.

Observed maximum latencies:
- One reproduction: Read 489 ms / Write 1613 ms.
- Other reproductions: Read 229 ms / Write 353 ms.

Current workaround: keep Statistics disabled while leaving AdGuard protection enabled.

### Screenshots

Screenshot 1

### Additional Information

### Environment
- AdGuard for Windows: 8.0.5560.0
- OS: Windows 11 25H2, build 26200.9168
- System disk: Crucial T710 4 TB
- SSD firmware: PBCR5103
- NVMe driver: `stornvme.sys` 10.0.26100.8972
- Free space during testing: 814 GB
- TRIM: enabled
- SSD health: Healthy

### Diagnostics already performed
- No relevant errors from stornvme, storport, Disk, or WHEA.
- SFC and DISM completed cleanly.
- Reproduced with Windows Search disabled.
- PCIe ASPM was disabled.
- AdGuard VPN 2.10.2148.0 was ruled out as the primary cause: stopping it reduced activity only slightly, while the Statistics ON/OFF change in AdGuard for Windows controls the symptom immediately.

### Fresh statistics database test
The existing `statistics.db` (approximately 11.09 MB) was moved to a backup and AdGuard was allowed to create a fresh statistics database. The problem still reproduced, so recreating the database did not resolve it.

Related issues: #5620 and #5809.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.