Individualizing DRM Applications
[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.]
To increase security, the DRM component of applications can be individualized. An individualized application is one that has received an upgrade to its DRM components that differentiates it from all other copies of the same application. Content owners can require that their protected files be played only on an application that has been individualized.
The individualization process starts when the application contacts the Microsoft Individualization Service, which then installs a security upgrade on the user's computer. Because the Individualization Service handles information from the user, you must display the Microsoft privacy policy or provide a link to that page at the Microsoft Web site: https://privacy.microsoft.com/privacystatement.
Individualization can be accomplished in different ways. For example, individualization can take place when a user plays a protected file. The license request is sent to the Windows Media License Service, which inspects the certificate of the application requesting the license. If the DRM component of the application has not been individualized, Windows Media License Service refuses to issue the license, because it is the policy of Windows Media License Service to issue licenses only to individualized players. The application can then notify the user that the application must be upgraded. If the user agrees, a security upgrade is provided to individualize the DRM component of the application.
For a better user experience, you can initiate the individualization process as a security upgrade step during setup; then the user is not interrupted to get a security upgrade while trying to play a protected file. You can also actively encourage individualization by adding a Security Upgrade menu command or button to the application.
Note
DRM is not supported by the x64-based version of this SDK.
Related topics