Windows XP build 2600.1089
| Build of Windows XP | |
 | |
| OS family | Windows NT |
|---|---|
| Version number | 5.1 |
| Build number | 2600 |
| Build revision | 1089 |
| Architecture | x86 |
| Build lab | xpsp1 |
| Compiled on | 2002-08-01 |
| About dialog | |
Windows XP build 2600.1089 is an unleaked Service Pack 1 beta build of Windows XP. It was released to testers sometime in early August 2002,[1] although the build itself has yet to be found. It is additionally referenced in a Microsoft troubleshooting article documenting PartitionMagic-related registry issues that prevent installation of build 2600.1079, where it is stated that a workaround was implemented in this build.
Only one screenshot of this build is known to exist.[2]
Documentation[edit | edit source]
The below help article is republished here for archival purposes only.
KB article "System could not allocate the required space in registry log":
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.
