PC Did That Update Actually Install? Reading Your Update History
You restart, Windows says you are up to date, and you still wonder if last night's update actually installed. Some updates fail quietly and try again later, so the message alone does not settle it.
Check update history, which works like a receipt. It lists each update by name, KB number, date and result, such as Successfully installed or Failed to install. A failed line also shows an error code, and that code is the clue you need next.
The steps below cover Windows 11 and Windows 10 in one place. First you will open the list, then read it line by line, then note the KB number and code from any failed update. From there, you can go straight to the fix for that code.
Part of the Windows Update Problems: Stuck, Failed and Slow Updates Fixed Safely series, the pillar guide for this cluster.
How to open update history in Windows 11 and Windows 10
You can open update history from Settings on either version of Windows, and you do not need to download anything to see it. Press the Windows key and I together to open Settings, or select the Start button and then select Settings. If you use search, type Settings and select it from the results.
On Windows 11, follow these steps in order: 1. Select Windows Update in the list on the left side of Settings. It is usually near the bottom of that list. 2. Select Update history on the right. The page that opens is your update history, and it stays in Settings until you close the window or move to another page.
On Windows 10, follow these steps in order: 1. Select Update and Security in Settings. 2. Select Windows Update in the list on the left. This section may already be open when Update and Security loads. 3. Select View update history on the right. That selection opens your update history page in the same Settings window.
The names differ a little, but the result is the same. Windows 11 labels the last step Update history, and Windows 10 labels it View update history, yet both open the same kind of list in Settings. Leave the page open when you reach it, so you can work through it next without repeating the route. No extra tool, download, or sign-in is needed for this check.
How to read the list like a receipt
The list is not one long stream of updates. Windows groups it under headings, a bit like sections on a receipt, so you can check one kind of update at a time. You may not see every group. That depends on what your PC has received. Start at the top, where the most recent updates are usually listed first, and work down.
Feature updates are the larger Windows version changes. Quality updates are the regular monthly fixes, driver updates are for parts such as your printer or display, and definition updates keep Microsoft Defender up to date. Other updates covers smaller items that do not fit the earlier groups. You read the entries the same way in each group.
Each line works the same way. The name tells you what the update was, the number in brackets starting with KB is its reference number, and the line below or beside it gives the date and the result. If you check lines in that order, name, KB number, date, result, they are much easier to compare. That order works for every group.
There are two results to look for. 'Successfully installed' means that update went in on the date shown, so you can tick it off and move on. 'Failed to install' means it did not go in on that date. For now, just note which result you see. The next step is finding the failed line's details. The same update may appear again later if Windows tries it again.
How to find the failed update, its KB number and its error code
Start with the lines that say Failed to install. Work through the list from the top, which shows the most recent entries first, and pass over the lines that say Successfully installed for now. If there are a lot of entries, check the dates first and start with the date of the restart or message that made you wonder.
Select a failed line to open it, then read the entry in full. Read the whole update name and the date under it, instead of stopping at the first few words, because similar names can cover different updates. The date also tells you whether this is the recent failure you are looking for or an older try.
Inside the entry, look for two pieces of information. The KB number, in brackets after the name, says which update this was. Under or beside the Failed to install line, look for a code that starts with 0x. That code says why the update failed. You need both, because each one answers a different question.
Write down the KB number and the 0x code exactly as they appear, or copy them if your screen lets you. Check each letter and number before you move on, since one wrong character can send you to a different code. If writing is awkward, take a clear photo of the entry with your phone instead. Keep it until you finish looking up the code.
If the same KB number appears on more than one failed line, note the most recent date first. Windows may try the same update again, so an older failure may later be followed by a success for that KB number. Keep the name, KB number, code, and date together as one record for each failed try.
What to do with the KB number and code you found
Start with the 0x code, because it says why the update failed. Type or paste the code exactly as you recorded it into the search box on this site. You can also look for it in the A to Z index or in the Windows update error codes list.
Open the page for that code from the results. Before you follow the steps on that page, use the KB number to confirm you have the right update. Check that the KB number, the update name, and the date match the failed entry in your history.
If they do not match, stop and check what you wrote down. A single wrong digit or letter can send you to a different code, so compare the code on screen with your note, your copy, or your photo before you try again.
If the failed line shows no code at all, search by the KB number instead. Keep the exact update name and the date from that line with the number. That pair helps you pick the right result when the same update appears more than once. Do not guess a code from a similar entry.
If an update is missing, the list is blank or the dates do not match
If you cannot find an update in history, check the main Windows Update page first. An update that is still waiting to install, is paused, or needs a restart appears there. It does not become a finished history entry until the install attempt ends, so its absence from history does not mean it has already failed.
If Windows asks for a restart, restart the computer, then open update history again and look for the new entry. The date may be the day of that restart, which can explain why it does not match the day you first saw the update message. Check the result on that new line before you do anything else.
A blank list, or a list with only a few entries, can follow a fresh Windows setup, a reset, or a major feature update. By itself, it does not prove that an update you had installed before was removed.
If an update was rolled back, history may show it as Failed to install instead of as a completed install. Write down the KB number and the 0x code from that line, and look up the code. Those are still the details that point to the right help.
Conclusion
You do not have to take an up to date message on trust. Update history is the record behind that message, and one line settles the question for a single update. If the line for the date you expected says Successfully installed, that update is in and you can stop checking it.
If the line says Failed to install, you are not back at the start. You already have the KB number and the 0x code from that entry, and those two details point to the one fix that matches it. Look up the code, not a general fix for any failed update.