Hi SO-2998,
Thank you for reaching out to Microsoft Q&A forum. I understand how inconvenient it can be when audio stops unexpectedly partway through a screen recording.
I can see that Q&A Assist has already shared some helpful steps, and I’d like to add a few additional recommendations that may also help.
Step 1: Find where the audio stops in the recording
Please open the video in a media player or editor that shows the audio waveform. Take a look at the timeline and note where the waveform goes flat or ends. This helps us understand whether the audio stopped all at once or gradually faded, which can give some clues about what caused it.
Step 2: Check for any changed that was made during the recording
If you can, try to recall whether anything happened during the session—such as Bluetooth headphones reconnecting, the screen locking, the system going idle, or a brief connection hiccup. Even short interruptions like these can cause the recorder to lose the audio input while continuing to capture the video.
Step 3: Consider whether the system briefly took over audio
Sometimes a call notification, meeting reminder, or system alert can temporarily redirect audio. When that happens, the recording may keep running, but it may no longer receive sound after that moment.
If the audio track ends or stays completely silent after the point where the interruption occurred, that means the audio wasn’t captured during that portion of the recording. Unfortunately, audio that wasn’t recorded can’t be restored afterward.
To help avoid this in future recordings, I recommend keeping the same audio devices connected throughout the session, avoiding locking the screen while recording and doing a quick check at the start to make sure audio is actively being captured.
In case the audio continues to cut out, we can also try testing in a clean boot environment. This starts Windows with only essential services running and helps rule out background apps or services that may be interfering with audio during recording. If the recording works correctly in a clean boot, it usually means a third‑party app or service is causing the conflict.
*Disclaimer: A "clean boot" starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem.
These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by-step so that it will help you get back on track.
I hope this helps.
Please feel free to contact me if you have any further questions. I am here to help.
If you have any further questions regarding this answer, please click "Comment".
Note: If you'd like to receive email notifications about this chat, follow the steps in our documentation to enable email notifications.