qWAVE Cache
Windows Quality Windows Audio Video Experience stores service-level cache data under the LocalService profile to support QoS policy lookups, flow state, and related temporary metadata used when the qWAVE service prioritizes audio and video traffic. That cache helps Windows and compatible apps reuse network quality information instead of recalculating it for every session, but stale entries can linger after network changes, policy updates, or driver changes. Kudu removes the qWAVE service cache files from this location while leaving user accounts, app data, saved settings, and passwords untouched.
Why clean qWAVE Cache?
- Stale QoS flow metadata after a network change can make Windows apply outdated traffic prioritization, which shows up as choppy video calls or inconsistent audio quality on a connection that otherwise tests fine
- Cached policy results from an old adapter, VPN, or Group Policy state can cause qWAVE to classify traffic incorrectly, leading to conferencing or streaming apps suddenly losing their usual call stability
- Corrupted service cache entries can delay qWAVE initialization or force the service to rebuild state repeatedly, which users notice as slow recovery when starting voice or video apps after boot
- Leftover cache data from previous NIC or driver versions can conflict with current network conditions, producing intermittent buffering, jitter, or uneven media playback that disappears after the cache is rebuilt
- A bloated qWAVE cache can preserve obsolete flow information for networks you no longer use, making troubleshooting harder when media quality problems follow you between Wi-Fi and Ethernet
- Clearing the cache forces qWAVE to regenerate fresh network quality state for current conditions, often resolving cases where real-time audio and video behave poorly only on one Windows machine
Cache paths Kudu targets
Windows
%WinDir%/ServiceProfiles/LocalService/AppData/Local/Microsoft/Windows/qWave |
Common questions about qWAVE Cache
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.