We use cookies to improve your experience on our websites and for

 Filter by title
advertising. Privacy Statement
Accept all Manage cookies

Optimize
Ｔ

Optimize Docs Documentation Learn Q&A Code Samples Search  Sign in

Compact OS, single-instancing,

Windows
andHardware Developer
image optimization Explore Ｓ Downloads Ｓ Events Samples Support Dashboard

Manage the component store

Ｔ

Docs / Windows / Manufacture / Desktop manufacturing  ＋

Manage the component

Take Inventory of an Image or

store

Determine the actual size of

the WinSxS folder

Clean up the WinSxS folder

Component Using DISM
05/02/2017 • 23 minutes to read • +1
Reduce the size of the
component store in an In this article
offline Windows image
Get Windows Image Information
Take inventory of an image Get Windows PE Information
or component using DISM Get Driver Information
Ｔ Prepare recovery tools Get Package and Feature Information
Ｔ Deployment Tools Reference Get App Package (.appx) Servicing Information
Ｔ IoT Core manufacturing Get International Settings and Languages

Service Get Windows Edition Information

Get Application Patch Information
Test for performance and compatibility
Related topics
 Download PDF
You can take an inventory of what drivers, packages, and other files and settings are
included in a Windows image. To do so, use Deployment Image Servicing and
Management (DISM) servicing commands.

You must mount an offline image from a WIM or VHD file before you can take
inventory of or service a specific Windows image. For more information, see Mount
and Modify a Windows Image Using DISM.

In this section:

Get Windows Image Information

Get Windows PE Information

Get Driver Information

Get Package and Feature Information

Get App Package (.appx) Servicing Information

Get International Settings and Languages

Get Windows Edition Information

Get Application Patch Information

Get Windows Image Information

You can use image commands to list the information about a specific Windows
image in a (WIM) file or virtual hard disk (VHD) file, about the images contained in a
specific WIM or VHD file, and about mounted WIM or VHD files. This information can
help you identify mount locations, image names, or verify the architecture of the
image that you are mounting.

You can gather information about all of the images in a WIM or VHD file by using the
/Get-ImageInfo servicing command in DISM. You can also gather information about
a specific image in a WIM or VHD file, such as operating system, architecture, and
settings, by specifying the name or index number of the image. To specify the image
in a VHD file, you must use /Index:1 .

You can identify the images that are currently mounted on your computer, and you
can list information about the mounted image such as read/write permissions,
mount location, mounted file path, and mounted image index by using the /Get-
MountedImageInfo servicing command.

For more information about image commands available in DISM, see DISM -
Deployment Image Servicing and Management Technical Reference for Windows.

To list images that are contained in a WIM or VHD file

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about all of the images in a WIM or VHD file, at the elevated
command prompt, type:

＝ Copy

Dism /Get-ImageInfo /imagefile:C:\test\images\install.wim

When used with the /Index or /Name options, more detailed information
about the specified image is displayed. To specify the image in a VHD file, you
must use /Index:1 .

The report that is generated includes the following information.

Field Description Example

Index The index value of the 1

image in the WIM or VHD
file.

Name The Windows edition Windows 8 Pro

name of the image in the
WIM or VHD file.

Description The description of the Windows 8 Pro

image in the WIM or VHD
file.

Size The size of the image. 8,045,951,502 bytes

To list mounted images

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. At the elevated command prompt, type:

＝ Copy

Dism /Get-MountedImageInfo

The report generated includes the following information:

Field Description Example

Mount Dir The location where the C:\Test\Mount

image is mounted.

Image File The full path to the WIM C:\Test\Images\install.wim

or VHD file.

Image Index The index number of the 1

mounted image that is
enclosed in WIM or VHD
file.

Mounted Read/Write Yes if the mounted image Yes

allows for both read and
write access or No if the
mounted image allows for
read-only access only.

Status The mount status of the OK

image. The possible values
include the following:

OK. The image is

mounted. There are no
problems.

Needs Remount. The

image must be
remounted. This can be
caused by rebooting the
host system when the
image is mounted.

Invalid.: the image is in an

invalid state. You might
have to use /Cleanup-
Mountpoints on the
image.

Get Windows PE Information

You can mount a Windows Preinstallation Environment (Windows PE) image for
servicing in the same way you would any Windows image. There are also Windows
PE servicing commands that are specific to a Windows PE image. These commands
can be used to list Windows PE settings such as scratchspace, targetpath, and
profiling information. For more information about Windows PE servicing commands
available in DISM, see DISM Windows PE Servicing Command-Line Options.

To list all settings in the mounted Windows PE image.

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about all of the Windows PE settings in the mounted

Windows PE image, at the elevated command prompt, type:

＝ Copy

Dism /image:C:\test\offline /Get-PESettings

The report generated includes the following information:

Field Description Example

Profiling Reports whether Windows Disabled

PE profiling is enabled or
disabled.

Scratch Space The amount of writeable 32MB

space available on the
Windows PE system
volume when booted in
ramdisk mode.

TargetPath The path to the root of the X:</p>

Windows PE image at boot
time.

Get Driver Information

The driver-servicing commands can be used to enumerate driver packages in the
driver store based on their .inf files. You can use the /Get commands to display basic
information about third-party driver packages or all driver packages in the offline
image. When you point to an offline image or a running operating system, you can
determine what driver packages are in the image, and get information about the
drivers.

You can display detailed information about a specific installed .inf file, or one that is
not yet installed. Installed drivers in the driver store will be named Oem0.inf,
Oem1.inf, and so on.

For more information about driver-servicing commands available in DISM, see DISM
Driver Servicing Command-Line Options.

To list driver packages in the offline image

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. Use one of the following commands to list information about all of the driver
packages in a mounted offline Windows image:

＝ Copy

Dism /image:C:\test\offline /Get-Drivers

＝ Copy

Dism /image:C:\test\offline /Get-Drivers /all

For a running operating system, type one of the following commands:

＝ Copy

Dism /online /Get-Drivers

＝ Copy

Dism /online /Get-Drivers /all

The report generated includes the following information:

Field Description Example

Published Name The name of the driver Oem0.inf

package after it is added
to the driver store.

Original File Name The original .inf file name Toaster.inf

of the driver package.

Inbox Yes for a default driver No

(inbox driver) or No for
third-party driver
packages.

Class Name The friendly name of the Printer

device class the driver is a
member of.

Provider Name The provider or digital Microsoft

signature for the driver
package.

Date The date associated with 10/31/2006

the driver, as it is specified
in the .inf file. The date will
be formatted appropriately
for your locale.

Version The version number that is 6.1.6801.0

specified in the INF
driverVer directive.

To get information about a specific driver

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. List information about a specific driver package in the offline Windows image.
For example, type:

＝ Copy

Dism /image:C:\test\offline /Get-DriverInfo /driver:oem1.inf

For a running operating system, type:

＝ Copy

Dism /online /Get-DriverInfo /driver:oem1.inf

The report generated includes the following information:

Field Description Example

Published The name of Oem0.inf

Name the driver
package
after it is
added to the
driver store.

Driver Store The path to E:\Images\Mount_depset\Windows\System32\DriverSto

Path the driver
location. If
the driver is
installed, the
path to the
driver store
is listed. If
the driver is
not installed
yet, the path
to the driver
on the
servicing
host is listed.

Class Name The friendly Printer

name of the
device class
the driver is
a member of.

Class The Printers

Description description
of the device
class the
driver is a
member of.

Class GUID The GUID of {4D36E97B-E325-11CE-BFC1-08002BE10318}

the device
class that the
driver is a
member of.

Date The date 8/6/2003

associated
with the
driver, as it is
specified in
the .inf file.
The date will
be formatted
appropriately
for your
locale.

Version The driver 1.0.1.37

version
number that
is specified in
the INF
driverVer
directive.

Boot Critical Yes if the No

driver is boot
critical or No
if it is not.

Drivers for The x86

architecture architecture
of the image
that it is
installed on.
If the driver
is not
installed yet,
the field is
reported
repeatedly
for each
supported
operating
system
architecture.

