Issues that are fixed in this update
Issue 1Computer may crash with "0xd1" Stop error when a proxy application redirects UDP traffic.
Issue 2Computer may crash with "0xA" Stop error during logon or logoff.
Issue 3When a computer that is running Windows 8.1 or Windows Server 2012 R2 runs out of or exhausts the number of TCP ephemeral ports, you may experience symptoms that resemble the following:
- The computer crashes, freezes, or hangs.
- The computer can't access the Internet or a network file share.
- The computer can't log on to the domain.
To resolve this problem, apply the update that is mentioned in the "How to get this update" section. After you apply this update, Windows 8 .1 and Windows Server 2012 R2 can reuse ephemeral ports without having to wait for the TIMED_WAIT state to expire.
Note To resolve this problem for Windows 8 or Windows Server 2012, see hotfix 3014399.
Note Windows Server 2016 supports the auto-reuse port range feature by default.
How to use this new featureThis new feature introduces the following two socket option settings:
For a connection scenario to be implemented, the socket option must be set before you bind a socket. This option instructs the system to postpone port allocation until connection time when the 4-tuple (quadruple) for the connection is known.
- Auto-reuse port range
You can set the auto-reuse port range by using Windows PowerShell cmdlets. This separate port range is defined by the following two new TCP template parameters:
For an application to use these new socket parameters, the auto-reuse port range must be defined as in the following example:
Set-NetTCPSetting –SettingName InternetCustom -AutoReusePortRangeStartPort 40000 -AutoReusePortRangeNumberOfPorts 1000
Note Restart requirement: You have to restart the computer after you change the AutoReusePortRange settings for the settings to take effect.
After the restart, you can verify your defined settings using the PowerShell command: