STATUS_FOUND_OUT_OF_SCOPE (0XC000022E) – Real Fixes

First Things First – The 30-Second Fix

You're seeing STATUS_FOUND_OUT_OF_SCOPE (0XC000022E) during boot. I've seen this hundreds of times on old Dell Optiplexes, HP Proliant servers, and custom builds with cheap drives. The culprit here is almost always a hardware link issue – not a corrupt OS file. Don't bother reinstalling Windows; it won't help.

Check Your Boot Order

Reboot and mash F2, Del, or Esc (depending on your motherboard) to get into BIOS. Look for the boot order. If your primary drive isn't first, or if the system is trying to boot from a USB stick or network, fix that. Set the correct disk as first boot device. Save and exit. If it boots, you're done. If not, move on.

Reseat the SATA Cable

Power down. Open the case. Unplug and replug both ends of the SATA data cable – first at the drive, then at the motherboard. Do the same for the power cable. This sounds stupid simple, but I've fixed this exact error half a dozen times doing just that. Bad connections cause the controller to lose track of the drive geometry, triggering FOUND_OUT_OF_SCOPE.

Boot again. Still failing? Swap the SATA cable with a known good one. Don't use a cable that's been folded tight – the wires inside snap.

5-Minute Fix – Change SATA Mode in BIOS

If reseating didn't work, the disk is likely fine but the controller is confused. Enter BIOS again and look for SATA operation mode. You'll see options like IDE, AHCI, or RAID. The error appears most often in RAID mode when a single disk is attached, or in AHCI mode when the disk expects IDE.

Try switching to AHCI (if on IDE) or IDE (if on AHCI). Save and reboot. Windows will complain about driver changes – let it run the automatic repair. I've seen this fix the error on older systems running Windows 7 or 8.1. For Windows 10/11, it's less common but worth a shot.

Check Disk Health with S.M.A.R.T.

If you can get into another computer or a live Linux USB (do that in a minute), run smartctl -a /dev/sda (Linux) or a tool like CrystalDiskInfo (Windows). Look at these attributes:

If you see high CRC errors but low reallocated sectors, swap the SATA cable and the power connector (try a different PSU cable). That alone can clear the error.

15+ Minutes Fix – Advanced Troubleshooting

Still stuck? You've got hardware failure or a controller issue. Let's go deep.

Boot to a Live Linux USB

Grab a Ubuntu or SystemRescue image, write it to a USB with Rufus, and boot from it. Once in Linux, open a terminal and run:

sudo fdisk -l

This lists all disks. If you don't see your boot drive, the disk is dead or disconnected. If you see it, try mounting it:

sudo mount /dev/sda1 /mnt

If it mounts without errors, the drive is probably fine. The issue is almost certainly the controller or the cable. If it throws I/O errors, the drive is toast. Back up whatever you can with ddrescue:

sudo ddrescue /dev/sda /dev/sdb /tmp/logfile.log

Replace /dev/sdb with a good drive. This saves every readable sector. Do this before you do anything else if the drive is failing.

Check the Controller

If you're on a dedicated RAID card (like an LSI or Adaptec), STATUS_FOUND_OUT_OF_SCOPE often means the controller lost the drive's metadata. Enter the controller BIOS (usually Ctrl+C or Ctrl+M during boot). Look for the virtual disk – if it shows as “missing” or “foreign”, import it. If it won't import, the array is broken. In that case, you're looking at rebuilding the array from backups – or if no backups, sending the drives to a data recovery service. Don't bother trying to force the controller – you'll just scramble the data.

On a motherboard SATA port (most home PCs), try a different SATA port. Port 0 and Port 1 are often tied to a different controller than Ports 2-5. Move the drive to a different port. Boot. Fixed it? Great. If not, the motherboard controller might be dying – try a cheap PCIe SATA card for $15.

Replace the Drive

If all else fails – the drive doesn't appear in BIOS, Linux can't see it, and you've swapped cables and ports – buy a new drive. For an old system, grab a cheap SSD like a Crucial BX500 or Kingston A400. Clone the old drive if it still works partially (use Clonezilla). If it's dead, reinstall Windows and restore from backup. This error is a death sentence for mechanical drives – don't argue with it.

Pro tip: I've seen this error on systems with a dying PSU that couldn't spin up the drive. If you've tried everything and the drive acts dead, test with a different power supply. A multimeter on the yellow (+12V) and red (+5V) lines of a SATA power connector will tell you fast.

When to Call It

If you've replaced the SATA cable, changed the SATA mode, checked S.M.A.R.T., booted Linux, tried another port, and checked the PSU, and the error persists, the drive is done. Don't waste more time. Replace it. You can try data recovery software like R-Studio or DMDE on a good drive once the bad one is cloned, but STATUS_FOUND_OUT_OF_SCOPE doesn't lie – the drive has lost its mind. Move on.