Manufacturer The Adventure Works

manufacturer
of the
supported
device.

Description A description Windows XP Adventure Works 376 Controller

of the
supported
device.

Architecture The x86

architecture
of the driver.

Hardware ID The ABC_3376

hardware ID
of the
supported
device.

Service The service C1232k

Name name of the
driver.

Compatible Alternate 12ABC

IDs Plug and
Play (PnP)
IDs for the
device, if any
apply.

Exclude IDs PnP IDs that A_123

will not
match the
device, any
apply.

Note
If you point to a driver that is not yet installed, the report will be slightly different.

Get Package and Feature Information

You can use operating system package-servicing commands to obtain information
about Windows packages. You can also use DISM and package-servicing commands
to obtain information about Windows features, either offline or on a running
Windows installation.

You can use the /PackagePath option to specify a .cab file or a folder where the .cab
file is extracted. You cannot use this command to obtain package information for
.msu files. Alternately, you can use /Get-Packages to find the name of a package,
and then use /PackageName to specify the name of the package.

You can display detailed information about a feature. You must use the
/FeatureName option with the /Get command. Use the /Get-Features option to find
the name of the feature in the image. Feature names are case sensitive if you are
servicing a Windows image other than Windows 8.

For more information about operating system package-servicing commands

available in DISM, see DISM Operating System Package Servicing Command-Line
Options.

To list all packages in the image

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about all of the packages in the offline Windows image, type
the following command:

＝ Copy

Dism /image:C:\test\offline /Get-Packages

For a running operating system, type the following command:

＝ Copy

Dism /online /Get-Packages

The report generated includes the following information:

Field Description Example

Package Identity The name of the Microsoft-Windows-NetFx3-OC-

package as it appears Package~31bf3856ad364e35~x86~en-
in the image. US~6.1.6772.0

State The current state of Installed

the package. Such as:

Installed. The
package is installed.

Install Pending. The

package is installed
but requires a reboot
to complete the
pending online
actions.

Staged. The package

is staged for
installation.

Release Type The type of package Feature Pack

that it is. Such as:

Feature Pack. A
Windows operating
system feature.

Language Pack. A
Windows operating
system Language
pack or Language
Interface Pack (LIP).

Foundation. Core
operating system
components
including optional
features.

Install Time The UTC date and 8/18/2008 7:58:00 PM

time when the
installation occurred.
If the package is not
installed yet, the
Install Time field is
left blank.

To list information about a specific package

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about a specific package in the offline Windows image, type
one of the following commands:

＝ Copy

Dism /image:C:\test\offline /Get-PackageInfo /PackagePath:C:\packages\p

＝ Copy

Dism /image:C:\test\offline /Get-PackageInfo /PackageName:Microsoft.Win

For a running operating system, type one of the following commands:

＝ Copy

Dism /online /Get-PackageInfo /PackagePath:C:\packages\package.cab

＝ Copy

Dism /online /Get-PackageInfo /PackageName:Microsoft.Windows.Calc.Demo~

The report generated includes the following information:

Field Description Example

Package Identity The name of the Microsoft-Windows-NetFx3-OC-

package as it appears Package~31bf3856ad364e35~x86~en-
in the image. US~6.1.6772.0

Applicable Indicates if the No

package applies to
the image.

Copyright Copyright Copyright© Microsoft Corporation. All

information for the Rights Reserved.
package.

Company The company that Microsoft Corporation

provided the
package, if available.

Creation Time The date and time 8/18/2008 7:58:00 PM

the package was
created, if available.

Description A brief description of Fix for KB300106

the package.

Install Client The client tool that DISM Package Manager Provider
installed the package.

Install Package The installed Microsoft-Windows-NetFx3-OC-

Name package.mum file Package~31bf3856ad364e35~x86~en-
name. US~6.1.6772.0.mum

Install Time The date and time 8/18/2008 7:58:00 PM

the package was
installed. If the
package is not
installed yet, the
Install Time field is
left blank.

Last Update Time The date the package 8/18/2008 7:58:00 PM

was last updated, if
available.

Name The display name of ActiveX® Installer Service

