Add-WindowsPackage

Add-WindowsPackage

Adds a single .cab or .msu file to a Windows image.

Syntax

Parameter Set: Offline
Add-WindowsPackage -PackagePath <String> -Path <String> [-IgnoreCheck] [-LogLevel <LogLevel> {Errors | Warnings | WarningsInfo} ] [-LogPath <String> ] [-NoRestart] [-PreventPending] [-ScratchDirectory <String> ] [-SystemDrive <String> ] [-WindowsDirectory <String> ] [ <CommonParameters>]

Parameter Set: Online
Add-WindowsPackage -Online -PackagePath <String> [-IgnoreCheck] [-LogLevel <LogLevel> {Errors | Warnings | WarningsInfo} ] [-LogPath <String> ] [-NoRestart] [-PreventPending] [-ScratchDirectory <String> ] [-SystemDrive <String> ] [-WindowsDirectory <String> ] [ <CommonParameters>]

Detailed Description

The Add-WindowsPackage cmdlet installs a specified .cab or .msu package in the image.

Parameters

-IgnoreCheck

Skips the applicability check for each package.

-LogLevel<LogLevel>

Specifies the maximum output level shown in the logs. The default log level is 3. The accepted values are as follows:1 = Errors only2 = Errors and warnings3 = Errors, warnings, and information4 = All of the information listed previously, plus debug output

-LogPath<String>

Specifies the full path and file name to log to. If not set, the default is %WINDIR%\Logs\Dism\dism.log.In Windows PE, the default directory is the RAMDISK scratch space which can be as low as 32 MB. The log file will automatically be archived. The archived log file will be saved with .bak appended to the file name and a new log file will be generated. Each time the log file is archived the .bak file will be overwritten. When using a network share that is not joined to a domain, use the net use command together with domain credentials to set access permissions before you set the log path for the DISM log.

-NoRestart

Suppresses reboot. If a reboot is not required, this command does nothing. This option will keep the application from prompting for a restart or keep it from restarting automatically.

-Online

Specifies that the action is to be taken on the operating system that is currently running on the local computer.

-PackagePath<String>

Specifies the location of the package to add to the image.

Valid values are:

-- 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.

If PackagePath is a folder that contains a .cab or .msu files at its root, any subfolders are also recursively checked for .cab and .msu files.

-Path<String>

Specifies the full path to the root directory of the offline Windows image that you will service. If the directory named Windows is not a subdirectory of the root directory, -WindowsDirectory must be specified.

-PreventPending

Skips the installation of the package if the package or Windows image has pending online actions.

-ScratchDirectory<String>

Specifies a temporary directory that will be used when extracting files for use during servicing. The directory must exist locally. If not specified, the \Windows\%Temp% directory will be used, with a subdirectory name of a randomly generated hexadecimal value for each run of DISM. Items in the scratch directory are deleted after each operation. You should not use a network share location as a scratch directory to expand a package (.cab or .msu file) for installation. The directory used for extracting files for temporary usage during servicing should be a local directory.

-SystemDrive<String>

Specifies the path to the location of the BootMgr files. This is necessary only when the BootMgr files are located on a partition other than the one that you are running the command from. Use -SystemDrive to service an installed Windows image from a Windows PE environment.

-WindowsDirectory<String>

Specifies the path to the Windows directory relative to the image path. This cannot be the full path to the Windows directory; it should be a relative path. If not specified, the default is the Windows directory in the root of the offline image directory.

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters (https://go.microsoft.com/fwlink/p/?LinkID=113216).

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

• System.String[]
• Microsoft.Dism.Commands.ImageObject
• Microsoft.Dism.Commands.BasicPackageObject
• Microsoft.Dism.Commands.AdvancedPackageObject

Outputs

The output type is the type of the objects that the cmdlet emits.

• Microsoft.Dism.Commands.ImageObject

Examples

Example 1: Add a package to an online image

This command adds a .cab package to an online image.

PS C:\> Add-WindowsPackage –Online –PackagePath "c:\packages\package.cab"

Example 2: Add a file to a mounted image

This command adds an .msu file to a mounted Windows image unless there are pending actions on the package or the image.

PS C:\> Add-WindowsPackage –Path "c:\offline" –PackagePath "c:\packages\demo_package.msu" -PreventPending

Example 3: Add several packages to a mounted image

This command adds all of the packages in a folder to a mounted Windows image without checking if they are applicable to the image.

PS C:\> Add-WindowsPackage –Path "c:\offline" –PackagePath "c:\packages" -IgnoreCheck

Related topics

Get-WindowsPackage

Remove-WindowsPackage