Software issue · Evidence-backed record

NDI streaming stutters after KB5063878

TraceCheck source review · Verification method · Request a correction

Direct answer

Microsoft documented uneven NDI audio/video after KB5063878, including in OBS and NDI Tools. The Windows 11 24H2 fix is KB5065426 or a later cumulative update; use the latest applicable update for your device.

Resolved Source: Microsoft

Check affected environmentsFind a remedy for your version

Status
Resolved FACT
Affected
Windows 11 24H2; Windows 10 22H2; Windows 10 21H2
First observed
Unknown
Last verified
Confidence
Vendor confirmed
Severity
Unknown

TraceCheck interpretation

Does this explain your situation?

Use these checks to interpret the source. This is a reading guide, not a device test or a vendor diagnosis.

  1. Match the streaming path, not just the app name

    An OBS problem is not enough to identify this issue. Look for NDI feeds between PCs and the documented lag or uneven audio/video. If you are troubleshooting local capture or a different transport, this record does not establish the cause. Keep the symptom match separate from the diagnosis.

    Source: Microsoft
  2. Keep the originating KB and the fixing KB separate

    KB5063878 identifies the documented starting point on Windows 11 24H2. KB5065426 identifies the historical resolution. The useful question is whether your applicable cumulative update includes that resolution, rather than whether you should install an old KB by name. This record does not identify the latest update available today.

    Source: Microsoft
  3. Do not carry a Windows 11 fix across to Windows 10

    The source lists Windows 10 versions among the affected platforms, but this record links a fixing KB only for Windows 11 24H2. An affected-platform entry and a verified fixing-update entry are different claims. Use the guidance for your exact Windows version; the Windows 10 fixing KB remains Unknown here.

    Source: Microsoft

Symptoms

  • NDI feeds between PCs may lag or deliver choppy audio/video, including under low bandwidth. Source: Microsoft
  • OBS and NDI Tools may be affected, especially with Display Capture on the source PC. Source: Microsoft

Affected environments

Evidence-backed affected targets. An omitted dimension has no recorded conclusion.
EntityVersionOriginating updateEvidence
Windows 1124H2KB5063878Source: Microsoft
Windows 1022H2UnknownSource: Microsoft
Windows 1021H2UnknownSource: Microsoft

What caused it?

Root cause has not been confirmed.

Fixes and workarounds

A version match identifies recorded guidance, not a diagnosis or a guarantee. Check the symptom, device and application requirements in each source before proceeding.

Install the latest applicable Windows 11 24H2 cumulative update

FACT Official fix · vendor fix

Microsoft identifies KB5065426 and subsequent updates as the resolution for Windows 11 24H2. Use the current update applicable to your device. The linked KB is the historical fixing update; this record does not assert that it is today's latest update or the fixing KB for Windows 10.

Documented symptom resolution

Applies to: Windows 11 24H2.

Risk: medium (TraceCheck editorial assessment, not a vendor success rate)

Verification:

Fixing update: KB5065426 · Source: Microsoft

Read Microsoft's instructions ↗

Current status

Resolved This is the recorded state as of the last verification, not a live device diagnosis. Source: Microsoft

Vendor acknowledgement / confirmation: .

Resolution recorded: .

Updates linked to documented corrections: KB5065426

For the recorded vendor guidance, see NDI streaming issue — Windows release health.

Evidence

  1. NDI streaming issue — Windows release health

    Microsoft · Vendor documentation

    Supports: NDI symptoms, affected Windows 11 24H2 and Windows 10 21H2/22H2, opened/resolved times, and Windows 11 KB5065426 resolution.

    Retrieved

Change history

  1. Confirmed → Resolved

    Microsoft records the Windows 11 24H2 issue as resolved by KB5065426.

    Source: Microsoft
  2. Confirmed

    Microsoft opened the issue in release health.

    Source: Microsoft

Browse all issues · Verification methodology