Share via

Netflix Store App instant crash - Error U7361-1253 (OS Build 22631.3296, ALC897)

David Miller 25 Reputation points
2026-05-13T07:33:44.5133333+00:00

I’m troubleshooting a persistent crash with the native Netflix app from the Microsoft Store. Upon initiating any video playback, the app immediately terminates and throws the U7361-1253 exception.

System Environment:

  • Windows 11 Pro (OS Build 22631.3296)

Intel Core i7-13700H

Realtek ALC897 Audio Codec (Driver version: 6.0.9514.1)

Troubleshooting steps already executed with zero success:

Ran sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth via elevated PowerShell.

Completely purged the app using Remove-AppxPackage and reinstalled.

Disabled all audio enhancements and rolled back to the generic Microsoft High Definition Audio Device.

Event Viewer specifically flags a faulting module in Windows.Media.Protection.PlayReady.dll. The browser version works perfectly. Has anyone successfully isolated this HAL mismatch, or is the native app architecture fundamentally broken on current Windows 11 builds?

Windows for home | Windows 11 | Apps
0 comments

Answer accepted by question author

  1. Wilson Wang 80 Reputation points
    2026-05-14T10:35:55.5966667+00:00

    Hi David, I'm Wilson, PM at StreamFab.

    First off, the community member above is absolutely correct—updating your system to the 25H2 build via the official ISO is the best immediate step, as running a legacy OS Build (22631.3296) often exacerbates driver incompatibilities.

    However, my engineering team tracks these specific media pipeline failures extensively, and you should be prepared for the possibility that the U7361-1253 exception may persist even after the 25H2 update.

    Architectural Root Cause: The Secure Audio Path (SAP) Conflict

    The error you are logging with Windows.Media.Protection.PlayReady.dll is often fundamentally tied to a hardware abstraction layer (HAL) timeout. When the native Netflix app initializes, it attempts to construct a highly restricted Secure Audio Path (SAP) directly to your Realtek ALC897 audio endpoint.

    If there is even a microsecond of DPC (Deferred Procedure Call) latency during this cryptographic handshake—which is incredibly common with OEM audio drivers even on fresh Windows 11 builds—the secure protocol assumes the path is compromised and forcefully terminates the pipeline.

    Alternative Workaround: Direct Local Parsing

    If the ISO update does not resolve the HAL handshake failure, the only permanent solution is to bypass this fragile hardware rendering path entirely.

    By shifting the processing workload away from the strict app container to a direct local parsing engine, you avoid the browser and app rendering overhead that triggers the PlayReady.dll crash.

    Implementation Protocol:

    Initialize Local Parsing Engine: Launch a tool like StreamFab and utilize the integrated streaming portal to access your media library.

    Extract the Raw Stream: Select the desired content. The software utilizes direct local parsing to process the video and audio tracks directly from the source server.

    Save for Offline Playback: The parsing engine will extract the pure media container and compile it into a standard, DRM-free local format (such as an MP4 or MKV file).

    Deploy Local Playback: Open the extracted file using a stable local media player like VLC. Because VLC uses standard WASAPI APIs instead of the restricted SAP, it completely bypasses the U7361-1253 exception.

    Update to 25H2 first, but keep this local parsing method in mind if the rendering architecture continues to fail on your specific hardware configuration.

    Was this answer helpful?

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DaveM121 876.6K Reputation points Independent Advisor
    2026-05-13T08:08:33.58+00:00

    Your Windows build No. (22631.3296) indicates your Windows version is over 3 years out of date and no longer supported, are you not offered the 24H2 or 25H2 updates in the Settings App?

    If not, the most successful method to install version 25H2 is to use the Windows 11 ISO.

    Please ensure you download the ISO in the same language as you use for the Windows UI, follow the steps, this is then not like re-installing Windows, it is just like an update and your personal files, settings and installed software will not be affected.

    You will need at least 40GB of free space on the C drive for the update (this data will be cleared later).

    Click this link:

    https://www.microsoft.com/software-download/windows11

    to download the Windows 11 ISO

    When the ISO file completes downloading

    Disconnect from the Internet

    Disconnect all external devices with the exception of a mouse or keyboard.

    Temporarily disable any 3rd party Anti-virus you may have installed

    Then, in Windows File Explorer, double click the ISO and then run Setup.exe and select the Install option.

    Very Important - ensure you select the option to keep your files and apps.

    Was this answer helpful?

    0 comments
  2. Q&A Assist
    2026-05-13T07:34:02.7066667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The crash during playback with error U7361-1253 and the PlayReady DLL in the faulting module strongly suggests a protected-content (DRM) playback failure, typically tied to audio/video driver or DRM support rather than a fundamentally broken app architecture.

    From the available information, the closest supported guidance is for protected-content playback failures in Store apps, which maps to your scenario (app closes or errors as soon as protected video starts). The documented root causes are:

    1. Video driver not fully supporting DRM or the OS version.
    2. Required Windows updates for protected content not installed.
    3. Misconfigured audio driver/stack.
    4. Hardware/driver that does not support DRM by design.

    Given what has already been tried (SFC/DISM, app reinstall, audio enhancements off, generic audio driver), focus should be on the DRM path and drivers:

    1. Ensure all relevant Windows updates are installed
      • Install all Important/Latest cumulative updates for Windows 11. Similar protected-content issues on earlier Windows versions required specific updates to fix DRM playback.
    2. Verify and correct audio driver configuration
      • The documented fix for protected-content playback failures in Store apps includes ensuring the audio driver is correctly configured and that a specific registry value is not disabling protected audio:
        1. Open Registry Editor (regedit) as administrator.
        2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Audio
        3. In the right pane, look for DisableProtectedAudioDG.
        4. If DisableProtectedAudioDG exists, delete this value.
        5. Close Registry Editor.
        6. Open an elevated Command Prompt and restart the audio service:
          • net stop audiosrv
          • net start audiosrv
          • If that fails, restart the PC to apply the change.
      • This specifically targets cases where protected audio/video content fails due to the audio stack configuration.
      Note: Editing the registry incorrectly can cause serious problems. Back up the registry before making changes (see KB322756 referenced in the documentation) and only proceed if comfortable with advanced troubleshooting.
    3. Update GPU/video drivers with WHQL-certified versions
      • Protected content playback can fail if the video driver does not fully support DRM or is not WHQL-certified for the OS.
      • Steps (adapted from the documented process):
        1. Run dxdiag (Win+R → dxdiag).
        2. On the Display tab, note the GPU name and manufacturer.
        3. Go to the GPU manufacturer’s site and install the latest WHQL-certified driver for Windows 11.
      • USB/virtual display adapters or non-WHQL drivers can break DRM playback in Store apps even if browser playback works.
    4. Ensure the audio driver is stable and current
      • Even though the generic Microsoft HD Audio driver was tested, also test with the latest OEM Realtek ALC897 driver specifically for the device and Windows 11 build.
      • If the OEM driver is already installed, try a clean reinstall of that driver.

    If, after ensuring:

    • All Windows updates are installed,
    • DisableProtectedAudioDG is absent,
    • Audio and GPU drivers are current and WHQL-certified,

    the Netflix Store app still crashes only on DRM playback while browser playback remains fine, the behavior aligns with a DRM/driver interaction issue rather than a general HAL or app-architecture failure. At that point, escalation through Netflix support and/or Microsoft Support would be appropriate, referencing the PlayReady fault and the protected-content troubleshooting already performed.

    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.