xp sp1 known problems (so far)
got this off another sitegoes over my head but some may find it usefulEnjoy your XP SP1, ladies and gentlemen!
...unless you encounter "some" of the following "minor" problems:
--------------------------------------------------
This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
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.
© 2002 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
Microsoft Corporation • One Microsoft Way • Redmond, WA 98052-6399 • USA
Table of Contents
XP SP1 Known Issues. 1
Part 1: Setup. 3
Blocked product key prevents XPSP1 for installing – Q326904. 3
Installation Error Message: "The core system file (kernel) used to start this computer is not a Microsoft Windows file…” – Q327101, 327120. 4
Installation Error Message: %REMOVE_NODIR_ERROR% - Q326731. 4
Setup error message: \\update\update.inf “File is not correct”. 5
This application has failed to start because netdtect.dll was not found. 6
Winerror ERROR_INSTALL_FAILURE (1603) 7
System could not allocate the required space in registry log. 8
“This upgrade is for Windows XP Only. You are running Microsoft Windows XP Professional (3604)” 9
Activation Completed” dialog – followed by “You Need To Activate Windows (YES / NO) 9
System Restore Filter generates event error after SP1 update (event ID 1) bug 632640 10
ASound 10/100 Ethernet adapter does not work after upgrading to XPSP1 standalone version. 11
Supported USB 2.0 Host Controller does not work after upgrading to XPSP1. 11
Cannot remove Windows Messenger, Internet Explorer or Media Player – Q327390 11
DVD Playback has frequent glitches, skips or slowdowns since upgrade to Windows XP SP1 12
Toshiba Portege 2000 or 4000 can no longer use Modem after Upgrading to SP1 13
Highpoint 372 disk controller driver removed from XPSP1 integrated media. 13
Warning: that Yamaha AG-XG Audio will not be available or Windows Media Player Error: Cannot play back the audio stream. 14
USB mousse and other devices don’t respond after upgrade to SP1. 14
Toshiba Tecra 9000 continually reboots after upgrading to SP1. 14
Terminal Service Active-X component not downloading. 14
.Cisco: pcx500.sys: Wireless connection roams randomly and incompletely. 15
Mobile Favorites no longer show Thumbnail View.. 16
Roxio Direct CD 5.1 fails writing large files. 16
Intel Application Accelerator 2.3.2135: install makes XPSP1 unbootable. 16
Appendix. 17
KB articles. 17
XP SP1 Known Issues
Part 1: Setup
Blocked product key prevents XPSP1 for installing – Q326904
Windows XP SP1 setup will check for a valid product key.
Issue: If a product keys is identified as invalid the customer will receive the following error message.
Resolution: Purchase valid retail product or purchase a new product key online. XPSP1 will incorporate a new feature which adds a URL link to the activation Window. This URL will allow the customer to purchase a new product key online.
h**p://shop.microsoft.com/Referral/Productinfo.asp?siteID=10798
The following provides the step by step customer scenario:
1. Client enters product key and requests for a license.
2. WPA Clearinghouse will validate the request and if the key has already been used, it will return an error message to client.
3. OOBE will display the following error message to the customer:
“If you believe you have received this message in error, please contact a Customer Service Representative or visit h**ps://productactivation.microsoft.com/req.asp?err=55274785091665122987-1234 For a contact number in your area, click Telephone”
Note the actual text has not yet been defined.
4. Depending on the initial key used, either a retail portal site link or an OEM portal site link is displayed for purchasing new keys.
5. Customer goes to the site and purchases a product key.
6. The new Product Key is used to install on a new box immediately.
Installation Error Message: "The core system file (kernel) used to start this computer is not a Microsoft Windows file…” – Q327101, 327120
Message: "The core system file (kernel) used to start this computer is not a Microsoft Windows file. The Service Pack will not be installed. For more information, see Knowledge Base article Q327101 at h**p://support.microsoft.com".
Customers will receive this message when trying to install SP1 if they have installed BootXP, Windows Theme applications or other applications that replace the Windows kernel. This application replaces the NTOSKRNL.EXE boot file. Customers may see this same behavior with other theme applications as well such a Windows Blinds and StyleXP.
Resolution:
Uninstall 3rd party theme program from Control Panel > Add/Remove Programs. Attempt to reinstall the service pack. If SP1 still fails to reinstall follow steps 4 – 10 in Q327101. Attempt to install the service pack once you have completed those steps.
Installation Error Message: %REMOVE_NODIR_ERROR% - Q326731
Users who are upgrading from Windows XP gold (2600) and who have edited the SYSOC.INF file to enable the removal of Windows Messenger will receive this error message on first logon when upgrading to XP SP1. This only occurs once; clicking OK continues the logon with no further errors.
Setup error message: \\update\update.inf “File is not correct”
Message: \\update\update.inf “File is not correct (Error 0xfffffe0b / error 0x000003e5 / error 0x00000426 as per \Windows\ System32\Catroot2\DBERR.TXT)
1. Error 0xfffffe0b - File C:\Windows\System32\Catroot2\EBD.LOG is damaged. Delete log file.
2. Error 0x00000426 - Cryptographic services are disabled. Re-enable Cryptographic services. Control Panel > Administrative tools > Services > Cryptographic services (double-click) > Start. – Q326815
3. Error 0x000003e5 - NLS entries in the registry contain invalid entries. This is known to have been caused by at least on third party application writing invalid data to the registry. Using regedit, locate and correct the following registry values:
Registry Keys
Correct value
Incorrect value
HKLM\System\CurrentControlSet\Control\Nls\Locale\0
0000C01
"d"
"Arabic (Egypt)"
HKLM\System\CurrentControlSet\Control\Nls\Locale\0
0000409
"1"
"English (American)"
HKLM\System\CurrentControlSet\Control\Nls\Locale\0
000040C
"1"
"French (Standard)"
HKLM\System\CurrentControlSet\Control\Nls\Locale\0
0000407
"1"
"German (Standard)"
HKLM\System\CurrentControlSet\Control\Nls\Locale\0
000041F
"6"
"Turkish (Standard)"
NEW: c:\441cdac5f84bd7b5cd7\update\update.inf file is not correct
NEW: "c:\b48c573\update\update.inf is not correct"
This application has failed to start because netdtect.dll was not found.
Message appears during upgrade: This application has failed to start because netdtect.dll was not found. Re-installing the application may fix this problem.
Machines affected: Dell Dimension 4300s and Dell Dimension 2200 or any workstation with Davicom dm9 series of network adapters. This outdated driver made a call to the Windows DLL, netdtect.dll – even though it doesn’t exist in WinXP (it existed in W2K).
The Windows Update that would cause this problem is the first of the four drivers listed in the screenshot below:
If a user installs this driver, the user will get periodic errors during network activity (in our internal case, when he tried to install WinXP SP1 Beta over his VPN connection, but this is not the only case when it will occur).
Users affected by this, need to download the newer Davicom driver (when it is released) – the version must be greater than 1.38.01.1203. Those installing WinXP SP1 in a few days, will not have the option of downloading this driver since it will be removed from Windows Update within a few days (by 8/18/02). It will re-appear on Windows Update when the newer driver is released.
There is no workaround at present since there is no driver to roll back to. Users should be able to continue setup.
Winerror ERROR_INSTALL_FAILURE (1603)
This is caused by a lack of disk space at the time the installation started and tried to complete resulting in UPDATE.EXE running out of available disk space.
Perform the following steps to free up as much space on your primary partition as possible and retry the upgrade.
1. Remove any unnecessary files you are aware of on your primary partition.
2. Use CLEANMGR to clean up unnecessary files and compress infrequently used files (START | RUN | CLEANMGR)
Perform the following steps to remove unneeded LastKnownGood information that is likely on your system due to the failed installation (the 1603 error)
1. rmdir /S /Q %windir%\LastGood
2. Remove the HKLM,"System\LastKnownGoodRecovery"
3. Run Built-in Disk Defragmenter to reduce fragmentation on your primary partition.
4. Reboot your machine (not just log off/login) to fully recover hidden LKG temporary files.
System could not allocate the required space in registry log
Partition Magic makes changes to the registry. These changes take place during the process of resizing a partition. It is possible other changes made by Partition Magic also make registry changes, but this is only known instance where an issue has come up. This change to the registry has been present when using Partition Magic, however has not caused any known issues that we are aware of in prior releases of our operating systems.
Build 1079 and later versions of the service pack will expose this registry change with an error. When you install Service Pack 1 for Windows XP you will get the following error message. "System could not allocate the required space in registry log."
* Build 1079 presents this error. Build 1050 did not.
* Build 1089 and later builds have a workaround in place for people did not run into this problem with 1079.
Steps to reproduce: Run Partition Magic and resize the partition. When Partition Magic runs it modifies the system hive of the registry.
Partition Magic makes changes to the registry at boot time before the OS is loaded. They rename the registry mounteddevices key.
HKEY_Local_Machine\System\MountedDevices
The MountedDevices key is later renamed back. A new key is left in place MountedDevice1 for trouble-shooting purposes. The way the registry is modified affects the changes in build 1079 when we look at the LastKnownGood entry. The entry is not at the expected location, thus the error is generated. We can work around the issue in the next release of Service Pack 1 by making changes to mounteddevice1 registry key.
Resolution: The built in workaround only applies to systems that did not previously install 1079 and ran across the registry error message. If the user previously had the error. "System could not allocate the required space in registry log." you may not be able to install the service pack unless you restore from an image without any previous 1079 installation failures.
This is due to uninstall failing to complete properly and leaving the system in a partially installed / uninstalled state. If the uninstall actually succeeded, it may very well be possible to install build 1089 or a later version of the service pack. However, all internal attempts to install the service pack after this type of failure were unsuccessful. Booting with last known good also failed to resolve this problem.
This key is not used by the OS and is left on the system only for trouble-shooting. This registry entries will be fully fixed with Service Pack Two for Windows XP and will be fully fixed in Windows .NET. Powerquest is working on resolution that will prevent this from happening and will update their software.
“This upgrade is for Windows XP Only. You are running Microsoft Windows XP Professional (3604)”
Some beta users are still on Windows .Net Professional. Any WINVER that shows “Windows XP Professional”, but has a build number greater than 2600 is running the no-longer-supported Windows .Net Professional code. Examples of WINVER responses and a sample screen shot:
* Build 3615.lab04_N.020306-2210: Service Pack 1
* Build 3605.lab04_N.020306-2210: Service Pack 1
Activation Completed” dialog – followed by “You Need To Activate Windows (YES / NO)
“Activation Completed” dialog – followed by “You Need To Activate Windows (YES / NO)” – which never lets the user into their machine. If the user chooses NO, the user is logged out. If the user chooses YES, the user is stepped through the activation process, but is eventually told that “Windows is already activated (OK)”. When OK is clicked, the user is logged off their machine.
This problem can occur for one of two reasons:
1. The user accidentally enters a Windows XP BETA activation key on a Windows XP RTM (build 2600) workstation.
2. The user simply upgrades to SP1 from an already-activated and functioning version of Windows XP RTM (build 2600.)
In either case, the WINVER will indicate the machine is still on Windows XP RTM (as if the service pack installation hadn’t even occurred).
If the user has accidentally entered an incorrect PID for their platform, the only workaround is to boot into Safe Mode and run the Activation Wizard while obtaining a valid key through telephone-based Microsoft Activation team. The details on this are available in another Primus/Helpdesk article and are not covered here.
If the user has upgraded to SP1 and the problem has occurred, it is important to collect the exact steps the user went through to upgrade their machine to Windows XP SP1 – including what dialogs they saw and when. If escalated, collect the following files from the user’s workstation:
n %WINDIR%\DEBUG\ACTIVATE.LOG
n %WINDIR%\SYSTEM32\$WINNT$.INF
In this case as well, the only workaround is to boot into Safe Mode and run the Activation Wizard while obtaining a valid key through telephone-based Microsoft Activation team.
System Restore Filter generates event error after SP1 update (event ID 1) bug 632640
After updating Windows XP to Service Pack 1 there is an error in the event viewer. The file listed in as being processed may be different to each update of SP1. In this example 'sysaudio.sys' is displayed by event viewer.
Event Type: Error
Event Source: sr
Event Category: None
Event ID: 1
Date: 5/30/2002
Time: 2:57:00 PM
User: N/A
Computer: VT9001D
Description:
The System Restore filter encountered the unexpected error '0xC0000056' while processing the file 'sysaudio.sys' on the volume 'HarddiskVolume2'. It has stopped monitoring the volume.
For more information, see Help and Support Center at h**p://go.microsoft.com/fwlink/events.asp
Need addition info on what causes this, see bug.
Part 2: Non-setup issues
ASound 10/100 Ethernet adapter does not work after upgrading to XPSP1 standalone version.
Windows XP does not natively support the Asound 10/100 Ethernet. Under Windows XP gold 2600 customer will install 3rd party drivers for this adapter. Upgrading to XPSP1 will cause this adapter to no longer function.
Cause: During setup to SP1 using integrated media setup ignores the 3rd party unsigned ASound driver and installs the (SP1 native) signed network adapter driver instead. This signed driver is for the Realtek network adapter and does not work with the ASound network adapter. This driver is installed because ASound uses the same PnP hardware ID as Realtek.
Resolution: Rollback the network adapter driver to the previous working version or reinstall the 3rd party network adapter driver.
Supported USB 2.0 Host Controller does not work after upgrading to XPSP1
After upgrading to XPSP1 supported USB 2.0 Host Controllers still display an exclamation point in device manager and do not function.
Resolution: Remove the unknown device from Device Manager and choose “Scan for hardware changes.” The USB 2.0 Host Controller will be correctly detected and installed.
Cannot remove Windows Messenger, Internet Explorer or Media Player – Q327390
Consent decree feature: Windows XP SP1 provides a new feature in Add/Remove Programs called Set Program Access and Defaults. This feature allows for the configuration of certain Windows programs such as Internet Explorer, Windows Messenger and Media Player. Configuration of these applications can remove specific access from the Start Menu and desktop.
Issue: Customers choose to remove access to Windows Messenger through Set Program Access and Defaults. Messenger will still launch when the customer loads Outlook Express.
Cause: Set Program Access and Defaults does not remove program code from the computer. Certain Windows applications rely on other application code to function correctly. In this example, Outlook Express causes Windows Messenger to load because it looks for the Messenger “contacts” list when launched.
DVD Playback has frequent glitches, skips or slowdowns since upgrade to Windows XP SP1
Occasionally, the installation of Windows XP SP1 will not be able to correctly identify the need for updated DVD drivers for particular brands and vendors DVD playing software. Usually, a dialog box will appear after SP1 installation indicating the web site the user will want to visit to download the latest drivers or software updates. In the case when this dialog does not appear and DVD audio and video playback seems slow or stuttered, it may be necessary to run two command-line tools to trigger DVD driver/software detection for Windows XP compatibility.
To determine if a software upgrade/update is necessary for the user, use the following steps (Note: the user must be a Local Administrator to run these commands):
1. Open a Command Prompt
2. In the Command Prompt, type DVDUPGRD /DETECT – it may take up to 10 seconds for the resulting dialog to appear
3. Once the ‘Detected DVD decoders’ dialog appears, check for a line near the bottom of the dialog for “W2k Upgrade=”. If the ‘W2k Upgrade=” entry =”no”, the software decoder is already on a Windows XP compatible version and troubleshooting will have to proceed using other methods
4. If this entry =”yes”, the DVD decoder software requires an update from the software vendor.
If the software requires an update, have the user type DVDUPGRD /UPGRADE and a resulting UI will appear providing the user access to updated decoder software. No dialog will appear if no upgrade is needed.
After the decoder update has been installed, the user can confirm that the new decoder software in Windows XP compatible by re-running DVDUPGRD /DETECT – and checking for the statement “W2k Upgrade=no” – which indicates that no upgrade is needed.
Toshiba Portege 2000 or 4000 can no longer use Modem after Upgrading to SP1
This problem is caused by insufficient hardware ID detection by Toshiba drivers hosted on the Windows Update site. Updated drivers should be available on Windows Update to resolve the problem, but if correct drivers cannot be found quickly, please refer the user to their original Toshiba Portege pre-installation CD-ROM or to the Toshiba web site – specific for the laptop model being updated – to obtain all 3 necessary (and dependant) Toshiba drivers:
1. Registry for Ali Audio Accelerator (2000 series only)
2. Sound card driver
3. Modem driver
After placing unzipped copies of these drivers into known locations on the user’s workstation, the user can update these drivers through the Windows Device manager – referencing these locations for the updated drivers.
Highpoint 372 disk controller driver removed from XPSP1 integrated media
Highpoint has recently updated the bios on their cards so they no longer work with our inbox (Windows XP) driver. The original Windows XP driver is the same driver as the one that was to be included in XPSP1.
Removing the driver from XPSP1, helps those who upgrade an existing system as the driver will be migrated instead of overwritten and the upgrade will succeed instead of fail. Note: It will make it harder for people installing a new system because they will have to get the driver from Highpoint to get the system installed. h**p://www.highpoint-tech.com
By removing the driver from XPSP1, we fix scenarios 1, 2 and 5. For 3 & 4, customers will need to use F6 to get the driver installed which they would have to do anyway if we did nothing.
1. WinXP -> XP slipstream SP1
2. Win2K -> XP slipstream SP1
3. NT4 --> XP slipstream SP1
4. WinME --> XP slipstream SP1
5. XP slipstream SP1 -> reapply or reinstall XP slipstream SP1
Warning: that Yamaha AG-XG Audio will not be available or Windows Media Player Error: Cannot play back the audio stream.
Message: Warning that “Yamaha AG-XG Audio will not be available after SP1 upgrade” or “Windows Media Player Error: Cannot play back the audio stream; no audio hardware is available, or the hardware is not responding” when trying to play music or view video in Windows Media Player.
This problem will occur on Toshiba 9000/9100 series laptops – which contain the Yamaha AG-XG audio card and drivers. If the user performed an attended installation or upgrade of service pack 1, the user will see the warnings after setup completes to indicate that the audio driver will not work after the upgrade. During an unattended installation the user will see NO warning, but the audio/sound device will be ‘banged out’ (yellow exclamation point) in Windows Device Manager to indicate the current drivers are not installed.
Toshiba – Updated drivers for the Toshiba 9000/9100 series laptops are available now at the Toshiba support web site. They will also be available on Windows Update at some later date (no ETA).
Sony – Updated drivers for the Sony Vaio laptops will be available from the Sony web site once Sony publishes these drivers (no ETA). The correct drivers will be dated more recently than 5/22/02.
The newer drivers should have a version number higher than v3150 for the YACXGC.SYS driver OR higher than v2150 for YACXG.SYS.
Possible workaround for other systems: install the Intel audio driver through Device Manager using the following steps:
1) Update Driver à Choose “Advanced”
2) Hardware Update Wizard à Choose “Don’t search. I will choose the driver to install.”
3) Pick Intel driver when prompted.
USB mousse and other devices don’t respond after upgrade to SP1
Bug 646432
Toshiba Tecra 9000 continually reboots after upgrading to SP1
Text here
Terminal Service Active-X component not downloading
Message: Internet Explorer
Problems with this Web page might prevent it from being displayed properly or functioning properly. In the future, you can display this message by double-clicking the warning icon displayed in the status bar.
[ ] Always display this message when a page contains errors.
[okay] [show details]
If the show details button displays:
Line: 21
Char: 7
Error: Object doesn't support this property or method: 'MsTsc.Server"
Code: 0
URL: h**p://mpslc/tsweb/connect.asp?Server=Servername&UserName=alvinloh@Domain=NTDEV&rW=800&rH=
This occurs because the older GUID of the has been blocked by Internet Explorer
The following GUIDs will not work on XPSP1 IE6.
{1fb464c8-09bb-4017-a2f5-eb742f04392f} - TSAC 1.0 ActiveX control
{791fa017-2de3-492e-acc5-53c67a2b94d0} - Windows XP gold version of this control
{931a8c29-3ea9-494d-91e7-22e9a9247687} - Current .NET builds of the control
The GUID that works today is as follows:
9059f30f-4eb1-4bd2-9fdc-36f43a218f4a
Customers will have to the code snippet in their existing asp pages as follows:
The following is the HTML snippet that illustrates the new GUID
CLASSID="CLSID:9059f30f-4eb1-4bd2-9fdc-36f43a218f4a"
Please note that on application of XPSP1 the connect.asp page is removed and there is only one page that is used to instantiate the control and that is default.htm
Customers that have have XP, apply RDWC and then apply XPSP1 will have the default.htm file in their directory. This won't apply to Windows 2000 customers
.Cisco: pcx500.sys: Wireless connection roams randomly and incompletely
More information: This has been identified as caused by a fragmented RAL packet was causing RAL packet storm between the STA and AP. Reason for initial fragmented RAL packet is unknown, one possibility is that this may result in a scenario with a high AP and STA density, i.e., high likelihood for RF interference. Both the NIC in the STA and the AP are equally impacted by this problem and may initiate the RAL packet storm.
When RAL packet storm occurs network throughput over the RF link deteriorates drastically and the STA may be forced to roam.
Resolution: Firmware updates need to be applied to the NIC in STA and AP however at the time a NIC driver update is not yet available from Cisco.
Mobile Favorites no longer show Thumbnail View
This behavior is by design and is a change from Windows XP RTM. Due to possible security vulnerability, the thumbnail view (which showed web content) has been replaced by a standard Internet Explorer icon. There is no way to restore the old behavior as this was a deliberate change to the Windows XP product.
Roxio Direct CD 5.1 fails writing large files
Steps to reproduce this error:
On a computer with Windows XP 2600 , install Roxio 5.02 then upgrade it to 5.1. Verify the application works by formatting a CD-R using Direct CD and verify functionality with files of various sizes.
Upgrade Windows using SP1. (This issue is exposed in SP builds 1089 and above.) Format a CD-R using Direct CD and verify functionality with files of various sizes. Note that small files and large directories of small files write fine.
When writing large (100 MB+ estimated) files to a Direct CD formatted disc the process hangs indefinitely.
Resolution: Currently there is no fix or workaround for this problem. Customers will need to contact Roxio to determine if/when a fix will be available.
More information: Roxio is aware of this problem but no new information is available. Debugging information was made available to to Roxio on 8/20 shows the problem to be in Roxio’s driver file CDUDF_XP.SYS.
Intel Indeo codec removed from XP SP1 slipstream media
Text here
Intel Application Accelerator 2.3.2135: install makes XPSP1 unbootable
After upgrading Windows XP to SP1 the installation of Intel's Application Accelerator build 2.3.2135 may cause the system to fail to boot back into Windows. Instead it loops at
the F8 screen regardless whether You select Safe mode, Start Windows Normally or Last good configuration. Selecting any of the above causes the system to reboot and return to the same screen repeatedly.
Resolution: Reinstall Windows to a clean directory.
More information: Intel Application Accelerator 2.3.2135 is a beta driver. Intel is aware of this issue and is working wih us to resolve this driver bug.
Appendix
KB articles
n Q326904 Blocked Product Key prevents XPSP1 from installing
n Q327101 Err: The core system file (kernel) used to start this computer
n Q326731 Error message: %REMOVE_NODIR_ERROR% on Reboot after installing XP
n Q326815 "Update.inf is not correct." when installing Windows XP SP.
n Q327389 - Netdtect.dll error when installing Windows XPSP1
n Q327390 - Messenger starts when Outlook Express is Launched.
Reply With Quote
Originally Posted by tobnvodka
) none have had a problem with it once i explained, i realy hope you feel the same (which it appears you do from your reply to marcode).
Social Networking Bookmarks