Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Audio capture redirection feature does not work after a second remote desktop connection is created in Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You enable the audio capture redirection feature on a remote desktop server that is running Windows Server 2008 R2.
  • You create a remote desktop connection to the server.
  • You run an audio recording application in the remote desktop connection.
  • You create another remote desktop connection to the remote desktop server.
In this scenario, the audio recording application stops capturing audio in the first remote desktop connection. To recover from this issue, you have to restart the audio recording application.

↑ Back to the top


Cause

When a new remote desktop connection is created on a remote desktop server, device change events are generated on the computer. These events cause the audio device to receive a new identifier. This new identifier disconnects the device from any existing services or applications that are using the device, and the resetting operation of the device stops audio capture software on the active remote desktop connection.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1).

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.1.760
    1.
    21xxx
    Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Winmm.dll6.1.7601.21718217,60002-May-201105:20x64
Winmm.dll6.1.7601.21718194,04802-May-201105:42x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information about how to configure audio recording redirection on an RD Session Host server, visit the following TechNet website:

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_69660c267e57b7710c81647583a72b8d_31bf3856ad364e35_6.1.7601.21718_none_8e50197e722c3e9f.manifest
File versionNot applicable
File size708
Date (UTC)02-May-2011
Time (UTC)09:09
File nameAmd64_70bc76b1dbe92cf6a37e7180669cddd9_31bf3856ad364e35_6.1.7601.21718_none_d31582571fdee841.manifest
File versionNot applicable
File size1,060
Date (UTC)02-May-2011
Time (UTC)09:09
File nameAmd64_9020e727ca8bb2e401767c7f797b56e0_31bf3856ad364e35_6.1.7601.21718_none_a67cc81bb640ebd4.manifest
File versionNot applicable
File size710
Date (UTC)02-May-2011
Time (UTC)09:09
File nameAmd64_microsoft-windows-audio-mmecore-base_31bf3856ad364e35_6.1.7601.21718_none_149361828169a815.manifest
File versionNot applicable
File size3,188
Date (UTC)02-May-2011
Time (UTC)06:53
File nameX86_microsoft-windows-audio-mmecore-base_31bf3856ad364e35_6.1.7601.21718_none_b874c5fec90c36df.manifest
File versionNot applicable
File size3,184
Date (UTC)02-May-2011
Time (UTC)06:04

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2538047
Revision : 1
Created on : 1/7/2017
Published on : 6/21/2014
Exists online : False
Views : 202