Why Cumulative Updates Take Different Times on Identical PCs

Quick fix: “Identical PCs” aren’t really identical. Different storage I/O, network speed, installed apps, antivirus, and background processes affect update time. Settings → System → Storage to see disk space. Task Manager during update shows what’s slowing it. SSD vs HDD: 5-10x difference. Even same SSD: wear, free space, fragmentation differ.

Update times vary even on identical hardware due to: storage health, network conditions, AV interference, accumulated state. Verify identical underlying conditions before comparing.

What causes this

Two PCs with same model + specs may still differ:

• Storage health: one SSD may be worn, slower.
• Free space: tight free space slows installs.
• Network: one on 5GHz, other 2.4GHz, ISP throughput.
• Installed apps + dependencies: more installed = more to update.
• Antivirus: scans during install can slow.
• Cumulative update applies on top of current build; if builds differ, install differs.

Method 1: Check storage health

The standard diagnostic.

1. Open Settings → System → Storage. Free space on C:.
2. Need 20GB+ for smooth update install.
3. Check disk health: install CrystalDiskInfo. Run.
4. Check:
   • Health: Good / Caution / Bad.
   • Power on hours: high = older.
   • Wear level (SSDs): 100% = new, lower = worn.
5. Worn SSD = slower writes = slower updates.
6. For HDDs: defragmentation status. Settings → System → Storage → Optimize Drives.
7. For chronic slow: replace drive.

This is the storage check.

Method 2: Check network speed

For download phase.

1. Download phase uses Internet.
2. Test at speedtest.net.
3. For one PC slower: Wi-Fi 2.4GHz vs 5GHz, distance from router, interference.
4. For Ethernet vs Wi-Fi: Ethernet faster.
5. For network adapter driver: update.
6. For Delivery Optimization: enables P2P from other PCs on LAN. Faster if first PC already downloaded.
7. Settings → Windows Update → Advanced → Delivery Optimization → turn on Allow downloads from other PCs (Local network).

This is the network check.

Method 3: Reduce variables for testing

For specific comparison.

1. To compare apples-to-apples:
   • Same Windows build before update.
   • Same antivirus (or both with Defender only).
   • Same number of installed apps.
   • Same free space.
   • Same network connection.
   • Same time of day.
2. Then start updates simultaneously. Compare.
3. For corporate fleet: image deployment. All PCs from same image. Then compare.
4. For chronic slow on one PC: clear SoftwareDistribution + catroot2, fresh start.
5. For monitor during install: Task Manager → Performance → Disk + Network. Identify bottleneck.

This is the comparison route.

How to verify the fix worked

• Updates complete in expected time.
• System functional.
• Comparing PCs: similar times within ~30% margin.

If none of these work

If chronic: Specific cumulative update: some are larger / more complex. For specific PC with antivirus: corporate AV may interfere. Test with Windows Defender only. For chronic Windows Update issues: SFC + DISM repair. For chronic Microsoft Update Catalog manual install: download .msu directly. For Insider Channels: more variability. For specific OEM customizations: vendor drivers may affect install. For chronic disk issues: replace drive.

Bottom line: Storage health, free space, network speed, installed apps all affect update time. CrystalDiskInfo to check SSD wear. SSD vs HDD = huge difference. Compare under controlled conditions for apples-to-apples test.