Applies to: desktop apps only

The Win32_DiskPartition WMI class represents the capabilities and management capacity of a partitioned area of a physical disk on a computer system running Windows. Example: Disk #0, Partition #1.

The following syntax is simplified from Managed Object Format (MOF) code and includes all of the inherited properties. Properties are listed in alphabetic order, not MOF order.

Syntax

class Win32_DiskPartition : CIM_DiskPartition
{
  uint16   Access;
  uint16   Availability;
  uint64   BlockSize;
  boolean  Bootable;
  boolean  BootPartition;
  string.  Caption;
  uint32   ConfigManagerErrorCode;
  boolean  ConfigManagerUserConfig;
  string.  CreationClassName;
  string   Description;
  string   DeviceID;
  uint32   DiskIndex;
  boolean  ErrorCleared;
  string   ErrorDescription;
  string   ErrorMethodology;
  uint32   HiddenSectors;
  uint32   Index;
  datetime InstallDate;
  uint32   LastErrorCode;
  string   Name;
  uint64   NumberOfBlocks;
  string   PNPDeviceID;
  uint16   PowerManagementCapabilities[];
  boolean  PowerManagementSupported;
  boolean  PrimaryPartition;
  string   Purpose;
  boolean  RewritePartition;
  uint64   Size;
  uint64   StartingOffset;
  string   Status;
  uint16   StatusInfo;
  string   SystemCreationClassName;
  string   SystemName;
  string   Type;
};

Members

The Win32_DiskPartition class has these types of members:

• Properties

Properties

The Win32_DiskPartition class has these properties.

Access

Data type: uint16

Access type: Read-only

Media access available.

Value	Meaning
0	Unknown
1	Readable
2	Writable
3	Read/write Supported
4	Write Once

 

Availability

Data type: uint16

Access type: Read-only

Availability and status of the device. Inherited from CIM_LogicalDevice.

Value	Meaning
1 (0x1)	Other
2 (0x2)	Unknown
3 (0x3)	Running or Full Power
4 (0x4)	Warning
5 (0x5)	In Test
6 (0x6)	Not Applicable
7 (0x7)	Power Off
8 (0x8)	Offline
9 (0x9)	Off Duty
10 (0xA)	Degraded
11 (0xB)	Not Installed
12 (0xC)	Install Error
13 (0xD)	Power Save - Unknown The device is known to be in a power save mode, but its exact status is unknown.
14 (0xE)	Power Save - Low Power Mode The device is in a power save state but still functioning, and may exhibit degraded performance.
15 (0xF)	Power Save - Standby The device is not functioning, but could be brought to full power quickly.
16 (0x10)	Power Cycle
17 (0x11)	Power Save - Warning The device is in a warning state, though also in a power save mode.

 

BlockSize

Data type: uint64

Access type: Read-only

Size in bytes of the blocks which form this storage extent. If unknown or if a block concept is not valid (for example, for aggregate extents, memory or logical disks), enter a 1.

For more information about using uint64 values in scripts, see Scripting in WMI.

Bootable

Data type: boolean

Access type: Read-only

Computer can be booted from this partition.

BootPartition

Data type: boolean

Access type: Read-only

Partition is the active partition. The operating system uses the active partition when booting from a hard disk.

Caption

Data type: string.

Access type: Read-only

Short description of the object.

ConfigManagerErrorCode

Data type: uint32

Access type: Read-only

Windows Configuration Manager error code.

Value	Meaning
0 (0x0)	Device is working properly.
1 (0x1)	Device is not configured correctly.
2 (0x2)	Windows cannot load the driver for this device.
3 (0x3)	Driver for this device might be corrupted, or the system may be low on memory or other resources.
4 (0x4)	Device is not working properly. One of its drivers or the registry might be corrupted.
5 (0x5)	Driver for the device requires a resource that Windows cannot manage.
6 (0x6)	Boot configuration for the device conflicts with other devices.
7 (0x7)	Cannot filter.
8 (0x8)	Driver loader for the device is missing.
9 (0x9)	Device is not working properly. The controlling firmware is incorrectly reporting the resources for the device.
10 (0xA)	Device cannot start.
11 (0xB)	Device failed.
12 (0xC)	Device cannot find enough free resources to use.
13 (0xD)	Windows cannot verify the device's resources.
14 (0xE)	Device cannot work properly until the computer is restarted.
15 (0xF)	Device is not working properly due to a possible re-enumeration problem.
16 (0x10)	Windows cannot identify all of the resources that the device uses.
17 (0x11)	Device is requesting an unknown resource type.
18 (0x12)	Device drivers must be reinstalled.
19 (0x13)	Failure using the VxD loader.
20 (0x14)	Registry might be corrupted.
21 (0x15)	System failure. If changing the device driver is ineffective, see the hardware documentation. Windows is removing the device.
22 (0x16)	Device is disabled.
23 (0x17)	System failure. If changing the device driver is ineffective, see the hardware documentation.
24 (0x18)	Device is not present, not working properly, or does not have all of its drivers installed.
25 (0x19)	Windows is still setting up the device.
26 (0x1A)	Windows is still setting up the device.
27 (0x1B)	Device does not have valid log configuration.
28 (0x1C)	Device drivers are not installed.
29 (0x1D)	Device is disabled. The device firmware did not provide the required resources.
30 (0x1E)	Device is using an IRQ resource that another device is using.
31 (0x1F)	Device is not working properly. Windows cannot load the required device drivers.

 

ConfigManagerUserConfig

Data type: boolean

Access type: Read-only

If True, the device is using a user-defined configuration.

CreationClassName

Data type: string.

Access type: Read-only

Name of the first concrete class to appear in the inheritance chain used in the creation of an instance. When used with the other key properties of the class, the property allows all instances of this class and its subclasses to be uniquely identified.

Description

Data type: string

Access type: Read-only

Description of the object.

DeviceID

Data type: string

Access type: Read-only

Qualifiers: Key

Unique identifier of the disk drive and partition, from the rest of the system.

DiskIndex

Data type: uint32

Access type: Read-only

Index number of the disk containing this partition.

Example: 0

ErrorCleared

Data type: boolean

Access type: Read-only

If True, the error reported in LastErrorCode is now cleared.

ErrorDescription

Data type: string

Access type: Read-only

Information about the error recorded in LastErrorCode, and information on any corrective actions that may be taken.

ErrorMethodology

Data type: string

Access type: Read-only

Type of error detection and correction supported by this storage extent.

HiddenSectors

Data type: uint32

Access type: Read-only

Number of hidden sectors in the partition.

Example: 63

Index

Data type: uint32

Access type: Read-only

Index number of the partition.

Example: 1

InstallDate

Data type: datetime

Access type: Read-only

Date the object was installed. This property does not need a value to indicate that the object is installed.

LastErrorCode

Data type: uint32

Access type: Read-only

Last error code reported by the logical device.

Name

Data type: string

Access type: Read-only

Label by which the object is known. When subclassed, the property can be overridden to be a key property.

NumberOfBlocks

Data type: uint64

Access type: Read-only

Total number of consecutive blocks, each block the size of the value contained in the BlockSize property, which form this storage extent. Total size of the storage extent can be calculated by multiplying the value of the BlockSize property by the value of this property. If the value of BlockSize is 1, this property is the total size of the storage extent.

For more information about using uint64 values in scripts, see Scripting in WMI.

PNPDeviceID

Data type: string

Access type: Read-only

Windows Plug and Play device identifier of the logical device.

Example: "*PNP030b"

PowerManagementCapabilities

Data type: uint16 array

Access type: Read-only

Array of the specific power-related capabilities of a logical device. This property is inherited from CIM_LogicalDevice.

