Wireless update rollup package for Windows XP is available (826942)

SUMMARY

Microsoft has released an update rollup package for Microsoft Windows XP that includes the hotfixes and updates that are described in the following list. The hotfixes and updates that are included in this rollup package are also included in Windows XP Service Pack 2. For more information about the latest service pack for Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

This small, comprehensive rollup of updates is an easy mechanism for managing the rollout of wireless fixes.

The following problems are resolved by this update:

You experience a long delay when you connect to a wireless network

When you connect to a wireless network by using 802.1x authentication, your network connection may take between 30 and 60 seconds to be established. This problem occurs because the Wireless Zero Configuration service is delayed when it tries to start. The Wireless Zero Configuration service does not start in a timely manner because it depends on the NETMAN component, but the NETMAN component has not yet been loaded at startup.
An incorrect media status appears for the wireless interface

When your computer is the only computer in a wireless network that is in ad-hoc mode, the wireless network connection icon may incorrectly show that the wireless network adapter is connected.
User interface items are incorrectly translated in other languages

Several user interface items in the Windows XP Support Patch for Wireless Protected Access (WPA) package that is described in the following Microsoft Knowledge Base article are incorrectly translated in some Asian languages:
815485 Overview of the WPA wireless security update in Windows XP
WPA does not work correctly in mixed AES/TKIP modes

WPA does not work correctly with an access point that is configured for Advanced Encryption Standard (AES) encryption for unicast transmission and for Temporary Key Integrity Protocol (TKIP) encryption for broadcast transmission.
WPA defaults to a weaker encryption scheme

By default, when a wireless client is offered the ability to connect to a wireless network by using the TKIP encryption scheme or by using the AES encryption scheme, the client selects the weaker encryption scheme.
Wireless networking client incorrectly responds to an RC4 key message in non-WEP mode

When you connect to a wireless connection that is encrypted by using the AES encryption, Windows incorrectly responds to an RC4 encryption algorithm message.
Cannot reconnect to the preferred network after an unsuccessful key exchange

When a wireless client key exchange operation is unsuccessful, the client fails the connection and blocks any attempts to automatically reconnect. You must then manually try to reconnect to the wireless network.
802.1x failure counter is not reset after a successful key exchange

The Wireless Zero Configuration service maintains a counter of unsuccessful authentication and key exchange attempts. However, when a wireless client successfully authenticates and performs a key exchange, this counter is not automatically reset.

This update also resolves the problems that are described in the following Knowledge Base articles:

822596 DHCP does not obtain a new address when EAP reauthenticates across access points with IP subnets that differ

826239 Small delay in logon to network when you use a wireless network connection

Note This update excludes a dependency on Nwlinkipx.sys that will cause Internet Explorer to stop responding when IPX Configurations are changed on a system that has hotfix Q826942 applied. Apply Q834565 after Q826942 to address the issue with the missed dependency.

MORE INFORMATION

Prerequisites

This update requires Windows XP Service Pack 1 (SP1). For more information about how to obtain the latest Windows XP service pack, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

Restart requirement

You must restart your computer after you install this update.

Update replacement information

This update rollup package does not replace any other updates.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows XP, 32-bit versions

   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   09-Feb-2004  20:53  5.1.2600.1331      99,840  Dhcpcsvc.dll     
   06-Feb-2004  21:01  5.1.2600.1331     168,192  Ndis.sys
   10-Jan-2004  13:33  5.1.2600.1331      12,416  Ndisuio.sys
   09-Feb-2004  20:53  5.1.2600.1331   1,630,720  Netshell.dll     
   10-Jan-2004  13:34  5.1.2600.1331      84,864  Nwlnkipx.sys
   09-Feb-2004  20:53  5.1.2600.1335      57,344  Wzcdlg.dll       
   09-Feb-2004  20:53  5.1.2600.1335      31,232  Wzcsapi.dll      
   09-Feb-2004  20:53  5.1.2600.1335     282,112  Wzcsvc.dll       
   29-Jan-2004  00:57  5.1.2600.1337     586,752  Xpsp2res.dll