the package,
localized if available.

Generally, "default"
will be displayed for
all servicing
packages.

Product Name The name of the Microsoft-Windows-NetFx3-OC-

product that the Package
package belongs to,
if available.

Product Version The version of the 123.01.0000

product that the
package belongs to,
if available.

Release Type The type of package Feature Pack

that it is. Such as:

Feature Pack. A
Windows operating
system feature.

Language Pack. A
Windows operating
system Language
pack or Language
Interface Pack (LIP).

Foundation. Core
operating system
components
including optional
features.

Restart Required Indicates if a reboot Possible

is required when you
install or uninstall the
package online.

Support Where to find https://support.microsoft.com/?

Information support information, kbid=300106
if available.

State Indicates if the Installed

package is installed
in the operating
system. Possible
values include the
following:

Not Present. The

package is not
installed.

Installed. The
package is installed.

Install Pending. The

package will be
installed but requires
a reboot to complete
pending online
actions.

Staged. The package

is staged for
installation.

Completely offline Yes. The package can

capable be installed offline
without booting the
image.

No. You must boot

into the image in
order to complete
installation of this
package.

Undetermined. You
may have to boot
into the image in
order to complete
the installation of this
package. Many
packages can be
installed offline
entirely. If you
attempt to install a
package offline and a
reboot is required, it
will be reported in
the log file. You can
check the status of a
package using the
Get-PackageInfo
command.

This field is only

applicable to
Windows 8, Windows
Server® 2012, and
Windows
Preinstallation
Environment
(Windows PE) 4.0
target images.

Custom Properties A list of custom Dependency: Language Pack

properties defined in
the package manifest
file. If there are no
custom properties,
(No custom
properties found) will
be displayed.

Features listing for A list of the features Microsoft-Windows-NetFx3-OC-

package found in the package. Package~31bf3856ad364e35~x86~en-
US~6.1.6772.0 (No features found for
If there is no feature this package)
in the package, the
package identity will
be displayed
followed by (No
features found for
this package).

To list all features in the image

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about the features in the offline Windows image, type one of
the following commands:

＝ Copy

Dism /image:C:\test\offline /Get-Features

＝ Copy

Dism /image:C:\test\offline /Get-Features /PackageName:Microsoft.Window

＝ Copy

Dism /image:C:\test\offline /Get-Features /PackagePath:C:\packages\pack

For a running operating system, type one of the following commands:

＝ Copy

Dism /online /Get-Features

＝ Copy

Dism /online /Get-Features /PackageName:Microsoft.Windows.Calc.Demo~659

＝ Copy

Dism /online /Get-Features /PackagePath:C:\packages\package.cab

The report generated includes the following information:

Field Description Example

Feature Name The name of the feature as InboxGames

it appears in the image.

State The current state of the Disabled

feature. Possible values
include the following:

Enabled. The feature

is enabled.
Disabled. The
feature is disabled.
Enable Pending. The
feature will be
enabled but requires
a reboot to
complete pending
online actions.
Disable Pending.
The feature will be
disabled but
requires a reboot to
complete pending
online actions.
Disabled with
Payload Removed.
The feature is
disabled and its
payload has been
removed. Only the
package metadata is
present in the
image. The payload
can be restored and
the feature can be
enabled on demand
after the image is
deployed. For more
information about
features on demand,
see Configure a
Windows Repair
Source.

To list information about a specific feature

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about a specific feature in the offline Windows image, type
one of the following commands:

＝ Copy

Dism /image:C:\test\offline /Get-FeatureInfo /FeatureName:Hearts

＝ Copy

Dism /image:C:\test\offline /Get-FeatureInfo /FeatureName:LocalPack-GB

For a running operating system, type the following command:

＝ Copy

Dism /online /Get-FeatureInfo /FeatureName:Hearts

The report generated includes the following information:

Field Description Example

Feature Name Name of the feature. InboxGames

Display Name The name of the feature as Games

it appears in the user
interface.

Description A brief description of the Standard inbox games.

feature.

Restart Required Indicates if a restart is Yes

required when you enable
or disable this feature.

