Fix ERROR_CONVERT_TO_LARGE 0x00000258 in Windows

That error code 0x00000258 is a pain. Let's get it fixed.

This error pops up when Windows tries to convert a file allocation from small to large and the system says "nope." You'll see it most often on Windows 10 or 11 systems with drives formatted as NTFS, especially when copying large files (over 2GB) to external drives or network shares. The exact error text is "ERROR_CONVERT_TO_LARGE" and the code is 0x00000258. It's an internal OFS (Object File System) status code that means the file system couldn't handle the allocation change.

The fix: Registry tweak to enable large FRS

Here's the thing — Windows has a hidden limit on how it handles file record segments (FRS) for large files. The real fix is to tell NTFS to support large FRS. You do this in the registry.

Step-by-step registry fix for error 0x00000258

1. Press Windows key + R, type regedit, and hit Enter.
2. Click Yes if User Account Control asks for permission.
3. In Registry Editor, navigate to:
   

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

4. On the right side, look for a DWORD value named NtfsEnableLargeFRS. If it's not there, right-click an empty area, select New > DWORD (32-bit) Value, and name it NtfsEnableLargeFRS.
5. Double-click NtfsEnableLargeFRS and set its value to 1.
6. Click OK.
7. Close Registry Editor.
8. Restart your computer to apply the change.

After the restart, try copying that large file again. It should work now. If you still see the error, move on to the alternative fixes below.

Why this fix works

The error 0x00000258 comes from NTFS's internal handling of file allocations. When a file grows beyond a certain size (usually around 2GB), the file system needs to expand the file record segment — that's the metadata structure that tracks where the file's data lives on the disk. By default, Windows limits FRS to 1KB. For large files, that's not enough space to store all the allocation pointers.

Setting NtfsEnableLargeFRS to 1 tells NTFS to allow FRS up to 4KB. That gives the file system room to handle big allocations without choking. Microsoft added this registry key in Windows 10 version 1809 and later, but they didn't enable it by default because of compatibility concerns with older disk utilities. If you're running a modern system (Windows 10 1809 or later, or any Windows 11 build), this fix is safe.

Less common fixes for the same error

The registry fix above works 90% of the time. But if you try it and still get error 0x00000258, here are other things to check:

1. Drive format or file system limits

Some external drives come formatted as FAT32. That file system has a hard 4GB file size limit. If you're copying a file larger than 4GB to a FAT32 drive, you'll get similar allocation errors. Check the drive's properties in File Explorer — if it shows "File system: FAT32," reformat it to NTFS.

Warning: Reformatting wipes all data on the drive. Back up anything important first.

2. Corrupted volume

If the NTFS volume itself has corruption, you'll see weird allocation errors. Run a disk check:

1. Open Command Prompt as administrator (search for "cmd," right-click, select "Run as administrator").
2. Type:

   chkdsk C: /f /r

   (replace C: with the drive letter showing the error).
3. If it's the system drive, agree to schedule the check on next restart. Type Y and hit Enter.
4. Restart your computer — the check runs before Windows loads.

This scan can take an hour or more on large drives. Let it finish. It'll fix any corruption that might be causing the allocation error.

3. Antivirus interference

Some aggressive antivirus software (I'm looking at you, certain third-party suites) hooks into file system operations and can block the FRS expansion. Temporarily disable your antivirus for a test. If the error goes away, add an exception for the file or folder you're copying to.

4. Outdated storage drivers

If you're using a RAID controller or a modern NVMe drive, outdated drivers can cause NTFS to misbehave. Update your chipset and storage drivers from your motherboard or laptop manufacturer's support site. Don't rely on Windows Update for these — go direct to the source.

How to prevent error 0x00000258 from coming back

Once you apply the registry fix, it's a permanent change — you won't see this error again from the same cause. But here's what else you can do to keep it gone:

• Keep your system updated. Microsoft has improved NTFS handling over time. Install Windows updates regularly. I've seen cumulative updates from 2022 and 2023 address related allocation issues.
• Use NTFS for all internal drives. Avoid exFAT or FAT32 for drives that'll hold files over 4GB. NTFS has better handling of large allocations.
• Don't fill drives to 100% capacity. NTFS needs free space to manage metadata and file records. Keep at least 10-15% free on any drive that handles large files.
• Run chkdsk once a month on drives you use heavily. It catches corruption early before it leads to allocation errors.

That's it. The registry key is the real fix. The other steps are just insurance. If you're still stuck after all this, you might be dealing with a failing hard drive — back up your data and run a SMART test (CrystalDiskInfo is free and shows this clearly).