# Recover a lost or deleted partition

> Scan a disk for lost NTFS and exFAT partitions with S.A.K. Utility, then write a found partition back to the disk's partition list using its offset and size.

Source: https://sakutility.com/wiki/recover-lost-partition
Applies to: S.A.K. Utility (SAK), a free portable Windows toolkit
Updated: 2026-11-10

To recover a lost or deleted partition on Windows, use the **Partition Recovery Wizard** in S.A.K. Utility: open the **Partition Manager** tab, select the disk, run the wizard's scan through **Apply**, read the offsets it finds in the log, then run the wizard again to write the partition back. This is a hands-on tool. The scan reports where a partition starts and, when its boot sector records it, its size. You supply the type.

## When to use this

A partition vanished or was deleted by mistake, and nothing has been written over that part of the disk since. If you need individual files instead, see [Recover deleted JPEG, PNG, and PDF files](https://sakutility.com/wiki/recover-deleted-files).

## What you need

- The affected disk connected as a second drive. Writing a partition back is blocked on the disk Windows is running from, though scanning it is allowed.
- The partition's size in bytes. The scan gives it when the partition's boot sector records it. When the log says `size unknown`, the size has to come from your notes, an earlier **Properties** copy, or another recovery tool.
- Administrator approval when you press **Apply**.

Stop using the disk until you are done. Do not create or format partitions on it first, because that can overwrite what you are trying to recover.

## Steps

### Find the partition

1. Press **Scan Disks** and select the **disk** row.
2. Click **Partition Recovery Wizard**. The **Source Disk** page names the disk. Press **Next >**.
3. On **Scan Mode**, set **Mode:** to **Quick** or **Full**, and press **Next >**. **Quick** checks the first 128 GB. **Full** checks the whole disk and takes longer.

   ![The Scan Mode page of the Partition Recovery Wizard with a Mode list](https://sakutility.com/screenshots/wiki/partition_manager_recovery_scan_mode.webp?v=12d2c24c80)

*Quick checks the first 128 GB, Full checks the whole disk*

4. On **Candidate Restore**, leave the checkbox clear, and press **Next >**. On **Review**, press **Finish**.
5. Turn on the **Log** switch.
6. Press **Apply**, read the **Apply Partition Operations** window, press **Apply** in it, and approve the Windows prompt.
7. In the log, look for lines like `Candidate partition boot sector at byte offset 3238002688 (NTFS, size 2147483648 bytes)`, which appear as the scan finds them. Write down the offset and the size. A partition the disk has now is listed as `Partition 2 is at byte offset ... and is not lost`, and a boot sector inside a partition the disk has now, or one that would run into it, is marked `not a candidate`, so neither is mistaken for a lost one.

   ![The log window showing the partition recovery report with a candidate boot sector line and its byte offset](https://sakutility.com/screenshots/wiki/partition_manager_recovery_log.webp?v=76e6508fc5)

*Found partitions appear in the log as byte offsets*

### Write the partition back

1. Select the same **disk** row and click **Partition Recovery Wizard** again.
2. Press **Next >** until you reach **Candidate Restore**.
3. Check **Queue recovered partition write-back candidate**.
4. Enter **Offset bytes:** and **Size bytes:** from the log. If the log said `size unknown`, enter the size from your own records.
5. Enter **Type ID:**. On a GPT disk, a normal Windows data partition is `{EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}`. On an MBR disk, use `IFS` for NTFS or `FAT32` for FAT32.
6. Press **Next >**. If the place overlaps a partition the disk has now, or runs past the end of the disk, the page says why in red and **Next >** stays off until the numbers are changed.

   ![The Candidate Restore page with a queue checkbox and offset, size, and type ID fields](https://sakutility.com/screenshots/wiki/partition_manager_recovery_candidate.webp?v=2fc4bcb123)

*Enter the offset, size, and type of the partition to restore*

7. Read the **Review** page, check **I understand the recovered partition candidate will be written to the selected disk.**, and press **Finish**. **Finish** stays off until you check it.

   ![The Review page of the Partition Recovery Wizard summarizing the scan and the write-back candidate](https://sakutility.com/screenshots/wiki/partition_manager_recovery_review.webp?v=5b642ffa51)

*The wizard summarizes what it will queue*

8. Press **Apply** as above. The wizard queues another scan along with the write-back, so both run.
9. Press **Refresh Disks** if needed, then check your files.

## How it works

**The scan** only reads. It looks at the first sector of every 1 MB step across the disk. A sector counts only if it ends with a boot sector's signature. S.A.K. then reads the format the boot sector records: NTFS, exFAT, FAT32, FAT16, or FAT12. A BitLocker volume is reported as BitLocker.

**The write-back** adds a partition entry at the offset and size you gave, using Windows' `New-Partition` command. First it checks that the entry stays within the disk and does not overlap an existing partition. Windows blanks the start of a partition it creates, where the boot sector is, so S.A.K. reads that part first and puts it back. It does not format anything or change the rest of the data.

## Good to know

> **Back up first.** If the data matters, take an image of the disk before you write to it, and store it elsewhere. On the v0.9.3 code, Partition Manager operations, including boot repair, MBR-to-GPT conversion and OS migration, ran through the app on disposable virtual machines and virtual disks. Some operations were also tested on one SAMSUNG MZVL2512HCJQ-00BH1 512 GB NVMe SSD and one Seagate Expansion Desk 8 TB USB disk. Internal SATA drives were not tested, and results on other devices may differ. See [what was tested](https://sakutility.com/wiki/partition-manager-basics#what-was-tested). A wrong entry can be removed, but it cannot be undone automatically.

- **Only some partitions can be found.** Ext, HFS+, and APFS partitions are not detected. NTFS, exFAT, and FAT partitions are found, including FAT volumes formatted by Windows.
- **Only partitions that start on a 1 MB boundary are found.** This covers partitions made by current Windows versions. Partitions from very old systems may not be.
- **A candidate is only a signature.** A line in the log can be a stale boot sector from an old layout, or a backup copy. Check that the offset makes sense before you write it back.
- **A wrong size causes real trouble.** A size you type yourself cannot be checked against the file system. Too small cuts off the file system. Too large includes space that does not belong to it.
- **The scan finds NTFS, FAT12, FAT16, FAT32, and exFAT boot sectors that start on a 1 MB boundary.** Windows has placed partitions that way since Vista. A partition from an older layout that starts elsewhere is not found.
- **The write-back is refused** if it overlaps an existing partition, runs past the end of the disk, or targets the disk Windows is running from. The **Candidate Restore** page says why and keeps **Next >** off, and the same checks run again when the operation is queued and before anything is written.

## Related guides

- [Recover deleted JPEG, PNG, and PDF files](https://sakutility.com/wiki/recover-deleted-files)
- [Clone a disk or copy a partition](https://sakutility.com/wiki/copy-disk-or-partition)
- [Partition Manager basics](https://sakutility.com/wiki/partition-manager-basics)
