Library Files, Header Files, and Compiler Settings
[The feature associated with this page, Windows Media Format 11 SDK, is a legacy feature. It has been superseded by Source Reader and Sink Writer. Source Reader and Sink Writer have been optimized for Windows 10 and Windows 11. Microsoft strongly recommends that new code use Source Reader and Sink Writer instead of Windows Media Format 11 SDK, when possible. Microsoft suggests that existing code that uses the legacy APIs be rewritten to use the new APIs if possible.]
The programming components of the Windows Media DRM Client Extended APIs are defined in the wmdrmsdk.h header file, and implemented in the wmdrmsdk.lib and mfuuid.lib libraries.
Some of the functionality of the Windows Media DRM Client Extended APIs requires that you obtain a protected library from Microsoft. This library, called the stub library in this documentation, is specific to the recipient and specifies the application security level for your applications. The stub library replaces wmdrmsdk.lib; you should never link to both.
Note The DRM stub library is separate from the stub library used by the rest of the Windows Media Format SDK but is licensed using the same method.
Note The DRM stub library must be linked into your application after the library file msvcrt.lib to avoid linker errors.
The stub library contains an embedded certificate which can be revoked by Microsoft if you fail to comply with the terms and conditions of the license agreement.
Specific methods that require the stub library are labeled in the documentation. If you try to use such a method without linking to the stub library, it will return an NS_E_DRM_STUBLIB_REQUIRED error.
The DRM subsystem cannot be used in a debug build. If this is attempted, methods of the API will return the NS_E_DRM_DEBUGGING_NOT_ALLOWED error.
Related topics