| Previous | Next |
| NS_E_WMP_WINDOWSAPIFAILURE | NS_E_DEVICE_NOT_READY |
NS_E_WMP_RECORDING_NOT_ALLOWED
Meaning at the producing boundary
NS_E_WMP_RECORDING_NOT_ALLOWED is HRESULT 0xC00D0FC9. At the recording not allowed checkpoint it means the selected content rights do not permit the requested recording or burn action; the result belongs to WMP file download, save and package persistence, not to an unspecified Player failure.
The generated part of the What Is page already shows the standard AllStat description for NS_E_WMP_RECORDING_NOT_ALLOWED. The additional test for the recording not allowed condition is to record the requested action and rights decision separately from file accessibility; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
Why the producing component matters
Before correcting the recording not allowed condition, remember that download, parse and save are separate stages: a successful HTTP response does not prove that the payload is valid or that the destination can be committed. A second platform rule for recording not allowed is that read-only attributes, sharing modes, redirected paths and streamed sources can prevent persistence even when playback succeeds.
Representative case for recording not allowed: Protected content plays but its license denies burn/record. For recording not allowed, the example isolates the producing boundary without assuming that the library, codec stack, skin engine and ActiveX host all failed together.
How to prove the condition
- Find the first component that returned
NS_E_WMP_RECORDING_NOT_ALLOWEDand label that event as the recording not allowed boundary. - Freeze the input and object identity associated with recording not allowed before WMP fallback or cleanup changes it.
- Reconstruct the immediately preceding successful state for recording not allowed, then identify the call or event that crossed into failure.
- Perform the code-specific test: record the requested action and rights decision separately from file accessibility.
- Make the narrow correction—obtain rights that permit recording or choose content authorized for the operation—and repeat the same producing operation for recording not allowed.
Minimum useful incident record
For NS_E_WMP_RECORDING_NOT_ALLOWED, capture the recording not allowed state before the Player advances, reloads, rescans or destroys the owning object:
- Decisive check: record the requested action and rights decision separately from file accessibility.
- Artifact: destination directory, temporary file and final rename/replace result for the recording not allowed reproduction.
- State: file attributes, owner, ACL and sharing handles for the recording not allowed reproduction.
- Object identity: bytes received/written, expected length and final hash for the recording not allowed reproduction.
- Underlying evidence: original URL/path and final redirected or canonical location for the recording not allowed reproduction.
- Correlation: HTTP status/content type or local CreateFile-style access outcome for the recording not allowed reproduction.
Logs for the recording not allowed case should retain exact paths or URLs, hashes, object IDs, offsets and HRESULT order where applicable. For recording not allowed, those logs should not contain credentials, protected-license payloads or unrelated library contents.
A narrow remediation path
Resolve NS_E_WMP_RECORDING_NOT_ALLOWED where the recording not allowed state is produced: obtain rights that permit recording or choose content authorized for the operation. After correcting recording not allowed, reload or recreate the owning object so cached failure state is not mistaken for a successful repair.
- Avoid retrying save under a new name without recording the failing destination and access mode while investigating recording not allowed; it can destroy the artifact or state needed to explain
NS_E_WMP_RECORDING_NOT_ALLOWED. - Avoid treating a downloaded error page as a valid playlist, skin or media package; for recording not allowed, that can replace the original HRESULT with a secondary failure from another layer.
Neighboring codes to separate
| Result | Different boundary |
|---|---|
NS_E_DAMAGED_FILE | the media parser identifies structural corruption in a file selected for use |
NS_E_FILE_FAILED_CHECKS | the file fails the Player library admission checks before it can be added |
NS_E_SHARING_VIOLATION | another handle’s sharing mode prevents the required WMP file access |
If NS_E_WMP_RECORDING_NOT_ALLOWED is followed by a broader “cannot play,” “cannot load,” or “operation failed” result, preserve the earlier recording not allowed event. In the recording not allowed case, the later code can be a consequence from a wrapper, fallback item or UI layer rather than the producing failure.
Completion criteria
Repeat the action that returned NS_E_WMP_RECORDING_NOT_ALLOWED and verify that the same object crosses the former recording not allowed checkpoint. For recording not allowed, success means reaching the next expected load, parse, playlist, control or playback state—not merely suppressing a dialog.
A representative failure pattern
Use NS_E_WMP_RECORDING_NOT_ALLOWED, 0xC00D0FC9 and the phrase “recording not allowed” together in traces and issue searches. Keep those keys beside the producing API, object ID, URL or file offset so the recording not allowed event remains distinguishable from a generic Player message.
Technical references
- Supported protocols and file types — normative or platform material relevant to
NS_E_WMP_RECORDING_NOT_ALLOWED. - File name extensions — API or format context for
NS_E_WMP_RECORDING_NOT_ALLOWED. - Windows Media Player SDK — documentation used to identify the producing boundary of
NS_E_WMP_RECORDING_NOT_ALLOWED. - Error handling in the WMP object model — normative or platform material relevant to
NS_E_WMP_RECORDING_NOT_ALLOWED.
Looking for a different code? Search another status or error code.