Start here if your Update history page shows nothing, incomplete entries, or recent updates don’t appear: the most common reason is corrupted or stopped update components — in short, Update history doesn’t work in Windows 10. This problem can be caused by corrupted update files, stopped services, incorrect system time, disk errors, third‑party cleaners, policy restrictions, or permission issues. In this article you’ll learn the eight most common causes and step‑by‑step fixes so you can restore a working Update history page and confirm which updates installed.
Key Takeaway
Resetting the Windows Update components and ensuring the core services (Windows Update, BITS, Cryptographic) are running fixes most cases quickly — run the built‑in Windows Update Troubleshooter, stop the services, rename %windir%\SoftwareDistribution and %windir%\System32\catroot2, then restart the services.
Quick Fix Guide
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| Corrupted Windows Update files (SoftwareDistribution/catroot2) | Rename the folders and restart Windows Update services to rebuild them. |
| Windows Update or related services are stopped/disabled | Start and set Windows Update, BITS, and Cryptographic Services to Automatic. |
| Corrupt system files | Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. |
| Incorrect date/time or time zone | Set correct date/time or enable Set time automatically. |
| Low disk space or disk errors | Free space and run chkdsk /f on the system drive. |
| Third‑party cleanup or security software removed logs | Temporarily disable/uninstall the tool and rebuild update components. |
| Group Policy or Registry blocking update history | Check gpedit.msc and relevant keys; reset to default if restrictive. |
| Permission or user profile issues | Repair profile permissions or create a new user to test. |
Detailed Fixes for “Update history doesn’t work in Windows 10”
Below are step‑by‑step fixes for each reason in the Quick Fix Guide. Follow in order from fastest to more advanced.
1) Corrupted Windows Update files (SoftwareDistribution / catroot2)
Why this causes the problem
- Windows Update stores downloaded updates, logs, and temporary files in %windir%\SoftwareDistribution and certificate data in %windir%\System32\catroot2. Corruption or incomplete writes prevent the Update history UI from reading entries.
How to fix it (step‑by‑step)
- Open Command Prompt as Administrator (right‑click Start > Command Prompt (Admin) or Windows PowerShell (Admin)).
- Stop update services:
- net stop wuauserv
- net stop bits
- net stop cryptsvc
- Rename folders so Windows rebuilds them:
- ren %windir%\SoftwareDistribution SoftwareDistribution.old
- ren %windir%\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.
Notes
- Renaming preserves the old folder if you need data; Windows creates a fresh folder automatically.
- If a service won’t stop, reboot into Safe Mode and repeat.
Why this causes the problem
- The Update history UI reads from services and logs produced by these services. If they’re disabled, history cannot populate.
How to fix it
- Press Windows + R, type services.msc, and press Enter.
- Find and double‑click each service: Windows Update, Background Intelligent Transfer Service (BITS), Cryptographic Services.
- Set Startup type to Automatic (Delayed Start) or Automatic, then click Start if the service is stopped.
- Click OK and close Services.
- Open Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update and run the troubleshooter.
Tip
- Antivirus or system optimization tools can set these services to Disabled; check their settings.
3) Corrupt system files
Why this causes the problem
- Corrupt or missing system files can break the UI that displays update history or the update client itself.
How to fix it
- Open Command Prompt (Admin).
- Run System File Checker:
- sfc /scannow
- If SFC reports it repaired files or finds errors, follow up with DISM:
- DISM /Online /Cleanup-Image /RestoreHealth
- Reboot and recheck Update history.
Notes
- DISM needs an internet connection to fetch healthy components; if offline, provide an installation source with /Source:.
4) Incorrect date/time or time zone
Why this causes the problem
- Update metadata and certificate validations rely on correct time — an incorrect clock can prevent update services from writing proper records or trusting signatures.
How to fix it
- Open Settings > Time & Language > Date & time.
- Turn on Set time automatically and Set time zone automatically, or manually set correct values.
- Click Sync now under Synchronize your clock.
- Restart Windows and check Update history.
Tip
- If on a domain, confirm domain controller time is correct too.
5) Low disk space or disk errors
Why this causes the problem
- If the system drive is low on space, Windows may fail to write update logs or complete database transactions; disk errors can corrupt files Windows needs.
How to fix it
- Open Settings > System > Storage and free space (remove large apps, use Storage Sense).
- Run Command Prompt (Admin): chkdsk C: /f and accept scheduling on next reboot if required.
- Restart to let chkdsk run and fix file system errors.
- After reboot, verify Update history.
Notes
- If using an SSD, disk errors are less common but still possible; check drive health with manufacturer tools.
6) Third‑party security or cleaning software removed logs
Why this causes the problem
- Tools like registry cleaners, system optimizers, or aggressive antivirus may delete update logs, caches, or reset permissions.
How to fix it
- Temporarily disable or uninstall the suspected software.
- Open Settings > Apps > Apps & features, select the program, and Uninstall.
- Rebuild Update components (see Section 1 rename steps) and restart services.
- Recheck Update history.
Tip
- If you need the security tool, whitelist Windows Update folders in its settings rather than uninstalling permanently.
7) Group Policy or Registry settings blocking update history
Why this causes the problem
- On managed or misconfigured systems, Group Policy or registry entries can prevent Windows Update from recording or showing history for privacy or control reasons.
How to fix it
- If you have Windows Pro or Enterprise, open gpedit.msc (press Windows + R, type gpedit.msc, Enter).
- Browse to Computer Configuration > Administrative Templates > Windows Components > Windows Update and look for policies that disable update UI or history (for example, Remove access to use all Windows Update features). Set them to Not Configured if appropriate.
- To check registry keys, open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate; back up keys and delete restrictive entries if you manage the PC.
- Reboot and check Update history.
Warning
- On corporate devices, changes may be enforced by your admin; consult IT before modifying policies.
8) Permission or user profile issues
Why this causes the problem
- The update history UI reads from the system event logs and update database; corrupted user profiles or wrong permissions on folders/registry can block access.
How to fix it
- Test with another account: create a local admin account
- Settings > Accounts > Family & other users > Add someone else to this PC, then set account type to Administrator.
- Log into the new account and open Settings > Update & Security > Windows Update to see if history appears.
- If it works, consider repairing the original profile (backup data, then create a new account and move files) or use System Restore to a date before the issue.
- Check folder permissions:
- Right‑click C:\Windows\SoftwareDistribution, Properties > Security, ensure SYSTEM and Administrators have full control.
- Repair permissions with an elevated command prompt:
- icacls C:\Windows\SoftwareDistribution /grant Administrators:F /T
Note
- Always back up the registry and user data before major repairs.
When to consider an in‑place repair or contact support
If none of the above fixes work, consider:
- Running an in‑place repair (Windows 10 repair install) which preserves files and apps while replacing system components — use the latest Windows 10 ISO and run setup.exe from inside Windows, then choose Upgrade this PC now and Keep personal files and apps.
- Contact Microsoft Support or your IT department if the device is managed: there may be server‑side policies or WSUS issues causing missing history.
Tip
- Before an in‑place repair, create a full backup (System Image or File History) so you can recover if needed.
FAQ
Why does Windows Update show “No updates have been installed” even after installing updates?
If the Update history is empty but updates installed, logs may have been deleted or the SoftwareDistribution folder was reset. Rebuild the update store (rename %windir%\SoftwareDistribution) and use Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational to confirm installs.
Can I safely delete SoftwareDistribution to fix history problems?
Yes — renaming or deleting %windir%\SoftwareDistribution forces Windows to recreate it. Deleting won’t uninstall already installed updates, but you will lose the Downloaded and DataStore entries temporarily.
Will clearing Update history remove installed updates?
No. Clearing the history only removes the records shown in Settings; installed updates remain applied to Windows.
How can I export my Update history?
Use Event Viewer to export relevant logs or run Get-WindowsUpdateLog in PowerShell (Admin) to generate a readable WindowsUpdate.log file you can save and share.
How to prevent this from happening again?
- Keep sufficient free disk space and avoid aggressive cleaners.
- Let Windows update automatically and don’t disable update services.
- Regularly run sfc /scannow and keep system time synchronized.
- Maintain a recent System Restore point or image backup.
Conclusion
Most cases where Update history doesn’t work in Windows 10 are caused by corrupted update components, stopped services, or permissions issues. Start with the Windows Update troubleshooter, reset the SoftwareDistribution and catroot2 folders, ensure core services run, and run SFC/DISM — these steps resolve the majority of problems.
