Skip to main content
jacekt22606938
Participant
Nov 17, 2026 2:24 PM UTC
Open for Voting

**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.

    2 replies

    Srishti Bali
    Community Manager
    Community Manager
    Nov 17, 2026 8:37 PM UTC

    Hi ​@jacekt22606938 

     

    Thank you for reaching out and sharing such a detailed explanation of the issue, along with the troubleshooting steps you've already performed. This information is extremely helpful in understanding the behavior.

    To investigate this further, could you please share the following details?

    1. Please open Lightroom Classic, navigate to Help > System Info, and copy and share the complete system information.

    2. Check how it works with different network like mobile hotspot etc.

    3. When the issue occurs, please open Task Manager > Processes and share a screenshot showing the network activity of the running applications.

    4. Please open Lightroom Classic and navigate to Edit > Preferences > General. Press and hold the Alt key to reveal the option to Generate Diagnostic logs. Click the option to generate the logs and share the resulting file with us.

    Since you mentioned that the issue seems to occur after using AI Denoise, it would also be helpful to know whether you've observed the same behavior during sessions where AI Denoise was not used.

    Once we have these details, we can investigate further and determine the next steps.

    Translate
    Thanks, Srishti Bali | Community & Engagement Strategist, Digital Imaging | Adobe
    jacekt22606938
    Participant
    Nov 18, 2026 6:14 AM UTC

    Thank you for the quick and thorough reply.

    Before you spend time on this, I need to correct my original report — further testing after I posted it indicates **Lightroom Classic was most likely not the cause**.

    What changed:

    1. Later the same evening the throttling returned **with Lightroom Classic fully closed** (no Adobe processes running). My original claim that closing LrC reliably restores full speed does not hold — the two instances where it appeared to work now look like coincidence.

    2. The actual pattern turned out to be **degradation after a series of large uploads**, regardless of which applications were running. A second PC on the same network, performing the same series of uploads, showed no degradation at all — so the problem is specific to this machine.

    3. Running `netsh winsock reset` followed by a reboot resolved it. After that, seven consecutive large uploads completed at full speed, where previously the machine would throttle after a similar volume. I am still monitoring whether this holds over the coming days.

    So at this point the evidence points to something in the Windows networking stack on this laptop, not to Lightroom Classic.

    I am sorry for the false lead. If the problem recurs and I find any genuine correlation with LrC or AI Denoise, I will gather the diagnostics you listed — System Info, diagnostic logs, Task Manager network activity — and open a new report with proper evidence.

    For the record on your question: I do not currently have data on whether the behaviour differs between sessions with and without AI Denoise, which is precisely why I should not have named it as a likely factor.

    Thanks again for taking the time.

    Translate