Symptoms

When you establish a connection to a Windows Server 2012-based Remote Desktop Gateway (RD Gateway) server by using a UDP transport, RD Gateway may stop processing the connection.

Notes

  • RD Gateway starts to process the connection again after the RD Gateway service is restarted.

  • When this issue occurs, users cannot connect to the server-hosted desktops by using RD Gateway.

Resolution

To resolve this issue, install update rollup 2876415, or install the hotfix that is described in this article.

This hotfix is also available at Microsoft Update Catalog.

Update information

For more information about how to obtain update rollup 2876415, click the following article number to view the article in the Microsoft Knowledge Base:

2876415 Windows RT, Windows 8, and Windows Server 2012 update rollup: September 2013

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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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.

PrerequisitesTo apply this hotfix, you must be running Windows Server 2012.

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

Restart requirementYou must restart the computer after you apply this hotfix.

Hotfix replacement informationThis 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 2012 file information notesImportant Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.16 xxx

    Windows Server 2012

    RTM

    GDR

  • 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 2012" 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 2012

File name

File version

File size

Date

Time

Platform

Aaedge.dll

6.2.9200.16673

509,952

23-Jul-2013

22:25

x64

Aaedge.mof

Not applicable

1,268

02-Jun-2012

14:30

Not applicable

Aatspp.dll

6.2.9200.16384

81,920

26-Jul-2012

03:04

x64

Aatspp.mof

Not applicable

1,271

02-Jun-2012

14:30

Not applicable

Rap.xml

Not applicable

895

02-Jun-2012

14:30

Not applicable

Tsgateway.xml

Not applicable

429

02-Jun-2012

14:30

Not applicable

Tsgclean.exe

6.2.9200.16384

369,664

26-Jul-2012

03:08

x64

Tsproxy-edgeadapter-ppdlic.xrm-ms

Not applicable

2,910

24-Jul-2013

01:04

Not applicable

Aaedge.dll

6.2.9200.20781

509,952

24-Jul-2013

04:00

x64

Aaedge.mof

Not applicable

1,268

02-Jun-2012

14:30

Not applicable

Aatspp.dll

6.2.9200.16384

81,920

26-Jul-2012

03:04

x64

Aatspp.mof

Not applicable

1,271

02-Jun-2012

14:30

Not applicable

Rap.xml

Not applicable

895

02-Jun-2012

14:30

Not applicable

Tsgateway.xml

Not applicable

429

02-Jun-2012

14:30

Not applicable

Tsgclean.exe

6.2.9200.16384

369,664

26-Jul-2012

03:08

x64

Tsproxy-edgeadapter-ppdlic.xrm-ms

Not applicable

2,910

24-Jul-2013

06:50

Not applicable




Status

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

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

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File property

Value

File name

Amd64_1782713ff4ff1df2b106fea6fea84744_31bf3856ad364e35_6.2.9200.16673_none_3f1bf564ad0630e9.manifest

File version

Not applicable

File size

711

Date (UTC)

24-Jul-2013

Time (UTC)

12:53

Platform

Not applicable

File name

Amd64_66b5814633c343dab7948bd49d27a70c_31bf3856ad364e35_6.2.9200.20781_none_1adf400d85e2a2fb.manifest

File version

Not applicable

File size

711

Date (UTC)

24-Jul-2013

Time (UTC)

12:53

Platform

Not applicable

File name

Amd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.2.9200.16673_none_96ddf022567247b6.manifest

File version

Not applicable

File size

110,435

Date (UTC)

24-Jul-2013

Time (UTC)

12:53

Platform

Not applicable

File name

Amd64_microsoft-windows-tsproxy-edgeadapter_31bf3856ad364e35_6.2.9200.20781_none_975abc6d6f99d0c3.manifest

File version

Not applicable

File size

110,435

Date (UTC)

24-Jul-2013

Time (UTC)

12:53

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×