Win32_DriverVXD - The Win32_DriverVXD class represents a virtual device driver on a Win32 computer system. A virtual device is a program that manages a system resource (such as a hardware device or installed software) so that more than one application can use the resource at the same time. Windows uses virtual devices to allow multitasking for Windows-based applications. The virtual devices work in conjunction with Windows to process interrupts, and carry out I/O operations for a given application without disrupting the execution of other applications. Most virtual devices manage a hardware device and many also manage or replace corresponding software such as ROM BIOS routines. A virtual device can contain the device-specific code needed to carry out actions on the device or it can rely on the other software to carry out these operations. In all cases, the virtual device keeps track of the state of the device for each application and ensures that the device is in the correct state whenever an application continues execution. Some virtual devices manage only installed software, such as an MS-DOS device driver or a Terminate and Stay Resident (TSR) program. Such virtual devices often contain code that either emulates the software or ensures that the software uses data that applies only to the currently running application. Virtual devices are sometimes used to improve the performance of installed software; the Intel-compatible microprocessors can execute the 32-bit code of a virtual device more efficiently than the 16-bit code of an MS-DOS device driver or TSR.

Win32_DriverVXD
The Win32_DriverVXD class represents a virtual device driver on a Win32 computer system. A virtual device is a program that manages a system resource (such as a hardware device or installed software) so that more than one application can use the resource at the same time. Windows uses virtual devices to allow multitasking for Windows-based applications. The virtual devices work in conjunction with Windows to process interrupts, and carry out I/O operations for a given application without disrupting the execution of other applications. Most virtual devices manage a hardware device and many also manage or replace corresponding software such as ROM BIOS routines. A virtual device can contain the device-specific code needed to carry out actions on the device or it can rely on the other software to carry out these operations. In all cases, the virtual device keeps track of the state of the device for each application and ensures that the device is in the correct state whenever an application continues execution. Some virtual devices manage only installed software, such as an MS-DOS device driver or a Terminate and Stay Resident (TSR) program. Such virtual devices often contain code that either emulates the software or ensures that the software uses data that applies only to the currently running application. Virtual devices are sometimes used to improve the performance of installed software; the Intel-compatible microprocessors can execute the 32-bit code of a virtual device more efficiently than the 16-bit code of an MS-DOS device driver or TSR.
NameSpace Path
\ROOT\CIMV2
PROPERTY	SMS_REPORT	CIMTYPE	DESCRIPTION
BuildNumber		String	The internal identifier for this compilation of this software element.
Caption		String	The Caption property is a short textual description (one-line string) of the object.
CodeSet		String	The code set used by this software element.
Control		String	The Control property indicates the offset address to the driver's control procedures. The virtual machine manager calls this procedure to send control messages to the virtual device system. The system control messages direct the virtual device to carry out actions. An example of an action is initializing itself; another is notifying the virtual device of changes to virtual machines (such as a virtual machine is being created).
Description		String	The Description property provides a textual description of the object.
DeviceDescriptorBlock		String	The DeviceDescriptorBlock property indicates the offset address to the device descriptor block (DDB) structure. The DDB contains information that the operating system uses to execute the procedures of the driver, including its location in the interrupt list, and other data to run and communicate with this VXD.
IdentificationCode		String	The value of this property is the manufacturer's identifier for this software element. Often this will be a stock keeping unit (SKU) or a part number.
InstallDate		DateTime	The InstallDate property is datetime value indicating when the object was installed. A lack of a value does not indicate that the object is not installed.
LanguageEdition		String	The value of this property identifies the language edition of this software element. The language codes defined in ISO 639 should be used. Where the software element represents multi-lingual or international version of a product, the string multilingual should be used.
Manufacturer		String	Manufacturer of this software element
Name		String	The name used to identify this software element
OtherTargetOS		String	The OtherTargetOS property records the manufacturer and operating system type for a software element when the TargetOperatingSystem property has a value of 1 ("Other"). Therefore, when the TargetOperatingSystem property has a value of "Other", the OtherTargetOS property must have a non-null value. For all other values of TargetOperatingSystem, the OtherTargetOS property is to be NULL.
PM_API		String	The PM_API indicates the offset address to the protected mode application programming interface for this VXD. These functions can give applications direct access to the features of the VXD.
SerialNumber		String	The assigned serial number of this software element.
ServiceTableSize		UInt32	The ServiceTableSize property indicates the number of installed services and device driver services provided by the operating system. Example: 1024
SoftwareElementID		String	This is an identifier for this software element and is designed to be used in conjunction with other keys to create a unique representation of this CIM_SoftwareElement
SoftwareElementState		UInt16	The SoftwareElementState is defined in this model to identify various states of a software elements life cycle. - A software element in the deployable state describes the details necessary to successful distribute it and the details (conditions and actions) required to create a software element in the installable state (i.e., the next state). - A software element in the installable state describes the details necessary to successfully install it and the details (conditions and actions required to create a software element in the executable state (i.e., the next state). - A software element in the executable state describes the details necessary to successfully start it and the details (conditions and actions required to create a software element in the running state (i.e., the next state). - A software element in the running state describes the details necessary to monitor and operate on a start element.
Status		String	The Status property is a string indicating the current status of the object. Various operational and non-operational statuses can be defined. Operational statuses are "OK", "Degraded" and "Pred Fail". "Pred Fail" indicates that an element may be functioning properly but predicting a failure in the near future. An example is a SMART-enabled hard drive. Non-operational statuses can also be specified. These are "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 on-line, yet the managed element is neither "OK" nor in one of the other states.
TargetOperatingSystem		UInt16	The TargetOperatingSystem property allows the provider to specify the operating system environment. The value of this property does not ensure binary executable. Two other pieces of information are needed. First, the version of the OS needs to be specified using the OS version check. The second piece of information is the architecture the OS runs on. The combination of these constructs allows the provider to clearly identify the level of OS required for a particular software element.
V86_API		String	The V86_API indicates the offset to the application programming interface for use under virtual 8086 mode. These functions can give applications direct access to the features of the VXD.
Version		String	The Version property indicates the version of the VXD driver. Example: 3,51
SAMPLE DATA INSTANCE
Class does not currently contain data instances