State The current state of the Disabled

feature. Possible values
include the following:

Enabled. The feature is

enabled.

Disabled. The feature is

disabled.

Enable Pending. The

feature will be enabled but
requires a reboot to
complete pending online
actions.

Disable Pending. The

feature will be disabled but
requires a reboot to
complete pending online
actions.

Disabled with Payload

Removed. The feature is
disabled and its payload
has been removed. Only
the package metadata is
present in the image. The
payload can be restored
and the feature can be
enabled on demand after
the image is deployed. For
more information about
features on demand, see
Configure a Windows
Repair Source.

Custom Properties A list of custom properties Dependency: Language

defined in the package Pack
manifest file. If there are
no custom properties, (No
custom properties found)
will be displayed.

Get App Package (.appx) Servicing

Information
You can use the app package (.appx) servicing commands to list the provisioned
apps in a Windows image. Provisioned apps will be registered for every user profile
that is created for the Windows image.

For more information about app package servicing commands available in DISM, see
DISM App Package (.appx or .appxbundle) Servicing Command-Line Options.

To list provisioned apps in the Windows image

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list provisioned apps in a mounted offline Windows image, type:

＝ Copy

Dism /image:c:\test\offline /Get-ProvisionedAppxPackages

For a running operating system, type:

＝ Copy

Dism /online /Get-ProvisionedAppxPackages

The report generated includes the following information:

Field Description Example

DisplayName The name of Fabrikam.Sample.CS

the app.

Version The version 1.0.0.0

number of
the app
package.

Architecture The neutral

architecture
of the app.

ResourceID For more

information,
see App
packaging
glossary.

PackageName The full name Fabrikam.Sample.CS_1.0.0.0_neutral_s9y1p3hwd5qda

of the app
package.

Get International Settings and Languages

The international servicing commands can be used to query existing international
settings in Windows and Windows PE images. For more information about operating
system package-servicing commands available in DISM, see DISM Languages and
International Servicing Command-Line Options.

Important
International servicing commands cannot be used on a Windows Vista or Windows
Server 2008 image.

Use the /online option to display information about international settings and
languages in the running operating system. Use /image:
<path_to_offline_image_directory> to display information about international settings
and languages in the offline image. When used with the /image and /distribution
options, information about international settings and languages in the distribution is
displayed.

To list all international settings and languages

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about all of the international settings in the offline Windows
image, type one of the following commands:

＝ Copy

Dism /image:C:\test\offline /Get-Intl

＝ Copy

Dism /image:C:\test\offline /distribution:C:\windows_distribution\langp

For a running operating system, type the following command:

＝ Copy

Dism /online /Get-Intl

The report generated includes the following information:

Field Description Example

Default system UI The language that is en-US

language currently set as the default
system UI language.

System locale The language for non- en-US

Unicode programs (also
referred to as system
locale) and font settings.

Default timezone The time zone that is Pacific Standard Time

currently set as the default.

User locale for default user The "standards and en-US

formats" language (also
referred to as user locale)
that is set for the default
user.

Location The geographical location United States

that is currently set for the
operating system. For
more information about
geographical locations, see
Table of Geographical
Locations.

Active keyboards The value pair for the 0409:00000409

active keyboard. In the
example provided, 0409 is
the language identifier and
00000409 is the keyboard
identifier.

Default keyboards The value pair for the 0409:00000409

default keyboard. In the
example provided, 0409 is
the language identifier and
00000409 is the keyboard
identifier.

Installed language(s) A list of all installed en-US

language packs.

Type The type of each installed en-US

language pack. For more
information, see Add Type: Fully localized
Language Packs to language
Windows.
ar-SA

Type: Partially localized

language, MUI type

Fallback Languages en-US,

fr-FR

Distribution languages A list of the languages that The default language in

are available in the the distribution is: ja-JP
distribution share.
The other available
languages in the
Note distribution are: bg-BG, nl-
NL
This list includes
the name of the
folder in the
distribution share.
The language of
the actual LP.cab
file in the folder is
not validated. For
example, if the
path to the
distribution is …
\Langpacks\bg-
BG\Lp.cab, the
value of bg-BG will
be reported as the
language in the
distribution share
even if the LP.cab
file is not the
correct .cab file for
bg-BG.

