List all windows updates applied

List all windows updates applied

Notice: This tool is very old and it’s not updated anymore. There is a new tool that replaces this old tool:
Windows Updates History Viewer

Description

System Requirements

Versions History

  • Version 1.33:
    • Fixed issue: The ‘Installation Date’ column displayed the time in GMT instead of local time.
  • Version 1.32:
    • Fixed the URLs on Microsoft Web site to the current format: http://support.microsoft.com/kb/xxxxxx
    • Fixed to display the ‘Last Modified Time’ values according to daylight saving time settings.
  • Version 1.31:
    • Added ‘Mark Odd/Even Rows’ option, under the View menu. When it’s turned on, the odd and even rows are displayed in different color, to make it easier to read a single line.
    • Added ‘Add Header Line To CSV/Tab-Delimited File’ option. When this option is turned on, the column names are added as the first line when you export to csv or tab-delimited file.
  • Version 1.30:
    • Added partial support for Windows 7/Vista/2008. The windows updates information is displayed in the upper pane, but there is no installed files information in the lower pane. Also on these version of Windows, you cannot view the information on remote computer.
    • Added ‘Long Description’ column, for Windows 7/Vista/2008 only.
  • Version 1.23:
    • Fixed bug: The dates displayed in system locale, instead of user locale.
  • Version 1.22:
    • Added support for saving as comma-delimited file.
    • Fixed bug: The main window lost the focus when the user switched to another application and then returned back to WinUpdatesList.
  • Version 1.21:
    • Fixed bug: Crash when running wul.exe with command-line parameters.
  • Version 1.20:
    • Changed Operating System column to Application.
    • Added filter by application (Windows, .NET, and others)
    • Added ‘Last Modified Time’ column.
    • Fixed Web link for .NET Updates.
    • Configuration is now saved to cfg file instead of the Registry.
    • Updates with extra sub-key level (in the Registry) are now displayed properly.
  • Version 1.13: A tooltip is now displayed when a string in a column is longer than the column length.
  • Version 1.12: Added support for Windows XP styles.
  • Version 1.11:
    • On Windows 2000/XP: new command-line options that allows you to connect another operating system on local or remote computer.
    • Computer name is now added to XML and HTML files.
  • Version 1.10:
    • Added support for Windows 98/ME
    • ‘Open Web Link’ now opens each link in a new browser window.
    • Command-Line support.
  • Version 1.00 — First Release.

Using WinUpdatesList

The main window of WinUpdatesList contains 2 panes: The upper pane displays the list of all updates installed on your computer. When you select an hotfix in the upper pane, the lower pane display the list of files installed with the selected hotfix.
If you want to get more information about a specific update, select the desired item in the upper pane, and then from the File menu (or from the popup menu) choose ‘Open Web Link’. This option opens your browser with a Web page in Microsoft site that provides information about the selected Windows update.

Notice: Some operations, like saving to file or copying to the clipboard, are performed on the pane that currently has the focus. For example: If you press Ctrl+C while the lower pane is focused, the selected files list will be copied to the clipboard. If the upper pane has the focus, the selected updates in the upper pane will be copied.

Connecting to another operating system (Windows 2000/XP only)

The second parameter specifies the Windows folder of the operating system.
Be aware that when you use this option, WinUpdatesList loads the Registry of the other operating system as a new hive under HKEY_LOCAL_MACHINE, and than unloads it after you exit from WinUpdatesList.

Windows 10 update history

Windows 10, version 1909 and Windows Server, version 1909

Updates for Windows 10, version 1909 and Windows Server, version 1909

Windows 10 is a service, which means it gets better through periodic software updates.

The great news is you usually don’t have to do anything! If you have enabled automatic updates, new updates will automatically download and install whenever they’re available, so you don’t have to think about it.

On the left side of this page, you’ll find a list of all the updates released for this version of Windows. You can also find more information about releases and any known issues. Installing the most recent update ensures that you also get any previous updates you might have missed, including any important security fixes.

For more information about the update and how to get it, see:

What’s new for Windows 10, version 1909 and Windows 10, version 1903 release notes

Windows 10, versions 1903 and 1909 share a common core operating system and an identical set of system files. As a result, the new features in Windows 10, version 1909 were included in the recent monthly quality update for Windows 10, version 1903 (released October 8, 2019), but are currently in a dormant state. These new features will remain dormant until they are turned on using an enablement package, which is a small, quick-to-install “master switch” that simply activates the Windows 10, version 1909 features.

Читайте также:  Как узнать свой внешний ip kali linux

