Windows Update Msu Files
- Msu File
- Windows Update Msu Files Download
- Download Windows Update Msu Files
- Install Windows Update Msu Files Silently
Nov 20, 2012 Here's How:1. Open the Control Panel (icons view), and click on the Windows Update icon. If the Windows Update is Installed on Windows 7A) Click on the View update history link. (see screenshot below) B) Select and right click on the Windows Update (ex: KB2484033) that you want to download the MSU file for, and click on View details. (see screenshot below).
-->Applies to: Windows 10
- Jul 02, 2019 Update file used by Windows Update, an application included with Windows Vista, Windows 7, and Windows Server; contains updates for applications and files; installed by the Windows Update Stand-alone Installer (Wusa.exe), which is run by Windows Update automatically (the user generally does not need to manually install MSU files).
- For those customers updating to Windows 8.1 Update manually using the available from MSDN and TechNet will notice that this spring update is a collection of.msu files needed to be installed in a certain order and one-by-one, instead of a single we’re used to see with Service Packs.
The following table describes the log files created by Windows Update.
| Log file | Location | Description | When to Use |
|---|---|---|---|
| windowsupdate.log | C:WindowsLogsWindowsUpdate | Starting in Windows 8.1 and continuing in Windows 10, Windows Update client uses Event Tracing for Windows (ETW) to generate diagnostic logs. | If you receive an error message when you run Windows Update (WU), you can use the information that is included in the Windowsupdate.log log file to troubleshoot the issue. |
| UpdateSessionOrchestration.etl | C:ProgramDataUSOSharedLogs | Starting Windows 10, the Update Orchestrator is responsible for sequence of downloading and installing various update types from Windows Update. And the events are logged to these etl files. | When you see that the updates are available but download is not getting triggered. When Updates are downloaded but installation is not triggered. When Updates are installed but reboot is not triggered. |
| NotificationUxBroker.etl | C:ProgramDataUSOSharedLogs | Starting Windows 10, the notification toast or the banner is triggered by this NotificationUxBroker.exe . And the logs to check its working is this etl. | When you want to check whether the Notification was triggered or not for reboot or update availability etc. |
| CBS.log | %systemroot%LogsCBS | This logs provides insight on the update installation part in the servicing stack. | To troubleshoot the issues related to WU installation. |
Generating WindowsUpdate.log
To merge and convert WU trace files (.etl files) into a single readable WindowsUpdate.log file, see Get-WindowsUpdateLog.
Note
When you run the Get-WindowsUpdateLog cmdlet, an copy of WindowsUpdate.log file is created as a static log file. It does not update as the old WindowsUpate.log unless you run Get-WindowsUpdateLog again.
Windows Update log components
The WU engine has different component names. The following are some of the most common components that appear in the WindowsUpdate.log file:
- AGENT- Windows Update agent
- AU - Automatic Updates is performing this task
- AUCLNT- Interaction between AU and the logged-on user
- CDM- Device Manager
- CMPRESS- Compression agent
- COMAPI- Windows Update API
- DRIVER- Device driver information
- DTASTOR- Handles database transactions
- EEHNDLER- Expression handler that's used to evaluate update applicability
- HANDLER- Manages the update installers
- MISC- General service information
- OFFLSNC- Detects available updates without network connection
- PARSER- Parses expression information
- PT- Synchronizes updates information to the local datastore
- REPORT- Collects reporting information
- SERVICE- Startup/shutdown of the Automatic Updates service
- SETUP- Installs new versions of the Windows Update client when it is available
- SHUTDWN- Install at shutdown feature
- WUREDIR- The Windows Update redirector files
- WUWEB- The Windows Update ActiveX control
- ProtocolTalker - Client-server sync
- DownloadManager - Creates and monitors payload downloads
- Handler, Setup - Installer handlers (CBS, and so on)
- EEHandler - Evaluating update applicability rules
- DataStore - Caching update data locally
- IdleTimer - Tracking active calls, stopping a service
Note
Many component log messages are invaluable if you are looking for problems in that specific area. However, they can be useless if you don't filter to exclude irrelevant components so that you can focus on what’s important.
Msu File
Windows Update log structure
The Windows update log structure is separated into four main identities:
- Time Stamps
- Process ID and Thread ID
- Component Name
- Update Identifiers
- Update ID and Revision Number
- Revision ID
- Local ID
- Inconsistent terminology
The WindowsUpdate.log structure is discussed in the following sections.
Time stamps
The time stamp indicates the time at which the logging occurs.
- Messages are usually in chronological order, but there may be exceptions.
- A pause during a sync can indicate a network problem, even if the scan succeeds.
- A long pause near the end of a scan can indicate a supersedence chain issue.
Process ID and thread ID
The Process IDs and Thread IDs are random, and they can vary from log to log and even from service session to service session within the same log.
- The first four hex digits are the process ID.
- The next four hex digits are the thread ID.
- Each component, such as the USO, WU engine, COM API callers, and WU installer handlers, has its own process ID.
Component name
Search for and identify the components that are associated with the IDs. Different parts of the WU engine have different component names. Some of them are as follows:
- ProtocolTalker - Client-server sync
- DownloadManager - Creates and monitors payload downloads
- Handler, Setup - Installer handlers (CBS, etc.)
- EEHandler - Evaluating update applicability rules
- DataStore - Caching update data locally
- IdleTimer - Tracking active calls, stopping service
Update identifiers
Update ID and revision number
There are different identifiers for the same update in different contexts. It’s important to know the identifier schemes.
- Update ID: A GUID (indicated in the previous screen shot) that's assigned to a given update at publication time
- Revision number: A number incremented every time that a given update (that has a given update ID) is modified and republished on a service
- Revision numbers are reused from one update to another (not a unique identifier).
- The update ID and revision number are often shown together as '{GUID}.revision.'
Revision ID
- A Revision ID (do no confuse this with “revision number”) is a serial number that's issued when an update is initially published or revised on a given service.
- An existing update that’s revised keeps the same update ID (GUID), has its revision number incremented (for example, from 100 to 101), but gets a completely new revision ID that is not related to the previous ID.
- Revision IDs are unique on a given update source, but not across multiple sources.
- The same update revision may have completely different revision IDs on WU and WSUS.
- The same revision ID may represent different updates on WU and WSUS.
Local ID
- Local ID is a serial number issued when an update is received from a service by a given WU client
- Usually seen in debug logs, especially involving the local cache for update info (Datastore)
- Different client PCs will assign different Local IDs to the same update
- You can find the local IDs that a client is using by getting the client’s %WINDIR%SoftwareDistributionDatastoreDatastore.edb file
Inconsistent terminology
Sometimes the logs use terms inconsistently. For example, the InstalledNonLeafUpdateIDs list actually contains revision IDs, not update IDs.
Recognize IDs by form and context:
- GUIDs are update IDs
- Small integers that appear alongside an update ID are revision numbers
- Large integers are typically revision IDs
- Small integers (especially in Datastore) can be local IDs
Windows Setup log files analysis using SetupDiag tool
SetupDiag is a diagnostic tool that can be used for analysis of logs related to installation of Windows Updates. For detailed information, see SetupDiag.
-->Use DISM with Windows cabinet (.cab) or Windows Update Stand-alone Installer (.msu) files to install or remove updates, service packs, language packs, and to enable or disable Windows features. Features are optional components for the core operating system.
Syntax
The following operating system package-servicing options are available for an offline image:
The following operating system package-servicing options are available for a running operating system:
Operating system package-servicing options
This section describes how you can use each operating system package-servicing option. These options are not case sensitive.
/Get-Help /?
When used immediately after a package-servicing command-line option, information about the option and the arguments is displayed.
Additional topics might become available when an image is specified.
Syntax:
Examples:
/Get-Packages
Windows Update Msu Files Download
Displays basic information about all packages in the image. Use the /Format:Table or /Format:List argument to display the output as a table or a list.
Syntax:
Examples:
/Get-PackageInfo
Displays detailed information about a package provided as a .cab file. Only .cab files can be specified. You cannot use this command to obtain package information for .msu files. /PackagePath can point to either a .cab file or a folder.
You can use the /Get-Packages option to find the name of the package in the image, or you can specify the path to the .cab file. The path to the .cab file should point to the original source of the package, not to where the file is installed on the offline image.
Syntax:
Examples:
/Add-Package
Installs a specified .cab or .msu package in the image. An .msu package is supported only when the target image is offline, either mounted or applied.
Multiple packages can be added on one command line. The applicability of each package will be checked. If the package cannot be applied to the specified image, you will receive an error message. Use the /IgnoreCheck argument if you want the command to process without checking the applicability of each package.
Use the /PreventPending option to skip the installation of the package if the package or Windows image has pending online actions. (Introduced in Windows 8/Windows PE 4.0).
/PackagePath can point to:
Hp pavilion dv9000 video drivers windows 7. Download freely the HP Pavilion dv9000 drivers software for Windows 7/8, 32-bit or 64-bit systems, in order to achieve better system optimization and derive pleasure from added computing features and capabilities.
A single .cab or .msu file.
A folder that contains a single expanded .cab file.
A folder that contains a single .msu file.
A folder that contains multiple .cab or .msu files.
Notes
- If /PackagePath points to a folder that contains a .cab or .msu files at its root, any subfolders will also be recursively checked for .cab and .msu files.
- /Add-Package doesn't run a full check for a package's applicability and dependencies. If you're adding a package with dependencies, make sure that all dependencies are installed when you add the package.
Syntax:
Examples:
/Remove-Package
Removes a specified .cab file package from the image. Only .cab files can be specified. You cannot use this command to remove .msu files.
Note Using this command to remove a package from an offline image will not reduce the image size.
You can use the /PackagePath option to point to the original source of the package, specify the path to the CAB file, or you can specify the package by name as it is listed in the image. Use the /Get-Packages option to find the name of the package in the image.
Syntax:
Examples:
/Get-Features
Displays basic information about all features (operating system components that include optional Windows foundation features) in a package. You can use the /Get-Features option to find the name of the package in the image, or you can specify the path to the original source of the package. If you do not specify a package name or path, all features in the image will be listed. /PackagePath can point to either a .cab file or a folder.
Feature names are case sensitive if you are servicing a Windows image other than Windows 8.
Use the /Format:Table or /Format:List argument to display the output as a table or a list.
Syntax:
Download Windows Update Msu Files
Examples:
/Get-FeatureInfo
Displays detailed information about a feature. You must use /FeatureName. Feature names are case sensitive if you are servicing a Windows image other than Windows 10 or Windows 8.x. You can use the /Get-Features option to find the name of the feature in the image.
/PackageName and /PackagePath are optional and can be used to find a specific feature in a package.
Syntax:
Examples:
/Enable-Feature
Enables or updates the specified feature in the image. You must use the /FeatureName option. Feature names are case sensitive if you are servicing a Windows image other than Windows 8. Use the /Get-Features option to find the name of the feature in the image.
You can specify the /FeatureName option multiple times in one command line for features that share the same parent package.
You do not have to specify the package name using the /PackageName option if the package is a Windows Foundation Package. Otherwise, use /PackageName to specify the parent package of the feature.
You can restore and enable a feature that has previously been removed from the image. Use the /Source argument to specify the location of the files that are required to restore the feature. The source of the files can by the Windows folder in a mounted image, for example c:testmountWindows. You can also use a Windows side-by-side folder as the source of the files, for example z:sourcesSxS.
If you specify multiple /Source arguments, the files are gathered from the first location where they are found and the rest of the locations are ignored. If you do not specify a /Source for a feature that has been removed, the default location in the registry is used or, for online images, Windows Update (WU) is used.
Use /LimitAccess to prevent DISM from contacting WU for online images.
Use /All to enable all parent features of the specified feature.
The /Source, /LimitAccess, and /All arguments can be used with Windows 10, Windows 8.x, and Windows PE images above 4.0.
Syntax:
Examples:
/Disable-Feature
Disables the specified feature in the image. You must use the /FeatureName option. Feature names are case sensitive if you are servicing a Windows image other than Windows 8. Use the /Get-Features option to find the name of the feature in the image.
You can specify /FeatureName multiple times in one command line for features in the same parent package.
You do not have to specify the package name using the /PackageName option if it the package is a Windows Foundation Package. Otherwise, use /PackageName to specify the parent package of the feature.
Install Windows Update Msu Files Silently
Use /Remove to remove a feature without removing the feature's manifest from the image. This option can only be used can be used with Windows 10, Windows 8.x, and Windows PE images above 4.0. The feature will be listed as 'Removed' when you use /Get-FeatureInfo to display feature details and can be restored and enabled using /Enable-Feature with the /Source option.
Syntax:
Examples:
/Cleanup-Image
Performs cleanup or recovery operations on the image. /AnalyzeComponentStore and /ResetBase can be used with Windows 10, Windows 8.1, and Windows PE images above 5.0. Beginning with Windows 10, version 1607, you can specify /Defer with /ResetBase. But we highly recommend you only use /Defer as an option in the factory where DISM /Resetbase requires more than 30 minutes to complete. /StartComponentCleanup can be used with Windows 10, Windows 8.x, and Windows PE images above 4.0. /CheckHealth, /ScanHealth, /RestoreHealth, /Source, and /LimitAccess can be used with Windows 10, Windows 8.x, and Windows PE images above 4.0. /HideSP and /SPSuperseded can’t be used when servicing a version of Windows that is earlier than Windows 7 Service Pack 1 (SP1) image.
Tip To determine when the /ResetBase option was last run, check the LastResetBase_UTC registry entry under this registry path:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionComponent Based Servicing
Syntax:
| Parameter | Description |
|---|---|
| /RevertPendingActions | If you experience a boot failure, you can use the /RevertPendingActions option to try to recover the system. The operation reverts all pending actions from the previous servicing operations because these actions might be the cause of the boot failure. The /RevertPendingActions option is not supported on a running operating system or a Windows PE or Windows Recovery Environment (Windows RE) image. Important: You should use the /RevertPendingActions option only in a system-recovery scenario on a Windows image that did not boot. |
| SPSuperseded | Removes any backup files created during the installation of a service pack. Use /HideSP to prevent the service pack from being listed in the Installed Updates Control Panel. The service pack cannot be uninstalled after the /SPSuperseded operation is completed. |
| /StartComponentCleanup | Cleans up the superseded components and reduces the size of the component store. Use /ResetBase to reset the base of superseded components, which can further reduce the component store size. Installed Windows updates can’t be uninstalled after running /StartComponentCleanup with the /ResetBase option. Use /Defer with /ResetBase to defer long-running cleanup operations to the next automatic maintenance. |
| /AnalyzeComponentStore | Creates a report of the component store. For more information about the report and how to use the information provided in the report, see Determine the Actual Size of the WinSxS Folder. |
| /CheckHealth | Checks whether the image has been flagged as corrupted by a failed process and whether the corruption can be repaired. |
| /ScanHealth | Scans the image for component store corruption. This operation will take several minutes. |
| /RestoreHealth | Scans the image for component store corruption, and then performs repair operations automatically. This operation will take several minutes. |
| /Source | Used with /RestoreHealth to specify the location of known good versions of files that can be used for the repair, such as a path to the Windows directory of a mounted image. |
| /LimitAccess | Prevents DISM from contacting Windows Update for repair of online images. |
Examples:
To learn more, see Repair a Windows Image.
Limitations
- When you are installing a package in an offline image, the package state is “install pending” because of pending online actions. In other words, the package will be installed when the image is booted and the online actions are processed. If subsequent actions are requested, they cannot be processed until the previous pending online action is completed. You can use the /PreventPending option when you add a package with /AddPackage to skip the installation of a package when there are pending online actions.
- Some packages require other packages to be installed first. You should not assume that dependencies will be satisfied. If there are dependency requirements, you should use an answer file to install the necessary packages. By passing an answer file to DISM, multiple packages can be installed in the correct order. This is the preferred method for installing multiple packages. For more information, see Add or Remove Packages Offline Using DISM.
- Packages are installed in the order that they are listed in the command line.
- When using DISM to list the optional components in a Windows PE image, the optional components will always be listed as pending even when the servicing operation was successful. This is by design and requires no additional action from you.