Windows XP, 64-bit versions

   Date         Time   Version            Size    File name    Platform
   --------------------------------------------------------------------
   09-Feb-2004  20:03  5.1.2600.1331     308,736  Dhcpcsvc.dll     IA-64
   10-Jan-2004  12:25  5.1.2600.1331     579,328  Ndis.sys
   10-Jan-2004  12:25  5.1.2600.1331      40,960  Ndisuio.sys
   09-Feb-2004  20:03  5.1.2600.1331   2,736,128  Netshell.dll     IA-64
   10-Jan-2004  12:25  5.1.2600.1331     329,856  Nwlnkipx.sys
   09-Feb-2004  20:53  5.1.2600.1331      99,840  Wdhcpcsvc.dll    x86
   09-Feb-2004  20:53  5.1.2600.1331   1,630,720  Wnetshell.dll    x86
   09-Feb-2004  20:53  5.1.2600.1335      57,344  Wwzcdlg.dll      x86
   09-Feb-2004  20:53  5.1.2600.1335      31,232  Wwzcsapi.dll     x86
   09-Feb-2004  20:53  5.1.2600.1335     282,112  Wwzcsvc.dll      x86
   29-Jan-2004  00:57  5.1.2600.1337     586,752  Wxpsp2res.dll    x86
   09-Feb-2004  20:03  5.1.2600.1335     117,760  Wzcdlg.dll       IA-64
   09-Feb-2004  20:03  5.1.2600.1335      65,024  Wzcsapi.dll      IA-64
   09-Feb-2004  20:03  5.1.2600.1335     687,104  Wzcsvc.dll       IA-64
   29-Jan-2004  00:57  5.1.2600.1337     586,240  Xpsp2res.dll     IA-64

Installation information

The standard version of this update supports the following Setup options:

/? Show the list of installation options.
/u Use Unattended mode.
/f Force other programs to quit when the computer shuts down.
/n Do not back up files for removal.
/o Overwrite Original Equipment Manufacturer (OEM) files without prompting.
/z Do not restart when the installation is complete.
/q Use Quiet mode (no user interaction).
/l List the installed hotfixes.
/x Extract the files without running the Setup program.

Additionally, this update supports the command-line commands that are described in the following Knowledge Base article:

824687 Command-line switches for Microsoft software update packages

To verify that this update rollup is installed, use the Qfecheck.exe tool. For more information about the Qfecheck.exe tool, click the following article number to view the article in the Microsoft Knowledge Base:

282784 Qfecheck.exe verifies the installation of Windows 2000 and Windows XP hotfixes

You can also verify that this update rollup is installed by confirming that the following registry subkey exists:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP2\KB826942

Note When you install this update rollup, any existing entries in the Add or Remove Programs dialog box are removed for the critical updates that are included in this update rollup package. Because of this, some tools may report that some of the included critical updates are not installed. For example, Marimba Software Change-Management solutions use the registry entries for the Add or Remove Programs tool that are associated with each critical update to confirm that the update is installed. Therefore, Marimba Software Change-Management solutions may incorrectly report that you are missing the individual critical updates that are included in this update rollup package.

Deployment information

To install this update without any user intervention, use the following command:

windowsxp-kb826942-x86-enu.exe -u -q

To install this update without forcing the computer to restart, use the following command:

windowsxp-kb826942-x86-enu.exe -z

Note You can combine these options in one command line.

Removal information

To remove update rollup 826942, use Add or Remove Programs in Control Panel.

Note When you install this update, any existing entries in the Add or Remove Programs dialog box are removed for the critical updates that are included in this update rollup package. When you remove this update, the previous entries in the Add or Remove Programs dialog box for the individual critical updates that are included in this update rollup are restored.

System administrators can use the Spuninst.exe tool to remove this update. Spuninst.exe is located in the %Windir%\$NTUninstallKB826942$\Spuninst folder. The utility supports the following Setup switches:

/? Show the list of installation switches.
/u Use Unattended mode.
/f Force other programs to quit when the computer shuts down.
/z Do not restart when the installation is complete.
/q Use Quiet mode (no user interaction).

You may also be able to verify that this update rollup is installed by confirming that the following registry subkey exists:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP2\KB826942\Filelist

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

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

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.