To reflect this change, the release notes for Windows 10, version 1903 and Windows 10, version 1909 will share an update history page. Each release page will contain a list of addressed issues for both 1903 and 1909 versions. Note that the 1909 version will always contain the fixes for 1903; however, 1903 will not contain the fixes for 1909. This page will provide you with the build numbers for both 1909 and 1903 versions so that it will be easier for support to assist you if you encounter issues.

For more details about the enablement package and how to get the feature update, see the Windows 10, version 1909 delivery options blog.

Current status of Windows 10, version 1909 and Windows Server, version 1909

For the most up-to-date information about Known Issues for Windows and Windows Server, please go to the Windows release health dashboard.

Notes and messages

General

IMPORTANT Release notes are changing! To learn about the new URL, metadata updates, and more, see What’s next for Windows release notes.

IMPORTANT Starting in July 2020, we will resume non-security releases for Windows 10 and Windows Server, version 1809 and later. There is no change to the cumulative monthly security updates (also referred to as the «B» release or Update Tuesday release). For more information, see the blog post Resuming optional Windows 10 and Windows Server non-security monthly updates.

IMPORTANT Starting in July 2020, all Windows Updates will disable the RemoteFX vGPU feature because of a security vulnerability. For more information about the vulnerability, seeCVE-2020-1036 and KB4570006. After you install this update, attempts to start virtual machines (VM) that have RemoteFX vGPU enabled will fail, and messages such as the following will appear:

If you re-enable RemoteFX vGPU, a message similar to the following will appear:

“The virtual machine cannot be started because all the RemoteFX-capable GPUs are disabled in Hyper-V Manager.”

“The virtual machine cannot be started because the server has insufficient GPU resources.”

