Merge pull request #2828 from MicrosoftDocs/main

Merging main into live to publish loopback recording update

Author: drewbatgit

desktop-src/CoreAudio/loopback-recording.md

@@ -3,7 +3,7 @@ description: Loopback Recording
 ms.assetid: 71c567f7-fffa-4b75-897a-63ed30c4c9b0
 title: Loopback Recording
 ms.topic: concept-article
-ms.date: 05/31/2018
+ms.date: 04/16/2025
 ---
 
 # Loopback Recording
@@ -70,8 +70,6 @@ Windows Vista provides digital rights management (DRM). Content providers rely o
 
 WASAPI loopback by default contains the mix of all audio being played, regardless of the Terminal Services session the audio originated from. For example, you can run a loopback client in a service running in session 0 and capture audio from all user sessions, as well as audio being played from session 0.
 
-Starting in Windows 10 Build 20348 you can include or exclude specific processes and their children from loopback capture by passing an [AUDIOCLIENT_ACTIVATION_PARAMS](https://learn.microsoft.com/windows/win32/api/audioclientactivationparams/ns-audioclientactivationparams-audioclient_activation_params) in the call to IMMDevice::Activate. See the [Application loopback audio capture sample](https://learn.microsoft.com/samples/microsoft/windows-classic-samples/applicationloopbackaudio-sample/).
-
 Remote Desktop allows redirecting audio to the client. This is implemented by creating new audio devices that only appear for that session.
 
 ## Related topics