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
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 (http://support.microsoft.com/kb/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.

Click here for more details.