Fix Update History Truncated to Two Months on Windows 11

When you open Windows Update and check your update history, it now shows only the last two months of activity. Older records for driver updates, cumulative updates, and security patches have disappeared from the list. This behavior started after Windows 11 version 24H2, which introduced a two-month rolling retention policy for the update history log. This article explains why the change happened and shows you how to recover and view the full update history beyond the two-month window.

Why Windows 11 Limits Update History to Two Months

Starting with Windows 11 version 24H2, Microsoft changed the update history display to show only the most recent two months of activity. This change was made to improve the performance of the Settings app. The full update log, which can grow to several hundred entries over a year, was causing the Settings page to load slowly on devices with many cumulative and driver updates.

The two-month cutoff is a display-level filter. The underlying database that records every update action still exists on your system. The Windows Update service writes each update event to the Windows Update log file and to the Event Viewer system log. Microsoft chose to apply the filter only to the Settings UI to reduce rendering time. The data is not deleted.

The effect is that when you check Settings > Windows Update > Update history, you see only the last 60 days of updates. Older updates are hidden from view. This can be frustrating if you need to verify that a specific driver or cumulative update was installed months ago. The fix is to access the full history using a different tool.

Three Methods to View the Full Update History on Windows 11

You can bypass the two-month limit using PowerShell, the Event Viewer, or the Windows Update log file. Each method works on Windows 11 version 24H2 and later. Choose the method that matches your comfort level with system tools.

Method 1: Use PowerShell to List All Updates

The PowerShell Get-WUHistory cmdlet retrieves the complete list of updates from the Windows Update database. This method shows every update since the system was first installed or since the database was last reset.

1. Open PowerShell as administrator
   Press the Windows key, type PowerShell, right-click Windows PowerShell, and select Run as administrator. Confirm the User Account Control prompt.
2. Install the PSWindowsUpdate module
   In the PowerShell window, type Install-Module -Name PSWindowsUpdate -Force and press Enter. Type Y if asked to install from an untrusted repository. This module adds the Get-WUHistory command to PowerShell.
3. Retrieve the full update history
   Type Get-WUHistory and press Enter. The command outputs a table with the date, title, and result of every update. Scroll through the list to find older entries. To export the list, use Get-WUHistory | Export-Csv -Path C:\UpdateHistory.csv.

Method 2: Use Event Viewer to See Every Update Event

The Windows Update service logs each update action as an event in the System log. Event Viewer can show these events without any two-month limit. The log retains events until it reaches its maximum size, which is typically 20 MB and can store months or years of data.

1. Open Event Viewer
   Press Windows + R, type eventvwr.msc, and press Enter.
2. Navigate to the System log
   In the left pane, expand Windows Logs and select System.
3. Filter for Windows Update events
   In the right pane, click Filter Current Log. In the Filter tab, type WindowsUpdateClient in the Event sources box and click OK. The log now shows only events from the Windows Update client.
4. Identify update events
   Look for Event ID 19 (install successful), Event ID 20 (install failure), Event ID 24 (update downloaded), and Event ID 43 (update installed). The date column shows when each event occurred. Scroll to the bottom of the list to see the oldest events.

Method 3: Read the Windows Update Log File Directly

Windows Update writes a detailed log file to the Windows directory. This file contains every update action in chronological order. The log is not affected by the two-month display limit.

1. Open the log file
   Press Windows + R, type C:\Windows\WindowsUpdate.log, and press Enter. If the file does not open, it may have been replaced by the newer .etl log format. In that case, use the next step.
2. Use PowerShell to read the .etl log
   Open PowerShell as administrator and type Get-WindowsUpdateLog. This command converts the binary .etl log into a readable text file saved at %USERPROFILE%\Desktop\WindowsUpdate.log. Open that file with Notepad.
3. Search for specific updates
   In Notepad, press Ctrl+F and type the update KB number or a keyword such as “Installation Successful” or “Downloaded.” The log shows a timestamp for each entry, allowing you to find entries older than two months.

What to Do If the Full History Is Still Incomplete

In rare cases, the update database or log may have been cleared or corrupted. This can happen after a system reset, a disk cleanup operation, or a manual deletion of the SoftwareDistribution folder. When the underlying data is gone, no tool can recover it.

“I Ran Get-WUHistory but It Shows No Updates”

If the PSWindowsUpdate module returns an empty list, the update database at C:\Windows\SoftwareDistribution\DataStore may have been cleared. This folder is reset when you run the Windows Update troubleshooter or manually delete the SoftwareDistribution folder. To confirm, check the date of the DataStore.edb file. If the file date is recent, the database was reset. In this case, only future updates will appear in the history.

“Event Viewer Shows No WindowsUpdateClient Events”

If the System log contains no events from the WindowsUpdateClient source, the log may have been overwritten. The System log has a maximum size, and when it fills up, older events are discarded. To prevent this, increase the log size. In Event Viewer, right-click System, select Properties, set Maximum log size to 20480 KB or higher, and select Overwrite events as needed. After increasing the size, future events will be retained longer.

“The WindowsUpdate.log File Is Missing”

Windows 11 version 22H2 and later use the .etl log format by default. The plain text WindowsUpdate.log file is not created unless you run the Get-WindowsUpdateLog PowerShell command. Run that command to generate the log file. If the generated log is empty, the .etl trace session may not have been active. Restart the Windows Update service by typing net stop wuauserv and net start wuauserv in an elevated Command Prompt, then wait for an update check to generate new log entries.

Settings App vs PowerShell vs Event Viewer: Update History Comparison

Item	Settings App	PowerShell Get-WUHistory	Event Viewer System Log
Time range shown	Last 60 days	Entire database history	Until log size limit reached
Data source	Filtered UI from DataStore	Raw DataStore database	System event log
Requires admin rights	No	Yes	Yes for filter
Exportable	No	Yes, to CSV	Yes, to CSV or EVTX
Shows failed updates	Yes	Yes	Yes, with error codes
Shows driver updates	Yes	Yes	Yes

The Settings app is convenient for recent updates but hides older data. PowerShell and Event Viewer give you full access to the complete history. Use PowerShell for a quick list and Event Viewer for detailed error codes.

You can now retrieve the full update history on Windows 11 version 24H2 using PowerShell or Event Viewer. For routine checks, use the Get-WUHistory cmdlet in an elevated PowerShell session. For troubleshooting a specific failed update, filter Event Viewer for WindowsUpdateClient events and note the Event ID and error code. To keep the Event Viewer log from overwriting old data, increase the System log size to 20480 KB in Event Viewer properties.