Value	Meaning
0 (0x0)	Unknown
1 (0x1)	Not Supported
2 (0x2)	Disabled
3 (0x3)	Enabled The power management features are currently enabled but the exact feature set is unknown or the information is unavailable.
4 (0x4)	Power Saving Modes Entered Automatically The device can change its power state based on usage or other criteria.
5 (0x5)	Power State Settable The SetPowerState method is supported. This method is found on the parent CIM_LogicalDevice class and can be implemented. For more information, see Designing Managed Object Format (MOF) Classes.
6 (0x6)	Power Cycling Supported The SetPowerState method can be invoked with the PowerState parameter set to 5 (Power Cycle).
7 (0x7)	Timed Power-On Supported The SetPowerState method can be invoked with the PowerState parameter set to 5 (Power Cycle) and Time set to a specific date and time, or interval, for power-on.

 

PowerManagementSupported

Data type: boolean

Access type: Read-only

If True, the device can be power-managed (can be put into suspend mode, and so on). The property does not indicate that power management features are currently enabled, only that the logical device is capable of power management.

PrimaryPartition

Data type: boolean

Access type: Read-only

If True, this is the primary partition.

Purpose

Data type: string

Access type: Read-only

Description of the media and its use.

RewritePartition

Data type: boolean

Access type: Read-only

If True, the partition information has changed. When you change a partition (with IOCTL_DISK_SET_DRIVE_LAYOUT), the system uses this property to determine which partitions have changed and need their information rewritten. If TRUE, the partition must be rewritten.

Size

Data type: uint64

Access type: Read-only

Qualifiers: Units (Bytes)

Total size of the partition.

Example: 1059045376

For more information about using uint64 values in scripts, see Scripting in WMI.

StartingOffset

Data type: uint64

Access type: Read-only

Qualifiers: Units (Bytes)

Starting offset (in bytes) of the partition.

Example: 32256

For more information about using uint64 values in scripts, see Scripting in WMI.

Status

Data type: string

Access type: Read-only

Qualifiers: MaxLen (10)

Current status of the object. Various operational and nonoperational statuses can be defined. Operational statuses include: "OK", "Degraded", and "Pred Fail" (an element, such as a SMART-enabled hard disk drive, may be functioning properly but predicting a failure in the near future). Nonoperational statuses include: "Error", "Starting", "Stopping", and "Service". The latter, "Service", could apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative work. Not all such work is online, yet the managed element is neither "OK" nor in one of the other states.

The values are:

"OK"

"Error"

"Degraded"

"Unknown"

"Pred Fail"

"Starting"

"Stopping"

"Service"

"Stressed"

"NonRecover"

"No Contact"

"Lost Comm"

StatusInfo

Data type: uint16

Access type: Read-only

State of the logical device. If this property does not apply to the logical device, the value 5 (Not Applicable) should be used. This property is inherited from CIM_LogicalDevice.

Value	Meaning
1 (0x1)	Other
2 (0x2)	Unknown
3 (0x3)	Enabled
4 (0x4)	Disabled
5 (0x5)	Not Applicable

 

SystemCreationClassName

Data type: string

Access type: Read-only

Creation class name of the scoping system.

SystemName

Data type: string

Access type: Read-only

Name of the scoping system.

Type

Data type: string

Access type: Read-only

Type of the partition.

The values are:

"Unused"

"12-bit FAT"

"Xenix Type 1"

"Xenix Type 2"

"16-bit FAT"

"Extended Partition"

"MS-DOS V4 Huge"

"Installable File System"

"PowerPC Reference Platform"

"UNIX"

"NTFS"

"Win95 w/Extended Int 13"

"Extended w/Extended Int 13"

"Logical Disk Manager"

"Unknown"

Remarks

The Win32_DiskPartition class is derived from CIM_DiskPartition.

Examples

For script code examples, see WMI Tasks for Scripts and Applications and the TechNet ScriptCenter Script Repository.

For C++ code examples, see WMI C++ Application Examples.

Requirements

See also

Operating System Classes

Send comments about this topic to Microsoft

Build date: 3/9/2012