© 2001 Microsoft Corporation. All rights reserved.
How to Use These Notes |
Back to Top |
These release notes contain important information that was not available when the product documentation for Windows XP was written. This release candidate version of Windows XP is a limited technical release that expires 180 days from the date of installation.
Unless stated otherwise, all information included here applies to the RC1 versions of Windows XP Home Edition, Windows XP Professional, and Windows XP 64-Bit Edition.
You should check whether any of these notes apply to your specific set up. Click the topics above to verify whether there is any important information that might apply. A list of additional resources is included at the end of this document.
Component Services |
Back to Top |
Message Queuing is not supported on Windows 95, Windows 98, or Windows XP Home Edition. If you run MSMQ version 1.0 on Windows Millennium Edition, upgrade to Windows XP Professional in order to continue using Message Queuing.
Product: Windows XP Professional only
On computers running Windows XP Professional, when the IP address of a computer is changed or when the Message Queuing service starts while the computer is off-line, the Message Queuing service stops accepting multicast messages to local queues.
To enable the reception of multicast messages:
This issue will be addressed in a future release.
Taking the Message Queuing service offline has no effect on receiving multicast messages and messages sent using HTTP.
This issue will be addressed in a future release.
Pausing outgoing queues opened for sending multicast or HTTP messages has no effect – the messages will continue to be sent although the queues are paused.
This issue will be addressed in a future release.
You must apply the update QFE MSMQ323 to servers running Message Queue Information Service (MQIS) and MSMQ 1.0 before installing Windows XP clients.
If you are running MSMQ version 1.0 of the dependent client, then your supporting server must be a machine running MSMQ versions 1.0 or 2.0. You cannot install an MSMQ version 1.0 dependent client against an MSMQ version 3.0 supporting server.
General |
Back to Top |
This will not be available in Windows XP until Whistler Server ships.
If your CD recorder (burner) drive is not recognized as a recording drive in My Computer, Windows Media Player cannot be used to create audio CDs.
To verify that your CD recorder drive is recognized, open My Computer, and in the Devices with Removable Storage area, right-click the drive, and then click Properties. If your CD recorder is recognized, you will see a Recording tab.
If you are having problems copying to CDs and your CD recorder is recognized in My Computer, verify that the Enable CD recording on this drive check box is selected in the Properties dialog box for that drive. For detailed instructions, see To set your Windows XP settings to digital mode in the section above.
The Media Library displays all files that have been added by users with accounts on that computer. If you are unable to play content displayed in Media Library, try logging on with a different user account to access those files.
If you are logged on with a Limited user account, you may not be able to play files added by another user.
If tracks that you copied from CDs are visible in Media Library but are silent during playback, change your Windows Media Player and Windows XP settings to digital mode.
To set your playback or copying settings to digital mode in Windows Media Player
To set your Windows XP settings to digital mode
Try your track copying again.
Note
If switching the copy settings to digital adds pops or scratches to copied tracks, use analog mode.
Products: Windows XP Home Edition, Windows XP Professional only
ATI All-In-Wonder analog video capture cards might fail in Windows Movie Maker when switching the Video line input in the Change Device dialog box.
In the Windows Movie Maker Help topic titled "Specifications for recording video only or video and audio", the video display size for the DV-AVI (25 Mbps) profile for PAL devices is inaccurate. The video display size for PAL devices is 720x576 pixels.
If your video device does not appear as the selected source for video input when recording, click the Change Device button and then select your device from the drop-down list. This issue sometimes occurs when a different video device was last used to record in Windows Movie Maker.
If a DV camera is not selected after clicking Yes in the dialog that states that your computer might not provide acceptable performance when recording from a DV device, it might be because:
To resolve this issue, choose the DV camera as the video and audio recording device.
Hardware |
Back to Top |
On computers running Windows XP, the OpenGL installable client driver (ICD) is not installed as standard. Some OpenGL-based programs can run correctly with the display drivers included in Windows XP.
If you have an OpenGL-based program that does not run correctly, contact the video card manufacturer for the latest display drivers.
This issue will not be addressed in a future release.
To work around this issue, reinstall this device using Windows 98 drivers (or later) or contact the device vendor for driver updates.
Products: Windows XP Home Edition, Windows XP Professional only
Laptops from Sony, Acer and Dell that use the 815EM chipset cannot toggle between on-board and external displays in Windows XP.
Products: Windows XP Home Edition, Windows XP Professional only
You must reinstall video capture device drivers after upgrading to Windows XP from Windows 98, Windows 98 Second Edition, or Windows Millennium Edition.
Contact the manufacturer of your video capture device for the latest information on drivers that are compatible with Windows 2000 and Windows XP.
This issue will not be addressed in a future release.
The Linksys Wireless USB Adapter (WUSB11) is not assigned an IP address when used with Internet Connection Sharing. To work around this issue, manually assign an address to the WUSB11 client in the 192.168.0.x range and set gateway and DNS server to point to 192.168.0.1 (the ICS server).
Imaging |
Back to Top |
Following a clean installation of Windows XP, the Canon CanoCraft software for this scanner displays the following error message:
Error Reading SCSI DevicesContact Adaptec for an updated ASPI driver version 4.57 for Windows XP or later.
Use the HP C618 camera in Mass Storage Mode only. The IHV device driver provided with HP software does not work correctly with Windows XP.
Connect the camera directly to your PC to start the Scanner and Camera Wizard.
This scanner fails to scan after upgrading from Windows 98 to Windows XP. Reinstall the driver after upgrade to restore.
Products: Windows XP Home Edition, Windows XP Professional only
For large scans at high resolutions, HP ScanJet 6350 might not scan if you connect it to a computer that does not have enough memory.
To work around this issue, reduce the scan area, color depth, or scan resolution.
This parallel port scanner is not available after upgrade from Windows 95 or Windows 98. To work around this issue, uninstall and then reinstall the scanner software to allow the scanner to work.
This scanner ,might not work with other SCSI devices installed on the same SCSI chain. To work around this issue, remove other devices on the SCSI chain and retry the scan.
When you choose to scan using a parallel port connection, the following error message displays:
Code: -1004, Scanner time out
To work around this issue, change the parallel port settings from Normal to ECP/EPP in BIOS and reinstall the E3 Plus driver.
This scanner is not available after upgrading from Windows 2000 to Windows XP. To work around this issue, reinstall the Microtek IHV driver for Windows 2000.
If you try to install the scanner software using the USB port, an error displays. Contact Microtek to obtain IHV driver version 5.1.
For scanners equipped with an Automatic Document Feeder, the IHV driver intermittently causes the scanner to be missing from the device manager. Other failures, including a system lock up, have been reported. Contact Microtek to obtain the IHV driver version 5.62 or later.
Olympus Camedia version 1.0 does not assign downloaded picture files with a .jpg extension. As a result, transferred files cannot be opened.
To view these files, rename them by adding a .jpg extension to each file name.
The IHV driver for Windows 2000 produces corrupted scans above 300 dots per inch (dpi). To work around this issue, scan at or below 300 dpi.
Transferring pictures from a Ricoh RDC-5300 camera over a serial port to ScanSoft TextBridge Pro 9.0 results in a TWAIN error. Contact Ricoh for driver updates that are compatible with this software.
Products: Windows XP Home Edition, Windows XP Professional only
After upgrading from Windows 2000 to Windows XP, the Image Expert Software provided with this camera no longer copies pictures.
To work around this issue, drag and drop pictures from Image Expert into My Pictures. An error displays the first time you try this, but subsequent attempts are satisfactory.
This scanner shares a Plug and Play ID with the Umax Astra 1200P, causing error messages to display during installation. To work around this issue, install this scanner as a Umax Astra 1200P.
The Umax IHV software, MagicScan version 4.4, produces an error message on installing this device. To work around this issue, unplug the scanner and then uninstall the Windows XP driver. Uninstall the IHV driver and software and then reinstall the MagicScan software and IHV driver. After the computer restarts, plug in the scanner.
The IHV driver for this scanner returns scans with streaks. Contact Visioneer for software updates.
The IHV driver for this scanner times out after 15-30 scans. Contact Visioneer for software updates.
The IHV driver for this scanner sets the status to unavailable during installation. To work around this issue, configure the scanner to use the parallel port.
If this scanner is installed on your computer, you will be prompted to install extra files when you upgrade from Windows 2000 to Windows XP. To work around this issue, click Cancel when these prompts display and continue the installation. After the installation is complete, upgrade the driver for this scanner using the driver provided with Windows XP rather than the IHV driver.
Products: Windows XP Home Edition, Windows XP Professional only
The HP DeskScan II version 2.9 software does not work for many HP scanners. Use the Windows XP inbox scanning software until a new version of the scanner software is available.
Products: Windows XP Home Edition, Windows XP Professional only
If you use Micrografx Picture Publisher 8 with the Agfa PhotoWise 1.52 TWAIN driver, the Acquire function is not available. Contact Agfa to obtain an updated TWAIN driver.
Some custom scanner software programs might be incompatible with PictureIt! 2001 and Greetings 2001 on Windows XP. To work around this issue, use the native Windows scanner option available with PictureIt! 2001 and Greetings 2001.
Some third party scanners, cameras, web cameras, and digital video cameras are not available through My Computer, the Control Panel (Scanners and Cameras), or Device Manager. This is because they do not have native Windows drivers (WIA drivers). These devices use proprietary drivers that are incompatible with the advance digital imaging features of Windows XP.
Network & Communications |
Back to Top |
Windows XP supports Internet Connection Sharing (ICS) and Internet Connection Firewall (ICF). However, settings for ICS and ICF are deleted during upgrades from Beta 2 to RC1. If you want to use these features, you must re-enable them after upgrade. All the settings you were using previously must also be re-entered.
When DNS name resolution builds an IPSec filter list and the DNS name resolves to multiple IP addresses, only the first filter in the list gets applied.
To work around this issue, build the filter list manually using the Microsoft Management Console (MMC) IPSec policy management snap-in.
The following issues will be addressed in a future release of Windows XP:
Support for the NetBIOS Extended User Interface protocols (also called NetBEUI or NBF) in Windows XP has been discontinued.
If your configuration requires temporary use of NetBEUI for Windows XP, follow these steps:
To install the NETBEUI protocol:
Valueadd\msft\net\netbeui\ directory on your Windows XP CD.netnbf.inf into the %SYSTEMROOT%\INF\ directory.Products: Windows XP Professional only
In order to prepare a Risetup image of Windows XP on a Windows 2000 RIS server, you must install hotfix 14021 from the Microsoft Web site.
To prepare a Riprep–based image of Windows XP on a computer running Windows 2000 Server, you must use the version of Riprep included in Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server.
Audience: Network administrators and corporate users where the PAL dialer is the method for remote access
The WorldCom (formerly UUNet Technologies Inc) PAL dial-up client version 4.11 or earlier does not work correctly with Windows XP. For more information, please contact the software vendor.
The Intel NetStructure or Shiva VPN Client version 6.81 or earlier might not send traffic over the VPN after connecting. For more information, please contact the software vendor. A possible workaround is to use the built-in VPN client from Windows XP that is compatible with the Intel/Shiva VPN server for L2TP/IPSec connections. For more information about using the Microsoft client, see Help and Support Center.
Some third party VPN clients work incorrectly after an upgrade from Windows 98 to Windows XP. If you use one of the following products, contact the vendor for a Windows XP-compatible version of their software. The clients affected are:
Products: Windows XP Home Edition, Windows XP Professional only
The existing network settings for your wireless LAN (802.11b) network device might not migrate to Windows XP from your previous version of Windows.
If you are unable to connect to your wireless network after upgrading to Windows XP, verify that your settings are configured using configuration software provided by your wireless network device vendor.
Products: Windows XP Home Edition, Windows XP Professional only
Telnet clients on VTNT terminals must be configured to use TrueType fonts to work properly with East Asian languages. Follow the instructions below for changing your settings before running the telnet client.
To configure command prompt font setting:
Products: Windows XP Home Edition, Windows XP Professional only
The options -s, -m and -k do not work with a remote server when using username and password authentication. This means that the following command does not work: tlntadmn.exe \\host -u host\administrator -p test_abcd -s
To work around this issue:
runas /user:domain\user cmd.exedomain\user credentials. tlntadmn <\\server> -s(specify the option you want to use, without specifying the username and password).
Printing |
Back to Top |
Products: Windows XP Home Edition, Windows XP Professional only
If you send a fax using both an e-mail address and a fax number, a message displays stating that the e-mail cannot be sent because the address is incorrect. However, the fax message is submitted and sent successfully.
This issue will be addressed in a later version of Microsoft Exchange.
If you want to send a fax that includes non-textual content, you cannot copy and paste graphics and tables directly into the fax.
If you want to include non-textual content in the fax transmission, you must include this as a separate file attachment.
There are additional issues with HTML documents:
The issues with HTML documents will be addressed in a future release.
Products: Windows XP Home Edition, Windows XP Professional only
Before upgrading to Windows XP you must uninstall SBS Fax Client, using Add or Remove Programs in Control Panel. If this program is not removed before Windows XP setup begins, the Windows XP installation will be blocked.
After the upgrade, you can add a fax printer connection to reconnect to the SBS Server, and use Windows XP Fax to send and receive faxes using this connection.
Products: Windows XP Home Edition, Windows XP Professional only
When you send a fax from Outlook XP on a computer running Windows XP and use Microsoft Word as the e-mail message editor, Fax Service attributes do not appear on the Tools menu, and you will not be able to specify individual fax settings for the fax being sent. The fax will be sent using the default fax settings for Outlook XP. These default settings include a selected fax printer, cover page template, and method of delivery notification.
To change the default fax settings:
If you modify the default fax settings, you must exit Outlook XP and restart it, or else your normal e-mail messages will not be delivered.
Products: Windows XP Home Edition, Windows XP Professional only
In the English-only version of Fax Service, personal fax cover pages that use Asian characters display the characters incorrectly. To work around this issue, follow the procedures below. Please note that the computer must be configured for multiple languages.
To change a personal fax cover page to display Asian characters correctly
To save the modified cover page
To configure your computer for multiple languages:
Products: Windows XP Home Edition, Windows XP Professional only
If you use Send Fax Wizard with a language other than the system default location language, the characters in the To field display as ?. For example, this problem occurs if your system is set to English (United States) and you want to include a recipient with a Japanese name. To work around this issue, follow the procedure below.
To change the system location language:
You will have to manually change the default system location language back to your original settings once you have entered the recipient's name.
These printers do not support receiving using PC Fax. This applies to all models marked with a J, such as the MFC-9200J.
Only walk-up receive fax is available for these specific devices. All other Brother devices are unaffected, and will send and receive PC Fax with Fax Services.
If you have a Brother multifunction printer and are using the Brother driver included with Windows XP, your Brother device will not support PC Fax. You must install this functionality manually.
To install PC fax functionality for your Brother multifunction printer:
Security |
Back to Top |
A Windows XP client cannot enroll for a certificate from a Certification Authority running Whistler Beta 2 Server.
This issue will be fixed in a future release of Whistler Server.
Product: Windows XP Professional only
When NTLM authentication (for domain accounts) is used on a remote computer that serves HTTP requests to a local computer with ForceGuest enabled, authentication is restricted. The registry key is HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Lsa\ForceGuest and is by default set to 1. When NTLM is used on the local computer, this restriction does not apply. Other security methods are not restricted. The ForceGuest registry setting can be set as the local security policy to "Force Network Logons using Local Accounts to authenticate as Guest" for network access.
When you configure a Windows XP workstation to log on using a non-Windows Kerberos realm, the host principal for the computer is no longer required.
If the Kerberos realm configuration is supplied by Ksetup and a suitable account mapping is available, a user can logon to the workstation using a Kerberos principal. This only works when the computer is not a member of a domain.
To access the logon dialog when using friendly logon, press Control-Alt-Delete twice, then supply the Kerberos principal name for the user and the password. The system logs you on to the local account mapped to the Kerberos principal name.
Windows XP Home Edition cannot be used for Kerberos authentication to services when a computer is using a non-Windows Kerberos realm. However, other Windows XP products can. For more information, see the step-by-step guide on Kerberos Interoperability at the Microsoft Web site.
Windows XP allows application developers to replace the authentication user interface (GINA).
Applications that replace this user interface typically support non-standard authentication types (such as biometrics) or provide helpdesk remote control functionality. Such applications designed for systems prior to Windows XP have the potential to render the system unusable. In addition, in replacing the Microsoft GINA, you might remove support for features such as the Friendly logon user interface and Fast User Switching.
Contact the vendor for an updated version of these applications.
Windows XP includes a Terminal Server client that can be used on Windows XP or Windows 2000 computers. However, the client will only allow smart card redirection to computers running Windows XP Terminal Server.
Server Management |
Back to Top |
The 32-bit versions of the Windows Management Instrumentation (WMI) providers, including High-Performance providers, are not supported in Windows XP 64-Bit Edition. Any attempt to connect to such providers from the client will result in an error.
Software Applications |
Back to Top |
See Windows XP 64-Bit Edition Only for additional information on 64-bit software issues.
Products: Windows XP Home Edition, Windows XP Professional only
On computers running Windows XP Home Edition or Windows XP Professional, only antivirus programs written for the specific operating system run correctly. Antivirus drivers not written to run on the specific Windows XP operating system might cause problems. Other issues might include a lack of real-time scanning for viruses or system vulnerability to virus attack. These problems range in severity from recoverable errors to loss of some or all of the data, to the computer becoming unusable. Contact your antivirus software vendor for updates.
The Collaboration Data Objects for Windows 2000 (CDOSYS), which implements version 2.0 of the CDO API specification, is a Component Object Model (COM) component. This is designed to simplify writing programs that create or manipulate Internet messages.
Applications that are currently using CDONTS are incompatible with this version of Windows XP. For information on CDOSYS, see the Microsoft Web site.
Products: Windows XP Home Edition, Windows XP Professional only
When this program attempts to install Adobe PostScript printer drivers on Windows XP, the following error message displays:
The procedure entry point SUnMapLS_IP_EBP_32 could not be located in the dynamic link library KERNEL32.dllContact Adobe for updated printer drivers.
Products: Windows XP Professional and Windows XP 64-Bit Edition only
On computers running Windows XP Professional and Windows XP 64-Bit Edition, users might experience problems using Adobe Photoshop 5.5 if the computer has an Intel Pentium 3 microprocessor.
While using Adobe Photoshop 5.5, the system stops responding. The electrical problem on the affected motherboards is triggered by computer operations that use the pathway (called a bus) between the processor and the random access memory (RAM) for an extended number of microseconds. The operating system or other programs can cause this problem; however, it often appears when using Photoshop because few other programs move memory as rapidly as Photoshop does.
Some Photoshop extensions optimize the way Photoshop moves data. Although removing or disabling these extensions can reduce the problem in some computers, this workaround is temporary because it slows the processing speed of Photoshop. This issue occurs with Dell Optiplex GX1 computers and ASUS P2B-F and P3B-F motherboards and might also occur with other motherboards.
If the computer manufacturer is Dell Computer Corporation, the computer might return the error, "Alert: Regulator Error." There are three possible workarounds to this issue:
Option 1
Option 2
Note
Perform this procedure if the computer has only one processor. Moving the Extensions folder disables the extensions in the folder that optimize data movement by Photoshop. After you move the extensions, Photoshop 5.5 performance slows noticeably.
Option 3
Note
Perform this procedure if the computer has multiple processors. The MMXCore and FastCore plug-ins optimize data movement by Photoshop. After you move the extensions, Photoshop 5.5 performance slows noticeably.
Products: Windows XP Home Edition, Windows XP Professional only
Calypso Mail versions 3.1 and 3.10.03 will not run correctly on Windows XP Home Edition or Windows XP Professional. Any attempt to configure a mailbox during or after installation of Calypso will result in loss of functionality. Without the ability to configure the mailbox, the application loses its primary functionality. There is no known workaround at this time.
Products: Windows XP Home Edition, Windows XP Professional only
User might not be able to scan when using HP scanners with PageKeeper Pro version 3.0. When using HP scanners with PageKeeper Pro, the application might not recognize the installed scanner or the user might experience issues when scanning. To work around this issue, try the following.
After installing the scanner and PageKeeper Pro version 3.0:
This error can be ignored and will stop appearing when the user opens a file from My Webs.
Storage |
Back to Top |
Local device drive names (a letter of the alphabet) are usually assigned incrementally starting from the letter C, and network drive names are automatically assigned starting from Z in reverse order (Z, Y, etc.).
Drive letter conflicts with existing network shares might result when connecting digital cameras or other consumer devices that use memory sticks to Windows XP while the computer is turned on. The same conflict might occur when adding external drives (such as USB or 1394 disks). In the event of a naming conflict with an existing network share, the local device will not be accessible.
To work around this issue, allow Windows to automatically assign network drive names or choose drive name letters later in the alphabet.
Products: Windows XP Professional, Windows XP 64-Bit only
NTBackup reports an error when backing up to 8mm AME tape on EXABYTE EXB-220 changer. To work around this issue, upgrade the firmware (latest firmware is 6.4.3).
Products: Windows XP Professional, Windows XP 64-Bit only
Backup operator does not have the ability to format or partition removable media. This task requires administrative rights since there is a possibility of loss of data. Once the media is formatted, the backup operator might utilize the media for the purposes of backup.
Tapes created using software compression in Windows 98 cannot be read using NtBackup The software compression used in Windows 98 is incompatible with Windows 2000 and later. If the tape is created using non-compressed mode, the media will be readable.
Products: Windows XP Professional, Windows XP 64-Bit only
Recall notifications from a computer running Windows 2000 Server do not work when Windows XP clients access a Remote Storage truncated file.
Windows XP does not support legacy Windows NT version 4.0 Ftdisk volume sets. If you are running Windows 2000, you must convert all Ftdisk volume sets to dynamic volumes before upgrading to Windows XP. If you are running Windows NT version 4.0, you should break any mirrors and back up all data on stripe, RAID5, or extended volume sets before upgrading to Windows XP. Ftdisk sets might not be accessible after the upgrade.
Other |
Back to Top |
From January 1, 2002, the euro will be the common currency for the following countries or regions: Austria, Belgium, Finland, France, Germany, Greece, Ireland, Italy, Luxembourg, Monaco, Netherlands, Portugal, and Spain.
If you set your standards and formats to one of these countries or regions during a clean installation of Windows XP, then your version of Windows XP will use the euro as the default currency.
All new documents created on your computer will use the euro symbol and not your previous local currency symbol. For example, in France "€" will now be the default currency instead of "F". All documents and files created previously with a different default currency will preserve the original settings. If you want these files to use the euro, you will have to manually change each of them.
If you are performing an upgrade from a previous version of Windows, then your current user settings (including your currency settings) will be preserved. To change your currency setting to the euro, follow the steps below but replace the local currency symbol with the euro symbol (€).
To revert to the default local currency settings:
For more information about the euro, see Help and Support Center or visit the Microsoft Web site.
Windows XP 64-Bit Edition Only |
Back to Top |
Computers running Windows XP 64-Bit Edition do not support 32-bit device drivers.
Some 32-bit applications ship with device drivers that are not supported by the 64-bit kernel. These applications will not function properly and might cause an error during installation or operation. Most 32-bit antivirus programs fall into this category and should not be loaded on computers running Windows XP 64-Bit Edition.
Windows XP 64-Bit Edition includes basic support for multifunction print devices. Other device driver functions such as scan, fax, and storage are not supported by the inbox drivers included with Windows XP 64-Bit Edition. Contact the hardware vendor for updated 64-bit drivers.
QLogic 1280 SCSI controllers with firmware versions lower than 1.30 do not support BIOS Enhanced Disk Drive Services (EDD) version 3.0 correctly. If you have a QLogic 1280 SCSI controller running a firmware version lower than 1.30, the following error message displays during installation of Windows XP 64-Bit Edition:
GetEddsSector: Error Reading Media!To resolve this issue, update the firmware on your QLogic controller. Contact Qlogic for more information.
Support for IPX/SPX networking protocol is not implemented in Windows XP 64-Bit Edition. To work around this issue, use x86-based (32-bit) hardware for IPX/SPX functionality.
Please note that support for IPX/SPX protocol is being phased out in future versions of Windows.
Windows XP 64-Bit Edition is not supported as a Remote Installation Services (RIS) client.
Windows XP 64-Bit Edition does not support most 16-bit DOS, Windows, and OS/2 applications. This is significant to applications where the initial setup.exe is a 16-bit stub which checks the machine type, then launches a 32-bit install engine to perform the install.
On computers running Windows XP 64-Bit Edition, certain proprietary 16-bit applications do not run correctly and might affect other applications.
Programs that use 16-bit Microsoft ACME Setup versions 2.6, 30.0, 3.01, and 3.1 and InstallShield versions 5.x should install without error.
The 64-bit default browser for Windows XP 64-Bit Edition will not load 32-bit plug-ins. However, a 32-bit version of Internet Explorer (IE) is included with Windows XP 64-Bit Edition.
To use the 32-bit version of IE in Windows XP 64-Bit Edition:
On computers running Windows XP 64-Bit Edition, after launching ActiveSync and clicking on the Explore icon, the following message will appear:
The path does not exist or is not a directory.ActiveSync relies upon 32-bit Explorer shell extensions. On Windows XP 64-Bit Edition, the 64-bit Explorer is the default shell.
This software is incompatible with Windows XP 64-Bit Edition.
During setup of VMWare version 2.03, you might receive the following message during setup:
No Ethernet adapter cards were located on your system. This may be due to improper installation of an adapter. The network adapters on your system will be rescanned and any with an unspecified media type will be presented for use in bridge networking. Beware that Ethernet adapters can be used with bridged networking support. If you select a non-Ethernet adapter the service will not function correctly.
This program does not recognize the network adapter and should not be installed on Windows XP 64-Bit Edition.
Windows XP 64-Bit Edition does not have a native 64-bit version of the Administration Tools Pack (Adminpak.msi). You can access native 64-bit server administration tools through 64-bit desktops by connecting the client through Remote Desktop to any 64-bit server that has the applicable tools installed.
Setting illegal registry values and executing illegal instructions on computers running Windows XP 64-Bit Edition might cause the operating system to stop responding or stop at a kernel-mode breakpoint. This happens because debugging tools are turned on by default and the system is designed with numerous breakpoints in order to catch bugs.
To work around this issue, turn off the kernel debugger. You can do this by removing the proper start options in the Start Manager. This might reduce the probability of issues caused by debugging tools. Note that Windows XP 64-bit Edition should not be deployed in environments where these actions might result in loss of data or in which unauthorized personnel can gain access to the computer.
Additional Resources |
Back to Top |
To review the latest application compatibility information, see the Windows Hardware Compatibility Web site.
To review the most up-to-date information for Windows XP, see the Microsoft Knowledge Base on the Microsoft Product Support Services Web site
To obtain the latest product updates, go to the Windows Update Web site.
Copyright |
Back to Top |
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.
Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2001 Microsoft Corporation. All rights reserved.
ActiveSync, Microsoft, MS-DOS, NetMeeting, Outlook, PictureIt!, Windows, Windows Media, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.