DISCLAIMER:
This piece of information is largely based on information from Microsoft, but neither i or Microsoft are responsible for any damages that may occur from using this piece of information.

48-Bit LBA Support for ATAPI Disk Drives in Windows 2000 and XP

The information in this article applies to:
sob sob
This article was previously published under Q305098

SYMPTOMS

Windows 2000 Service Pack 2 (SP2) and earlier versions of Windows 2000 and some versions of Windows XP do not support 48-bit Logical Block Addressing (LBA) as defined in the ATA/ATAPI 6.0 specification.

Even if you get Windows to recognize the large drive, once you've written more than 128 Gb data on it, you will start getting corrupted files and at some point you might even get an entire corrupted disk.

RESOLUTION

To resolve this problem, run this and obtain the latest service pack for Windows 2000 or XP. For additional information, click the following article number to view the article in the knowledge base:

260910 How to Obtain the Latest Windows Service Pack


Manual installation and additional notes:


The English-language version of this fix should have the following file attributes or later:
   Date        Time      Version       Size     File name
   --------------------------------------------------------
   10/19/2001  01:42 PM  5.0.2195.4529  86,768  Atapi.sys
   04/19/2002  05:43 PM                214,938  Update.inf

The following conditions are necessary for the correct functioning of 48-bit LBA ATAPI support: To enable 48-bit LBA large-disk support in the registry:
  1. Start Registry Editor (Regedt32.exe).
  2. Locate and then click the following key in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters

  3. On the Edit menu, click Add Value, and then add the following registry value:

    Value name: EnableBigLba
    Data type: REG_DWORD
    Value data: 0x1

  4. Quit Registry Editor.
NOTE: If you enable 48-bit LBA ATAPI support by editing the preceding registry key, but your system does not meet the minimum requirements, you may observe the following behaviors:

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 3.

LINKS

Tips on Windows NT 4.0 and some alternative work-arounds. (Microsoft did not release a similar little fix for Windows NT4 - i wonder if they're using this as a way to force people into buying Windows 2000 or XP?)