NS_S_DRM_LICENSE_ACQUIRED (0x000D2726) — It's Not An Error

You're staring at a code that says "license acquired" while your movie sits frozen, and that's maddening.

Here's the thing nobody tells you: NS_S_DRM_LICENSE_ACQUIRED is not an error. The NS_S_ prefix means "Non-fatal Success." Microsoft's DRM stack wrote that code to confirm it grabbed a PlayReady license from the license server. The playback failure you're actually chasing is a different code, usually hiding in the same log or Event Viewer entry right next to this one.

The real fix

Stop hunting 0x000D2726. Hunt the code that follows it. Do this:

1. Open Event Viewer. Press Win + R, type eventvwr.msc, hit Enter. You should see the Event Viewer console window open.
2. In the left pane, expand Applications and Services Logs → Microsoft → Windows → Media Foundation.
3. Click the Operational log. If it's empty or disabled, right-click it, choose Enable Log, then reproduce the playback failure.
4. Look for events timestamped at the moment your video died. You'll see NS_S_DRM_LICENSE_ACQUIRED logged as informational, then a nearby event with a code starting in 0x8 or 0xC. That second code is your real problem.

Common follow-up codes and what they mean:

If you see the PlayReady corruption code, nuke and rebuild the DRM stores. Close every media app first — this won't work with Netflix or Movies & TV still running.

net stop playready /y
net stop wmdrmdev /y
net stop wmdrmnet /y

ren "%ProgramData%\Microsoft\PlayReady" PlayReady.old
ren "%ProgramData%\Microsoft\Windows\DRM" DRM.old

net start playready
net start wmdrmdev
net start wmdrmnet

Run that from an elevated Command Prompt. After the last net start, you should see "The service started successfully" three times. Reopen your streaming app and play the same title. Windows rebuilds both folders on first playback — give it 10-15 seconds of buffering before you judge it.

Why this works

PlayReady is Microsoft's DRM client. When a streaming app asks to play protected content, it hands the request to PlayReady, which talks to the provider's license server, gets a signed token, and stores it under %ProgramData%\Microsoft\PlayReady. The NS_S_DRM_LICENSE_ACQUIRED message means step one through four all worked. The token landed.

What fails next is decryption. The renderer takes that token, checks it against the content's key ID, and either the token doesn't match, the store is corrupt, or the pipeline can't bind to the protected surface. Renaming those two folders forces Windows to reissue a fresh license on next playback — no stale token, no half-written key blob.

If renaming folders makes you nervous: you're not deleting anything. Both .old folders stick around until you clean them up manually. Nothing's gone until you say so.

Less common variations

Sometimes the follow-up code never shows up because playback just hangs. Try these in order.

Hardware acceleration collision

On older Intel UHD 620 graphics with PlayReady 4 SL3000, protected video can hang at license handoff. Disable hardware acceleration in the app's settings — Netflix, Prime Video, and Disney+ all have the toggle buried under playback settings. If playback starts, the GPU driver is the culprit. Update to the latest Intel DCH driver from Intel's site, not Windows Update.

Clock skew

DRM license tokens are time-signed. If your PC's clock drifts more than 5 minutes from the license server, the token gets rejected silently — you see the acquire message, then nothing. Right-click the clock, Adjust date/time, toggle Set time automatically off and back on. Then run:

w32tm /resync /force

You should see "The command completed successfully" within a few seconds.

Region mismatch on Microsoft Store content

Movies & TV titles bought in one Store region won't license in another, even with the same Microsoft account. The Store thinks you're in region A, the license server is region B, and PlayReady hands you a token the renderer can't use. Check Settings → Time & language → Language & region → Country or region. If it doesn't match where you bought the movie, that's your problem.

Third-party codec packs

K-Lite, CCCP, and Shark007 codec packs overwrite Media Foundation handlers. Protected content stops working the moment a non-Microsoft handler takes over the MF pipeline. Uninstall the pack, reboot, and re-test. The real fix is to use VLC for local files and leave Media Foundation alone for streaming — VLC doesn't touch PlayReady.

Prevention

• Don't disable the Windows Media Player Network Sharing Service. It sounds unrelated. It isn't — DRM renewals ride on it.
• Skip "debloat" scripts that rip out PlayReady or the Windows Media Feature Pack. You'll save 40MB and lose every streaming app on the machine.
• Keep your GPU driver current. PlayReady uses hardware-backed protected memory, and stale drivers break the handoff more often than anything else.
• Leave your system clock on automatic sync. This one causes the weirdest intermittent failures.

Bottom line: when you see 0X000D2726, don't chase it. It's a receipt, not a complaint. Follow the log two lines down and fix what's actually broken.