«We no longer support the RemoteFX 3D video adapter. If you are still using this adapter, you may become vulnerable to security risk. Learn more (https://go.microsoft.com/fwlink/?linkid=2131976)”

What’s new for Windows 10, version 1909 and Windows 10, version 1903 release notes

Windows 10, versions 1903 and 1909 share a common core operating system and an identical set of system files. As a result, the new features in Windows 10, version 1909 were included in the recent monthly quality update for Windows 10, version 1903 (released October 8, 2019), but are currently in a dormant state. These new features will remain dormant until they are turned on using an enablement package, which is a small, quick-to-install “master switch” that simply activates the Windows 10, version 1909 features.

To reflect this change, the release notes for Windows 10, version 1903 and Windows 10, version 1909 will share an update history page. Each release page will contain a list of addressed issues for both 1903 and 1909 versions. Note that the 1909 version will always contain the fixes for 1903; however, 1903 will not contain the fixes for 1909. This page will provide you with the build numbers for both 1909 and 1903 versions so that it will be easier for support to assist you if you encounter issues.

For more details about the enablement package and how to get the feature update, see the Windows 10, version 1909 delivery options blog.

Troubleshooting

If you have questions or need help activating or troubleshooting Windows, see our help topics below:

For information about how to update, see Update Windows 10.

If you have questions about manually installing or removing an update, see Windows Update: FAQ.

Getting an error message when updating? See Troubleshoot problems updating Windows 10.

If you need to activate Windows, see Activation in Windows 10. If you’re having trouble with activation, see Get help with Windows activation errors.

To get the latest major update to Windows 10, see Get the Windows 10 November 2019 Update.

Windows 10 update history

Windows 10, version 1903 and Windows Server, version 1903

Updates for Windows 10, version 1903 and Windows Server, version 1903

Windows 10 is a service, which means it gets better through periodic software updates.

The great news is you usually don’t have to do anything! If you have enabled automatic updates, new updates will automatically download and install whenever they’re available, so you don’t have to think about it.

On the left side of this page, you’ll find a list of all the updates released for this version of Windows. You can also find more information about releases and any known issues. Installing the most recent update ensures that you also get any previous updates you might have missed, including any important security fixes.

Current status of Windows 10, version 1903 and Windows Server, version 1903

For the most up-to-date information about Known Issues for Windows and Windows Server, please go to the Windows release health dashboard.

Читайте также:  Утилита для пользователя windows

Notes and messages

General

IMPORTANT Release notes are changing! To learn about the new URL, metadata updates, and more, see What’s next for Windows release notes.

IMPORTANT Starting in July 2020, we will resume non-security releases for Windows 10 and Windows Server, version 1809 and later. There is no change to the cumulative monthly security updates (also referred to as the «B» release or Update Tuesday release). For more information, see the blog post Resuming optional Windows 10 and Windows Server non-security monthly updates.

IMPORTANT Starting in July 2020, all Windows Updates will disable the RemoteFX vGPU feature because of a security vulnerability. For more information about the vulnerability, seeCVE-2020-1036 and KB4570006. After you install this update, attempts to start virtual machines (VM) that have RemoteFX vGPU enabled will fail, and messages such as the following will appear:

If you re-enable RemoteFX vGPU, a message similar to the following will appear:

“The virtual machine cannot be started because all the RemoteFX-capable GPUs are disabled in Hyper-V Manager.”

“The virtual machine cannot be started because the server has insufficient GPU resources.”

«We no longer support the RemoteFX 3D video adapter. If you are still using this adapter, you may become vulnerable to security risk. Learn more (https://go.microsoft.com/fwlink/?linkid=2131976)”

What’s new for Windows 10, version 1909 and Windows 10, version 1903 release notes

Windows 10, versions 1903 and 1909 share a common core operating system and an identical set of system files. As a result, the new features in Windows 10, version 1909 were included in the recent monthly quality update for Windows 10, version 1903 (released October 8, 2019), but are currently in a dormant state. These new features will remain dormant until they are turned on using an enablement package, which is a small, quick-to-install “master switch” that simply activates the Windows 10, version 1909 features.

To reflect this change, the release notes for Windows 10, version 1903 and Windows 10, version 1909 will share an update history page. Each release page will contain a list of addressed issues for both 1903 and 1909 versions. Note that the 1909 version will always contain the fixes for 1903; however, 1903 will not contain the fixes for 1909. This page will provide you with the build numbers for both 1909 and 1903 versions so that it will be easier for support to assist you if you encounter issues.

For more details about the enablement package and how to get the feature update, see the Windows 10, version 1909 delivery options blog.

End of servicing

IMPORTANT Windows 10, version 1903 will reach end of servicing on December 8, 2020. To continue receiving security and quality updates, Microsoft recommends that you update to the latest version of Windows 10. If you want to update to Windows 10, version 1909, you must use the Enablement Package KB4517245(EKB). Using the EKB makes updating faster and easier and requires a single restart. For more information, see Windows 10, version 1909 delivery options.

Troubleshooting

If you have questions or need help activating or troubleshooting Windows, see our help topics below:

For information about how to update, see Update Windows 10.

If you have questions about manually installing or removing an update, see Windows Update: FAQ.

Getting an error message when updating? See Troubleshoot problems updating Windows 10.

If you need to activate Windows, see Activation in Windows 10. If you’re having trouble with activation, see Get help with Windows activation errors.

To get the latest major update to Windows 10, see Get the Windows 10 October 2018 Update.

List all windows updates applied

Get-InstalledWindowsUpdates uses Windows Management Instrumentation (WMI, with a command » Get-WmiObject -Class Win32_QuickFixEngineering » (Method 1)) to retrieve a list of some HotFixIDs installed on a local machine and displays the results in console. The Windows Management Instrumentation Command-Line Utility ( WMIC.exe with the query path of win32_quickfixengineering (Method 2)) is then used to write a secondary CSV-file ( partial_hotfix_list.csv ) to $path – this secondary CSV-file populated by WMIC.exe contains about the same partial results as which were obtained by using the previous Method 1.

Finally, Get-InstalledWindowsUpdates uses Windows Update Agent (WUA) API (Method 3) to retrieve a third – comprehensive – list of all the installed and uninstalled Windows updates, and displays those results in a pop-up window and writes them to a CSV-file ( installed_windows_updates.csv ). This script is based on Stéphane van Gulick’s PowerShell function «Get-WindowsUpdates».

Homepage: https://github.com/auberginehill/get-installed-windows-updates
Short URL: http://tinyurl.com/gtcktwy Version: 1.3 Sources: Emojis: Emoji Table Microsoft TechNet: How to List All of the Windows and Software Updates Applied to a Computer ScriptingGuy1: How Can I Tell Which Service Packs Have Been Installed on a Computer? Anna Wang: Cannot index into a null array Stéphane van Gulick: Get-WindowsUpdates Downloads: For instance Get-InstalledWindowsUpdates.ps1. Or everything as a .zip-file.

➡️
  • Displays a partial list of installed HotFixIDs in console and a list of all installed Windows updates in a pop-up window » $windows_updates_sorted_selection » ( Out-GridView ). Also writes two CSV-files at $path .

A pop-up window ( Out-GridView ):

Name Description
$windows_updates_sorted_selection Displays a list of installed Windows updates

And also two CSV-files at $path .

Path Type Name
$env:temp\partial_hotfix_list.csv CSV-file partial_hotfix_list.csv
$env:temp\installed_windows_updates.csv CSV-file installed_windows_updates.csv
⚠️
  • Please note that the files are created in a directory, which is specified with the $path variable (at line 10).

The $env:temp variable points to the current temp folder. The default value of the $env:temp variable is C:\Users\ \AppData\Local\Temp (i.e. each user account has their own separate temp folder at path %USERPROFILE%\AppData\Local\Temp ). To see the current temp path, for instance a command

may be used at the PowerShell prompt window [PS>] . To change the temp folder for instance to C:\Temp , please, for example, follow the instructions at Temporary Files Folder — Change Location in Windows, which in essence are something along the lines:

  1. Right click Computer icon and select Properties (or select Start → Control Panel → System. On Windows 10 this instance may also be found by right clicking Start and selecting Control Panel → System. or by pressing [Win-key] + X and selecting Control Panel → System). On the window with basic information about the computer.
  2. Click on Advanced system settings on the left panel and select Advanced tab on the «System Properties» pop-up window.
  3. Click on the button near the bottom labeled Environment Variables.
  4. In the topmost section, which lists the User variables, both TMP and TEMP may be seen. Each different login account is assigned its own temporary locations. These values can be changed by double clicking a value or by highlighting a value and selecting Edit. The specified path will be used by Windows and many other programs for temporary files. It’s advisable to set the same value (a directory path) for both TMP and TEMP.
  5. Any running programs need to be restarted for the new values to take effect. In fact, probably Windows itself needs to be restarted for it to begin using the new values for its own temporary files.
📖 To open this code in Windows PowerShell, for instance:

./Get-InstalledWindowsUpdates
Runs the script. Please notice to insert ./ or .\ before the script name.

help ./Get-InstalledWindowsUpdates -Full
Displays the help file.

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine
This command is altering the Windows PowerShell rights to enable script execution in the default ( LocalMachine ) scope, and defines the conditions under which Windows PowerShell loads configuration files and runs scripts in general. In Windows Vista and later versions of Windows, for running commands that change the execution policy of the LocalMachine scope, Windows PowerShell has to be run with elevated rights (Run as Administrator). The default policy of the default ( LocalMachine ) scope is » Restricted «, and a command » Set-ExecutionPolicy Restricted » will «undo» the changes made with the original example above (had the policy not been changed before. ). Execution policies for the local computer ( LocalMachine ) and for the current user ( CurrentUser ) are stored in the registry (at for instance the HKLM:\Software\Policies\Microsoft\Windows\PowerShell\ExecutionPolicy key), and remain effective until they are changed again. The execution policy for a particular session ( Process ) is stored only in memory, and is discarded when the session is closed.

    Restricted Does not load configuration files or run scripts, but permits individual commands. Restricted is the default execution policy.
    AllSigned Scripts can run. Requires that all scripts and configuration files be signed by a trusted publisher, including the scripts that have been written on the local computer. Risks running signed, but malicious, scripts.
    RemoteSigned Requires a digital signature from a trusted publisher on scripts and configuration files that are downloaded from the Internet (including e-mail and instant messaging programs). Does not require digital signatures on scripts that have been written on the local computer. Permits running unsigned scripts that are downloaded from the Internet, if the scripts are unblocked by using the Unblock-File cmdlet. Risks running unsigned scripts from sources other than the Internet and signed, but malicious, scripts.
    Unrestricted Loads all configuration files and runs all scripts. Warns the user before running scripts and configuration files that are downloaded from the Internet. Not only risks, but actually permits, eventually, running any unsigned scripts from any source. Risks running malicious scripts.
    Bypass Nothing is blocked and there are no warnings or prompts. Not only risks, but actually permits running any unsigned scripts from any source. Risks running malicious scripts.
    Undefined Removes the currently assigned execution policy from the current scope. If the execution policy in all scopes is set to Undefined , the effective execution policy is Restricted , which is the default execution policy. This parameter will not alter or remove the («master») execution policy that is set with a Group Policy setting.
    Notes:
    • Please note that the Group Policy setting » Turn on Script Execution » overrides the execution policies set in Windows PowerShell in all scopes. To find this («master») setting, please, for example, open the Local Group Policy Editor ( gpedit.msc ) and navigate to Computer Configuration → Administrative Templates → Windows Components → Windows PowerShell.