Hotfix increases the 64K limit on RIO buffers per process for Azure service in Windows

This article describes a hotfix that increases the limit of 65,536 (64K) per process on Registered Input/Output (RIO) buffers in Windows RT 8.1, Windows 8.1 or Windows Server 2012 R2. Before you apply this hotfix, notice that this hotfix has a prerequisite.

About this hotfix

After a process allocates approximately 65,535 RIO buffers, additional allocations that use RIORegisterBuffer fail with the "WSAETOOMANYREFS" error code. To avoid this situation, an internal limit on RIO buffers per process is increased.

Get the hotfix for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2

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.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

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

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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, 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.3.960 0.17 xxx

    Windows RT 8.1, Windows 8.1 and Windows Server 2012 R2

    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" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 x86-based versions of Windows 8.1

File name

File version

File size

Date

Time

Platform

Afd.sys

6.3.9600.17663

462,848

19-Jan-2015

23:24

x86

For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File name

File version

File size

Date

Time

Platform

Afd.sys

6.3.9600.17663

559,104

19-Jan-2015

23:25

x64

For all supported Windows RT 8.1

File name

File version

File size

Date

Time

Platform

Afd.sys

6.3.9600.17663

448,000

19-Jan-2015

23:22

Not applicable

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1

File property

Value

File name

X86_f8b59fbf99cd525f7fbba137e61ee5c8_31bf3856ad364e35_6.3.9600.17663_none_0e61a3b356a34da4.manifest

File version

Not applicable

File size

700

Date (UTC)

21-Jan-2015

Time (UTC)

00:49

Platform

Not applicable

File name

X86_microsoft-windows-winsock-core_31bf3856ad364e35_6.3.9600.17663_none_6c9c959179f7746b.manifest

File version

Not applicable

File size

103,917

Date (UTC)

20-Jan-2015

Time (UTC)

00:10

Platform

Not applicable

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

File property

Value

File name

Amd64_882aa7d8544955b7b579c52c3d0af980_31bf3856ad364e35_6.3.9600.17663_none_c8bd999d38f4934f.manifest

File version

Not applicable

File size

704

Date (UTC)

21-Jan-2015

Time (UTC)

00:49

Platform

Not applicable

File name

Amd64_microsoft-windows-winsock-core_31bf3856ad364e35_6.3.9600.17663_none_c8bb31153254e5a1.manifest

File version

Not applicable

File size

103,921

Date (UTC)

20-Jan-2015

Time (UTC)

00:24

Platform

Not applicable

Additional files for all supported Windows RT 8.1

File property

Value

File name

Arm_cda32301cd6b51bb86848c1b606d5f61_31bf3856ad364e35_6.3.9600.17663_none_7fc181d3d2c18810.manifest

File version

Not applicable

File size

700

Date (UTC)

21-Jan-2015

Time (UTC)

00:49

Platform

Not applicable

File name

Arm_microsoft-windows-winsock-core_31bf3856ad364e35_6.3.9600.17663_none_6c9f07e979f49331.manifest

File version

Not applicable

File size

103,917

Date (UTC)

19-Jan-2015

Time (UTC)

23:54

Platform

Not applicable


Status

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

References

See the terminology that Microsoft uses to describe software updates.

Need more help?

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

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×