A DIF_POWERMESSAGEWAKE request allows an installer to supply custom text that Windows displays on the power management properties page of the device properties.

When Sent

When a user clicks on a menu item or tab to display the properties of a device.

Windows only sends this DIF request if the drivers for the device support power management. Otherwise, Windows does not display any power properties for the device.

Who Handles

Class Co-installer

Can handle

Device Co-installer

Can handle

Class Installer

Can handle


Installer Input


Supplies a handle to the device information set that contains the device.


Supplies a pointer to an SP_DEVINFO_DATA structure that identifies the device in the device information set.

Device Installation Parameters

There are device installation parameters (SP_DEVINSTALL_PARAMS) associated with the DeviceInfoData.

Class Installation Parameters

An SP_POWERMESSAGEWAKE_PARAMS structure is associated with the DeviceInfoData.

Installer Output

Class Installation Parameters

An installer can modify the SP_POWERMESSAGEWAKE_PARAMS to supply custom text for a device's power properties page.

Installer Return Value

A co-installer typically returns NO_ERROR, ERROR_DI_POSTPROCESSING_REQUIRED, or a Win32 error code.

A class installer returns NO_ERROR if it successfully supplies power properties text. Otherwise, a class installer returns ERROR_DI_DO_DEFAULT or a Win32 error code.

Default DIF Code Handler


Installer Operation

A DIF_POWERMESSAGEWAKE request allows an installer to supply text that Windows displays on the power properties page for a device.

If a co-installer supplies power-properties text, it should do so in its postprocessing phase. A co-installer should be careful when overwriting any power-properties text supplied by an installer that handled the request before the co-installer.

For more information about DIF codes, see Handling DIF Codes.



Supported in Microsoft Windows 2000 and later versions of Windows.


Setupapi.h (include Setupapi.h)

See also




Send comments about this topic to Microsoft

© 2016 Microsoft