Keyboard layered driver A list of the keyboard Japanese Keyboard

drivers for Japanese or (106/109 Key)
Korean keyboards, if any
are installed.

Get Windows Edition Information

You can use the edition-servicing commands to obtain information about which
editions of Windows are available for upgrade.

Target editions are the editions of Windows that you can upgrade to. You can display
information about the current edition or the target edition of an offline Windows
image or a running operating system.

For more information about Windows edition servicing commands available in DISM,
see DISM Windows Edition-Servicing Command-Line Options.

To get information about the current Windows editions

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about the current edition of the offline Windows image, type
the following command:

＝ Copy

Dism /image:C:\test\offline /Get-CurrentEdition

For a running operating system, type the following command:

＝ Copy

Dism /online /Get-CurrentEdition

To get information about target editions of Windows

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about the target edition of the offline Windows image, type
the following command:

＝ Copy

Dism /image:C:\test\offline /Get-TargetEditions

For a running operating system, type the following command:

＝ Copy

Dism /online /Get-TargetEditions

Get Application Patch Information

Application servicing command-line options can be used on a offline image to check
the applicability of Microsoft® Windows® Installer application patches (.msp files)
and to query your offline image for information about installed Windows Installer
applications (.msi files) and application patches (.msp files).

You can display detailed information about installed MSP patches filtered by patch
and application. If the /PatchCode option is specified, detailed information is
displayed for all Windows Installer applications that the patch is applied to. If the
/ProductCode option is specified, information about all MSP patches in the specified
application is displayed.

If the /PatchCode and /ProductCode options are both specified, information is

displayed only if that specific patch is applied to the specified Windows Installer
application. If the /PatchCode and /ProductCode options are not specified, all
installed Windows Installer packages and MSP patches are displayed.

For more information about application servicing commands available in DISM, see
DISM Application Servicing Command-Line Options.

To list information about installed MSP patches

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about the MSP patches, type one of the following
commands:

＝ Copy

Dism /image:C:\test\offline /Get-AppPatchInfo

＝ Copy

