Les mises à jour facultatives qui n’apparaissent pas ou qui restent bloquées sont un problème fréquent, et la bonne nouvelle : la plupart des causes sont réparables sans perdre de données. Si vous voyez que Optional updates don’t work, cet article explique pourquoi cela se produit et comment résoudre chaque cause pas à pas.
Vous apprendrez les raisons les plus courantes (services stoppés, cache corrompu, paramètres réseau, stratégies de groupe, antivirus, etc.), un guide rapide pour corriger le problème, puis des corrections détaillées et des commandes précises à exécuter sur Windows 10.
Key Takeaway
La plupart des problèmes d’updates facultatifs viennent d’un service Windows Update ou d’un cache corrompu ; redémarrer et réparer les services liés à Windows Update, vider le cache SoftwareDistribution et exécuter les outils de réparation intégrés (SFC/DISM) résout la majorité des cas.
Quick Fix Guide
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| 1. Windows Update service stopped/disabled | Start or set Windows Update service to Automatic and restart it. |
| 2. Background Intelligent Transfer Service (BITS) stopped | Start Background Intelligent Transfer Service and set to Automatic (Delayed Start). |
| 3. Pending restart or stuck update | Restart PC and check Settings > Update & Security > Windows Update for pending restart. |
| 4. Corrupted update cache (SoftwareDistribution/Catroot2) | Stop update services, delete C:\Windows\SoftwareDistribution and Catroot2, then restart services. |
| 5. Metered or limited connection | Turn off metered connection in Settings > Network & Internet > Wi‑Fi (or Ethernet). |
| 6. Group Policy or Registry blocking optional updates | Check gpedit.msc or registry keys that control Windows Update visibility. |
| 7. Third‑party antivirus or firewall interference | Temporarily disable/uninstall AV or firewall and test updates. |
| 8. Windows Update components corrupted (WU Agent) | Run DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow. |
| 9. Delivery Optimization or WSUS/Proxy settings | Reset Delivery Optimization, ensure no WSUS/Proxy policies block optional updates. |
| 10. Network/DNS or Microsoft server outage | Test internet, change DNS, or wait/retry if Microsoft servers are the issue. |
Detailed Fixes for “Optional updates don’t work”
1. Windows Update service stopped/disabled
Why it causes the problem
- Windows Update is the core service that detects, downloads and installs updates. If it’s stopped or disabled, optional updates won’t appear or download.
Step-by-step solution
- Press Windows + R, type services.msc, press Enter.
- Find Windows Update in the list and double‑click it.
- Set Startup type to Automatic (Delayed Start) and click Start if the service is stopped.
- Click Apply and OK.
- Reopen Settings > Update & Security > Windows Update and click Check for updates.
Note: If the service fails to start, check Event Viewer (Event Viewer > Windows Logs > System) for error codes.
2. Background Intelligent Transfer Service (BITS) stopped
Why it causes the problem
- BITS handles background downloads for Windows Update. If it’s stopped, downloads can stall or never start.
Step-by-step solution
- Open services.msc.
- Locate Background Intelligent Transfer Service and double‑click.
- Set Startup type to Automatic (Delayed Start) and click Start.
- Apply changes and restart the PC.
Tip: BITS depends on the Cryptographic and DCOM Server Process Launcher services—ensure those are running.
3. Pending restart or stuck update
Why it causes the problem
- Some updates require a restart to finalize previous changes before optional updates are offered.
Step-by-step solution
- Go to Settings > Update & Security > Windows Update.
- If you see Restart required, click Restart now or schedule the restart.
- After reboot, check updates again and install optional updates.
Tip: If no restart is shown but updates still fail, run Windows Update Troubleshooter in Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update.
4. Corrupted update cache (SoftwareDistribution/Catroot2)
Why it causes the problem
- The update cache stores downloaded updates and metadata; corruption prevents detection and installation.
Step-by-step solution
- Open an elevated Command Prompt: press Windows, type cmd, right‑click Command Prompt, choose Run as administrator.
- Stop services:
- net stop wuauserv
- net stop bits
- net stop cryptsvc
- Rename/delete cache folders:
- ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
- ren C:\Windows\System32\catroot2 catroot2.old
- Restart services:
- net start wuauserv
- net start bits
- net start cryptsvc
- Open Settings > Update & Security > Windows Update and click Check for updates.
Note: Renaming keeps a backup; you can delete the old folders after a successful update.
5. Metered or limited connection
Why it causes the problem
- Windows treats metered connections as pay-per-use and may block optional updates to save data.
Step-by-step solution
- Go to Settings > Network & Internet > Wi‑Fi (or Ethernet).
- Click your network connection and turn off Set as metered connection.
- Return to Windows Update and check for updates.
Tip: On managed enterprise networks, IT may enforce metered-like settings via policy.
6. Group Policy or Registry blocking optional updates
Why it causes the problem
- Enterprises or misconfigured settings can hide optional updates or prevent manual update checks.
Step-by-step solution (Local Group Policy)
- Press Windows + R, type gpedit.msc, press Enter.
- Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update.
- Look for policies like Do not include drivers with Windows Updates or Configure Automatic Updates and set them to Not Configured or adjust accordingly.
- Run gpupdate /force in an elevated Command Prompt.
Step-by-step solution (Registry)
- Press Windows + R, type regedit, press Enter.
- Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate and check for keys that enforce WSUS or disable updates (e.g., WUServer, WUAUOptions).
- Export the key as backup, then delete or modify problematic entries. Reboot.
Warning: Editing Group Policy/Registry can affect system behavior; back up before changes.
7. Third‑party antivirus or firewall interference
Why it causes the problem
- Some security products block Windows Update traffic or lock files the update service needs.
Step-by-step solution
- Temporarily disable antivirus/firewall from its system tray icon or app settings.
- Retry Settings > Update & Security > Windows Update > Check for updates.
- If updates work, configure the security product to whitelist Windows Update components or update the security software.
Tip: If disabling isn’t an option, uninstall the AV temporarily and test; reinstall afterward.
8. Windows Update components corrupted (WU Agent)
Why it causes the problem
- Corrupted system files or a damaged Windows Update Agent prevent proper update discovery and installation.
Step-by-step solution
- Open an elevated Command Prompt.
- Run system health checks:
- DISM /Online /Cleanup-Image /RestoreHealth
- After DISM completes, run sfc /scannow
- Reboot the PC and check for updates.
Note: DISM may take 10–30 minutes depending on corruption and connection.
9. Delivery Optimization, WSUS, or Proxy blocking optional updates
Why it causes the problem
- Delivery Optimization settings, WSUS (Windows Server Update Services), or proxy configurations can limit update sources and block optional updates.
Step-by-step solution
- Check Delivery Optimization: Settings > Update & Security > Delivery Optimization, toggle Allow downloads from other PCs as needed or disable to test.
- If domain-joined, open Settings > Update & Security > Windows Update > Advanced options > Choose how updates are delivered to verify.
- For WSUS/proxy: open gpedit.msc and look under Windows Update for WSUS server settings; remove if wrongly configured.
- For proxy: Settings > Network & Internet > Proxy; turn off proxy or set correctly.
Tip: In corporate environments, contact IT—WSUS may intentionally withhold optional updates.
10. Network/DNS or Microsoft server outage
Why it causes the problem
- Connectivity problems or temporary Microsoft server outages can prevent optional updates from appearing.
Step-by-step solution
- Test internet access and browse to a few sites.
- Try changing DNS to Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1) in Network & Internet > Adapter options > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties.
- Run ping update.microsoft.com or nslookup to test name resolution.
- If Microsoft servers are down, wait and retry later; check https://status.microsoft.com/ or community reports.
Tip: Use a different network (mobile hotspot) to rule out local ISP issues.
Outils supplémentaires et journalisation (section supplémentaire utile)
Why this helps
- Collecting logs and using built‑in tools helps diagnose persistent or unusual failures.
Useful commands and tools
- Generate update log: open PowerShell as admin and run Get-WindowsUpdateLog (creates WindowsUpdate.log on Desktop).
- Force update scan: run wuauclt /detectnow (legacy) and UsoClient StartScan (undocumented but often works) from an elevated command prompt.
- Check update history: Settings > Update & Security > Windows Update > View update history.
- Event Viewer: Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient for detailed failures.
When to collect logs
- If you must escalate to Microsoft Support or IT, include WindowsUpdate.log, relevant event log entries, and a screenshot of Windows Update errors.
FAQ
Q: Why are optional updates different from regular Windows Update patches?
Optional updates include driver updates, feature previews, and certain non‑critical fixes; they aren’t forced automatically and may be hidden by settings like metered connections or group policy.
Q: Can I safely delete the SoftwareDistribution folder?
Yes — stop Windows Update, rename or delete C:\Windows\SoftwareDistribution; Windows will recreate it. Keep a renamed backup (e.g., SoftwareDistribution.old) until you confirm everything works.
Q: Will temporarily disabling antivirus harm my PC?
Temporarily disabling is safe for short troubleshooting; if possible disconnect from the internet while disabled and re‑enable it as soon as tests complete. Prefer adding exceptions rather than uninstalling long‑term.
Q: How do I revert Group Policy or registry changes if something goes wrong?
Always export keys or note policy settings before changing. For Group Policy, run gpupdate /force after reverting. For registry, import your exported .reg file or use System Restore to revert.
Q: When should I contact Microsoft Support or IT?
Contact support if logs show persistent errors (Event Viewer codes, DISM/SFC failures), or if your machine is domain‑managed and policies block updates; include logs for faster help.
Conclusion
Most times when Optional updates don’t work the fix is to restart and repair Windows Update services, clear the update cache, and run the built‑in repair tools (DISM/SFC). Follow the steps above to identify the cause, apply the targeted fix, and gather logs if you need to escalate.
