A conversion that stops at 0x000036B7 usually ends with a disk that no longer starts and a lot of worry about the files on it. The code is a layout complaint, not a report of destroyed data. The conversion stops because it cannot place the partitions it needs in the space it found, and in most cases every folder is still where it was. The important part is what you do next: every retry and every repair attempt writes to the disk, and those writes are what turn a recoverable layout into missing files. This guide covers the order that protects the data.
The conversion rewrites the partition table and creates new partitions for the modern boot scheme. It reserves room for an EFI system partition and a reserved partition, and when the free space on the disk does not fit that plan, it stops and reports the code. The message is about geometry, so the volumes themselves are normally intact.
There are two possible end states. If the check failed before any write, the table is unchanged and the disk still holds its original partitions. If it failed after the table was rewritten, the disk may carry a partial layout and no longer start, while the Windows volume sits in place with its file system untouched.
The state decides the next move. A disk that still boots as before needs no recovery at all, only more free space and a different plan. A disk that no longer boots has to be read from another machine, and the folders on it are the priority.
MBR2GPT is a Microsoft tool that ships with Windows and is not part of any Qiling product. It is named here only to explain the message you saw, and none of the recovery steps below run it.
Do not repeat the conversion to see whether it works the second time. Each run writes to the partition table again, and a disk that is already half converted is the worst starting point for a recovery scan.
Do not accept a prompt that offers to initialize the disk, and do not format a volume to make it visible. A format writes a new file system over the records that describe your folders, and that is the one action that can turn a readable disk into an empty one.
Stop booting from the disk as well. A machine that repeats its startup repairs writes to the same areas on every attempt, and a disk that keeps restarting is also the easiest way to overheat a drive that is already suspect.
Take a sector-level image of the whole disk before you scan it. The image is a safe copy that you can scan again, hand to a specialist, or restore later, which means the original disk only has to be read once.
Connect the drive to a working desktop with a spare data cable, or place a laptop drive in a USB enclosure. A desktop port keeps the drive powered for the whole job, which matters when the disk is old or already unstable.
Read the image, not the failing disk, when the original starts to make noise or drops off the bus. Everything after this point happens on the copy, and the original stays untouched until you decide what to do with it.
Qiling Deep Data Recovery reads the file records below the partition table, so a volume that Windows no longer mounts can still be listed with its folder structure. Scan the image or the attached disk, preview the files you need, and save them to a third drive.
Use Fast Scan when the volume still mounts but shows nothing, because the file records are probably in place. Choose Format Scan or Disk Scan when the volume reports as RAW or Disk Management shows the space as unallocated after the failed conversion.
Pick the disk by model and capacity, not by letter, since the letters may have been reassigned. Do not select the disk that will receive the recovered files, or the scan will compete with its own output.
Sort by date and open the folder that matches your user profile. Preview a few documents and photos of different types before you select anything, so the batch you save is known to open after recovery.
Write the results to a disk that is not part of the problem, and keep the image until you are satisfied that everything important is out. Only then decide whether the disk should be converted again or rebuilt from scratch.
Almost never. The code stops a layout change, and the volumes keep their file systems unless something later writes over them. A scan of the disk shows whether the records are still present.
Yes, once the data is saved elsewhere and the free space is arranged. Running it again before that risks the only copy of the data for a problem that may need a different layout anyway.
Not before the files are out. Startup repair rewrites boot areas and can also rewrite the partition table, which is the one structure a recovery scan still needs in its original state.