**Lightroom Classic collapses system-wide network throughput to ~1% while running (Windows 11)**
I have a reproducible issue where running Lightroom Classic drops network throughput for the **entire system** — not just for Lightroom — to roughly 1% of normal. Closing LrC restores full speed instantly, with no reboot required.
**System**
- Lenovo Legion Pro 7, RTX 5080 Laptop GPU, 64 GB RAM
- Windows 11, build 10.0.26300.9974
- Lightroom Classic 16.0 Camera Raw 19.0
- Intel Wi-Fi 7 BE200 (driver 24.70.0.3) and onboard Ethernet
- 1 Gbps cable connection
**Symptom**
After a period of work in LrC, all internet transfers on the machine slow to a crawl. Measured today:
| | LrC running | LrC closed |
|---|---|---|
| Download | 12.1 Mbps | 903 Mbps |
| Upload | 0.27 Mbps | 39.5 Mbps |
| Ping | 18 ms | 18 ms |
Reproduced twice on the same day, several hours apart. Both times closing LrC restored full speed within seconds.
**Key observation: this is not bandwidth saturation**
While throttled, Resource Monitor reported total network activity of ~352 Kb/s and **0% network utilization**. The link was essentially idle. Nothing was consuming bandwidth — yet no application could transfer at more than ~1% of line speed. Ping stayed low and stable throughout, and packet loss was zero on every TCP connection.
**What I have ruled out**
- **Router / ISP / line**: a second PC on the same network, tested at the same moment, reached 717 Mbps.
- **Network adapter**: identical throttling over Wi-Fi and over wired Ethernet with Wi-Fi fully disabled. Wi-Fi link rate was negotiated at 1729/865 Mbps throughout.
- **Browser**: identical results in Brave and Edge.
- **Lightroom sync**: disabled. No synced collections, Preferences > Lightroom Sync shows "No sync activity". Preferences > Network tab is empty.
- **Creative Cloud desktop app**: not running.
- **Dropbox**: paused during a test — no effect.
- **System resources**: CPU 2%, disks 0–1%, RAM 32/64 GB used, GPU idle at 45°C, non-paged pool 791 MB.
- **TCP stack**: `netsh int tcp show global` shows Receive Window Auto-Tuning normal, RSS enabled, pacing off. `netstat` showed 5 connections in TIME_WAIT, so no ephemeral port exhaustion.
- **Proxy / VPN**: none configured. Microsoft Defender only, no third-party security software.
- `netsh int ip reset` and `ipconfig /flushdns` made no difference.
**Possibly relevant**
The only networked LrC feature I use is **AI Denoise**, which I run regularly on batches of images. The problem appears after a period of work rather than immediately on launch, and it does not clear itself after denoising finishes — it persists until LrC is closed.
**Questions**
1. Is this a known issue in current LrC builds?
2. Is there any LrC background network activity (licensing checks, Denoise service calls, telemetry) that could block or exhaust the Windows network stack without consuming bandwidth?
3. What additional logs or diagnostics would be useful? I can reproduce this reliably and capture whatever is needed.
Any pointers appreciated.
