Article ID: 884907 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
When you use Windows Update or use Microsoft Update to intall Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows XP Tablet PC Edition 2005, the installation process may abruptly stop. When this problem occurs, you do not receive an error message.
Note The Windows XP SP2 features and components are included in Windows XP Tablet PC Edition 2005.
Additionally, you may see entries that are similar to the following entries at the end of the Svcpack.log log file:
Note The Svcpack.log file is located in the Windows folder at the root level of your hard disk.
150.782: There is not enough space on the disk. 150.782: Service Pack 2 installation did not complete. 150.782: Update.exe extended error code = 0x70
This problem occurs when there is insufficient hard disk space to download and expand the installation files for Windows XP SP2. Additionally, this problem may occur if you do not have 30 megabytes (MB) of free hard disk space on the first primary system partition. The first primary system partition is the disk volume that contains the hardware-specific files that are required to start Windows. The primary system partition contains the Ntldr file, the Boot.ini file, and the Ntdetect.com file.
For additional information about Windows XP SP2 system requirements, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/837783/ )The hard disk space requirements for Windows XP Service Pack 2
To work around this problem, free sufficient space on your hard disk to install the Windows XP SP2 update files. You can use Disk Cleanup to free hard disk space.
For additional information about using Disk Cleanup, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/310312/ )Description of the Disk Cleanup tool in Windows XP
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.