Dism /image:C:\test\offline /Get-AppPatchInfo /PatchCode:{B0B9997C-GUID

＝ Copy

Dism /image:C:\test\offline /Get-AppPatchInfo /ProductCode:{B0F9497C-GU

＝ Copy

Dism /image:C:\test\offline /Get-AppPatchInfo /PatchCode:{B0B9997C-GUID

The report generated includes the following information:

Field Description Example

Patch Code A GUID identifying {8ACD2816-595D-48AA-A43B-3523CAA4F692}

a specific Windows
Installer package.
The package code
associates an .msi
file together with
an application or
product and can
also be used for
the verification of
sources.

Product Code A GUID that is the {7764DEFC-C5D1-413C-8428-2AA903BF6DAA}

principal
identification of an
application or
product.

Patch Name The registered QFE9 - Non Removable

display name for
the patch. For
patches that do
not include the
DisplayName
property in the
MsiPatchMetadata
table, the returned
display name is an
empty string.

Patch State 1 if this patch is 1 (Applied)

currently applied
to the product.

2 if this patch has

been superseded
by another patch.

4 if this patch has

been made
obsolete by
another patch.

Patch 1 if the patch is 0

Uninstallable marked as possible
to uninstall from
the product. In this
case, the installer
can still block the
uninstallation if
this patch is
required by
another patch that
cannot be
uninstalled.
Otherwise 0 is
reported.

Help Link Where to find https://www.microsoft.com

support
information, if
available.

Transforms The set of patch :App1RTMToApp1QFE9;:#App1RTMToApp1QFE9

transforms applied
to the product by
the last patch
installation. This
value may not be
available for per-
user unmanaged
applications if the
user is not logged
on to the
computer.

Local The location of the C:\Windows\Installer\132f5c.msp

Package local cached patch
file that is used by
the product.

Install Date The date when the 20080912

patch was applied
to the product.

To list information about MSP patches applied to an application

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about the MSP patches, type one of the following
commands:

＝ Copy

Dism /image:C:\test\offline /Get-AppPatches

＝ Copy

Dism /image:C:\test\offline /Get-AppPatches /ProductCode:{B0F9497C-GUID

The report generated includes the following information:

Field Description Example

Patch Code A GUID identifying a {8ACD2816-595D-48AA-

particular Windows A43B-3523CAA4F692}
Installer package. The
package code associates
an .msi file together with
an application or product
and can also be used for
the verification of sources.

Product Code A GUID that is the principal {7764DEFC-C5D1-413C-

identification of an 8428-2AA903BF6DAA}
application or product.

Patch Name The registered display QFE9 - Non Removable

name for the patch. For
patches that do not
include the DisplayName
property in the
MsiPatchMetadata table,
the returned display name
is an empty string.

To list information about all Windows Installer applications

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about the MSP patches, type the following command:

＝ Copy

Dism /image:C:\test\offline /Get-Apps

The report generated lists the product code and product name for applications that
are installed in the offline image. For example:

Product Code : {DB935363-5A68-47AF-A55A-CFC90F2E83BC}

Product Name : MsiTestApplication2

To list information about a specific Windows Installer application

1. Click Start, and type deployment. Right-click Deployment and Imaging Tools
Environment and then select Run as administrator.

2. To list information about the MSP patches, type the following command:

＝ Copy

Dism /image:C:\test\offline /Get-AppInfo /ProductCode:{B0F9497C-GUID-GU

The report generated includes the following information:

Field Description Example

Product Code A GUID that is the {DB935363-5A68-47AF-A55A-

principal CFC90F2E83BC}
identification of an
application or
product.

Product Name The name of the MsiTestApplication2

application.

Product State The installation 5 (Installed)

state for the
product at
initialization.

-1 if the product is
neither advertised
nor installed.

1 if the product is
advertised but not
installed.

2 if the product is
installed for a
different user.

5 if the product is
installed for the
current user.

Package Code A GUID identifying {C67CA1AE-6074-4810-BD74-

a particular F6BBB609744A}
Windows Installer
package. The
package code
associates an .msi
file together with
an application or
product and can
also be used for
the verification of
sources.

Product Version The version of the 1.0.0

product in string
format.

Assignment Type 0 if the product is 1 (Per-Machine)

advertised or
installed per-user.

1 if the product is
advertised or
installed per-
computer for all
users.

Publisher The name of the Microsoft MSI Test

manufacturer for
the product.

Language The decimal 1033

identifier for the
product language.

Install Source The directory that E:\Testpkg\App2_RTM</strong>

contains the
source .cab file or
the source file tree
of the installation
package.

Package Name The name of the MsiTestApplication2.msi

original installation
package.

Help Link Where to find https://www.microsoft.com/management

support
information, if
available.

Transforms The set of patch C:\Windows\Installer{BDB20E90-3ACD-

transforms applied 450B-BBDE-
to the product by 61E39687C6B1}\ACBlueT02.mst
the last patch
installation. This
value may not be
available for per-
user unmanaged
applications if the
user is not logged
on to the
computer.

Local Package The location of the C:\Windows\Installer\132f3b.msi

local cached
package.

Install Date The date the 20080912

application was
installed.

Related topics
Service a Windows Image Using DISM

Service a Windows PE Image with DISM

Deployment Image Servicing and Management (DISM) Best Practices

Is this page helpful?

 Yes  No

Recommended content

DISM Global Options for Command-Line Syntax

DISM Global Options for Command-Line Syntax

Add or Remove Packages Offline Using DISM

Add or Remove Packages Offline Using DISM

DISM Operating System Package (.cab or .msu) Servicing Command-Line

Options
DISM Operating System Package (.cab or .msu) Servicing Command-Line Options

Modify a Windows Image Using DISM

Modify a Windows image using DISM

Show more Ｓ

 English (United States) ０ Theme

Manage cookies Previous Version Docs Blog Contribute Privacy & Cookies Terms of Use Trademarks © Microsoft 2021