This article describes the Setup problems and update scenarios that are addressed in Microsoft Windows XP Service Pack 2 (SP2).
For additional information about the problems that are resolved in Windows XP Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
List of fixes included in Windows XP Service Pack 2
For additional information about how to obtain Windows XP Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest Windows XP service pack
Windows XP SP2 addresses all the following Setup-related problems and update scenarios.
The default user profile is not updated when you run the Sysprep -reseal -mini command
You can create custom settings for new users by running the Sysprep -reseal -mini
command. The Sysprep -reseal -mini
command copies the settings from the administrator profile to the default user profile. However, when you do this, you may notice that the settings in the default user profile are not updated. If you create a new user profile and then log on to Windows as the new user, the custom settings are not applied to that user's profile.
Update to the Setup program to examine the version of the Ntldr file
This update modifies the Setup program in Windows XP to examine the version of the Ntldr file that is installed on the computer. By examining the version of the Ntldr file, the Setup program can prevent overwriting a later version of the file with an earlier version of the file on computers that are configured to use dual-boot or multi-boot operating systems. For example, if you install Windows XP on one partition, and the version of the Ntldr file that is currently installed on the computer is replaced with a newer version of the file, you cannot start the operating system that is installed to a different partition.
Update to the Out-of-Box Experience (OOBE) feature that lets you control whether the page is displayed that prompts users to turn on the Automatic Updates feature
This update introduces a feature to Windows XP Out-of-Box Experience (OOBE). This feature lets you control whether the page is displayed that prompts users to turn on the Automatic Updates feature.
If you do not want to display the page, set the value of the SKIPAUTOUPDATE
entry to 1
in the [Options]
section of the Oobeinfo.ini file.
If you want to display the page, either remove the SKIPAUTOUPDATE
entry or set the SKIPAUTOUPDATE
entry to 0
"File FileName could not be loaded. Error code is 18." error message when you perform an unattended installation
When you try to perform an unattended installation of Windows XP, and the Unattend.txt file includes the OEMPreinstall = Yes
Setup command entry, you receive the following error message from the Setup program:
File FileName could not be loaded. Error code is 18.
Setup cannot continue.
Press any key to continue.
This problem occurs if the computer supports the OEM Virtual Disk feature, and the Unattend.txt file does not specify any files to be preinstalled. Under these conditions, the Setup loader program does not use the OEM Virtual Disk feature to locate third-party device drivers.
The OEM Virtual Disk feature was created by various original equipment manufacturers. This feature lets you load third-party drivers on the virtual disk for use in unattended installations.
Temporary files are extracted to mapped drives
When you install service packs, or when you apply hotfixes or updates, you may notice that temporary files are extracted to mapped drives.
When you install Windows XP SP2, temporary files are extracted to local drives.
"An error occurred while copying file plylst9.wp_" error message when you install a service pack
When you install a service pack, you may receive the following error message:
An error occurred while copying file plylst9.wp_.
Cannot copy file to destination directory.
Click Retry to retry the operation, or click Cancel.
New functionality by using the /integrate command-line switch
Windows XP SP2 includes new functionality that lets you use the /integrate
command-line switch to integrate hotfixes into Windows installation source files. You can use the new /integrate
switch to integrate software updates, such as security updates, critical updates, and hotfixes, that use Update.exe as the Setup program for Windows installation source files.
For additional information about how to integrate a software update into your Windows installation source files, click the following article numbers to view the articles in the Microsoft Knowledge Base:
How to integrate software updates into your Windows installation source files
Description of the new features in the package installer for Windows software updates
Deployment scripts that use the -ER switch may not return extended error reporting
When you use the -ER
switch together with a deployment script, you may not receive the correct extended error reporting information about failures. This problem may occur when you use Update.exe together with dual-mode hotfix packages.
A "STATUS_USER_CANCELLED" message is returned when you use the incorrect switches
When you use the incorrect switches to apply an update, Update.exe may return a "STATUS_USER_CANCELLED" message.