Note: The update Install Time shown by DISM may be in GMT.

Method 4: Run the KB update installer (.msu) file again.

Running the KB setup .msu again will tell you if the update has been already installed. Here is how to obtain the standalone installer from Microsoft Update Catalog and run the .msu setup file. Note that this method works for Windows update standalone installers .msu only. That is, this method doesn’t apply if you have the .cab version.

1. Visit the Windows Update Catalog
2. Download the update package ( .msu ) by mentioning the KB number.
3. Double-click the .msu file to run the setup. The Windows Update Standalone Installer (WUSA) searches for updates on your computer and determines if the update is already installed or not.

If it’s already installed, it shows the message saying “(KBnnnnnn) is already installed on this computer.”

Method 5: Using WinUpdatesList or WinUpdatesView utility from NirSoft

The WinUpdatesList utility ( wul.exe ) from Nirsoft displays the list of all Windows updates, including Service Packs and Hotfixes installed on your local computer. You can copy the list of updates to the clipboard, or save it to text/HTML/XML file in a single click. The following fields are shown for each update listed. We’ve covered WinUpdatesList in the article How to Print Your Windows Update History By Exporting to Text or HTML File?.

Note: The WinUpdatesList utility, however, did not list the Servicing Stack Update KB4470788 on my computer. Hope this tool works well in your case.

WinUpdatesView (Windows Updates History Viewer)

WinUpdatesView is a simple tool from Nirsoft that displays the history of Windows updates on your system. WinUpdatesView can load the Windows updates history from your local system, using API, and it can also read and parse the Windows updates database file ( DataStore.edb ) from an external drive or from a remote computer on your network.

Method 6: Using WMI command-line

From an admin Command Prompt, run:

It shows the list of updates installed along with the date of installation and other details.

Or Export to HTML file, using this syntax:

Or to list a specific update, run:

Alternately, you can run the command Get-Hotfix from a PowerShell window to get the same results.

You can sort the table by the InstalledOn column in descending order by running this command:

PowerShell’s Get-HotFix cmdlet also uses the WMI’s Win32_QuickFixEngineering (QFE) class as the WMIC CLI tool above. The output is exactly the same.

The systeminfo command from a Command Prompt window also lists the hotfixes installed. It again uses the WMI QFE class to query the list of hotfixes.

Method 7: Check the Windows Update CBS Registry Entries

For each update installed, a corresponding Component Based Servicing package registry entry is created. Using the Registry Editor, you can check whether a Windows update has been installed on your computer.

1. Start the Registry Editor ( regedit.exe )
2. Go to the following registry key:
3. Use the Find option under the Edit menu, and search for the key having the text 4470788 (to find KB4470788 related entries.)

If the key exists, you’re taken to the branch. In my case, as the update was already installed, the Find option led me to this key:
In the right-pane, check the value data for “CurrentState”. If the value data reads 0x00000070 (112) , it means that the update was successfully installed.

Here is the list of possible CurrentState registry values and their meaning:

Determine the install date & time of an update using registry

Each CBS Package key has two values namely InstallTimeLow & InstallTimeHigh . These keys, when decoded will show you the date and time the update was installed. However, we have a shortcut way to find the exact installation date and time the update was installed on your computer.

The trick is to export the Package branch to a .txt file (instead of .reg format) and read the timestamp mentioned in the file. We’ll find the installation date and time of update KB4470788 in this example.

1. In the Registry Editor, select the following ( KB4470788 ) key:
2. Right-click on the package key and click Export.
3. In this example, we’ll export the Package_1_for_KB4470788

17763.164.1.1 branch.

The last write time denotes the date and time the registry entry was created.

As you can see, the last write time in this example matches with the date and time we determined in Method 2 using “Programs and Features”.

That’s it! Hope this article helped you check if a specific Windows Update (KBnnnnnn) has been applied to your system or not.

Find all windows updates installed

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Is there a simple command that can be used to check the installed Windows Updates from the Command-prompt?

e.g. to check if MS10-066 is installed on the server from the Windows Command-prompt

Answers

You’ll need the corresponding KB number (982802) or you’ll need to know if it was part of a rollup or service pack.

wmic qfe list
— Mike Burr

All replies

You’ll need the corresponding KB number (982802) or you’ll need to know if it was part of a rollup or service pack.

wmic qfe list
— Mike Burr

This worked for me:

wmic qfe | find “982802”

Another option if you want to use PowerShell:

To search for a specific hotfix

I share my solution here, which list every updates ( some post here only list few updates ) and dump to a file

$Session = New-Object -ComObject «Microsoft.Update.Session»
$Searcher = $Session.CreateUpdateSearcher()
$FormatEnumerationLimit=-1
$historyCount = $Searcher.GetTotalHistoryCount()

$Searcher.QueryHistory(0, $historyCount) | Select-Object Title, Description, Date,

>>> -ExpandProperty Title > C:/Maintenance/ListOfWindowsUpdates.txt

Thank you for sharing this script. I’m starting to use saltstack for automated configuration management and their Windows Updates module has been unable to find a specific KB that I was interested in verifying was installed on computers. I’ve been unable to track down why the module doesn’t display this KB (and probably others). The Windows GUI shows it installed, however, but the get-hotfix command does not. Your script DOES show it, though.

KB4012215 is the KB in question.

Are you able to explain to me what part of your script is exposing this otherwise hidden KB? That might help me in figuring out how to filter it in with saltstack.