Aomei Partition Assistant Error Code 51

[Escolastico Hall]

PartitionAssistant is a highly-efficient, easy-to-use and multifunction partition managementsoftware. Under the help of Partition Assistant, you can easily & fast create/delete thepartition and the most advantage is that it resize/move your partiti

When change the drive letter failed. - eg.The program needs a change of drive letter from D to F, the program needs to unmount the D drive in order to stop the system from occupying it. If there is any system process running in this drive then the unmount operation end up failing.

When remove the drive letter failed. - eg.when partition operations such as resizing partitions, the program needs to unmount the target partition to prevent users from reading the data in it. If the program failed to unmount, you will get this notice.

When the program is manipulating partition operations, the target partition should be locked to avoid interrupting by data changing from other programs, however those obstinate applications such as anti-virus and firewall cannot be stopped normally. The program fail to lock the partition then you will be given this error code.

In operation of partitioning, partitions need to be locked firstly, when the operation has been finished, the program will unlock the target for you, if the unlock process failed, you will be given this error.

This error usually occurs when you clone a disk. To fix the issue, please first do a defragment and run chkdsk/r or chkdsk/f command to fix the errors on source drive and then retry the operation. Or, you can first manually delete your destination partition/drive and retry clone. And, we advise you to run a partition clone or clone with the sector-by-sector mode.

If you get this error when converting a data disk from MBR to GPT, please check if the starting position of the first partition is greater than 32 (right-click on the partition, choose Properties-->Partition Info and check the value of "First physical sector"), if it is greater than 32 you can directly delete all the partitions on this disk and then convert it to GPT. Finally use the Partition Recovery Wizard to retrieve the deleted partitions.

There may be underlying problems on your partition table after having your system in use for a long time, the most popular one is partition overlap. Partition Assistant will detect the disk for this error, and you will be given this error code when the partition table overlap detected.

You may be told to restart to PreOS mode when applying some partition operations, then program will save the operations into a configuration file named ampa.ini which is located in the directory of C:\Windows. Partition Assistant under PreOS mode will need to read the instructions in ampa.ini to finish the operations. You will be given this error code if the process of writing the ampa.ini failed.

The reason is usually being that the Anti-virus or System Protection programs prevent Partition Assistant from writing ampa.ini, otherwise is the insufficient disk space for writing data. By then you should close those program or clean up your system for more space.

Some operations should be done under "PreOS" mode, program then needs to add the "ampa" information to the registry item named "BootExecute" which is lying in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager" for the execution after reboot to run "C:\Windows\ampa.exe" to finish the task. You will be given the error code when writing to registry fails.

It is usually because the process of changing the registry is stopped by Antivirus or System Protection program. By then you should close those programs or let them allow Partition Assistant to do so then retry it.

If the issue persists, you may create the Partition Assistant bootable media and finish the operation under Windows PE mode. Click here to learn how to create the bootable media. Or you could perform the clone operation by AOMEI Backupper.

If the operation in PreOS mode aborted, the operation is not finished and you will be given this error when the computer starts next time, then you need just press any key to reboot your computer to solve it. Or, After login Windows, re-run Partition Assistant once to solve the issue.

When reboot from destination disk after copying disk or migrating system with Partition Assistant, when you boot the system on the destination disk, you may be given this error, then you need just press any key to reboot your computer to solve it. Or, After login Windows, re-run Partition Assistant once to solve the issue.

Volume labels are the names of your volumes you specified to differentiate them, for example we usually specified the C partition with the label System, D partition with the label Data or Work. It is a simple operation, Partition Assistant allows you to set the volume label as well. The operation rarely fails or sometimes fails due to unknown reasons.

After having installed Partition Assistant, you will have a driver program named ampa.sys located in C:\windows\system32. You will be given this error code when Partition Assistant failed to load the driver because it's been loss or corrupted.

The above errors codes are indicating the process of changing the boot.ini failed. boot.ini is a system file to save the partition parameters and boot information for Windows XP/2000/2003. Partition Assistant will need to save the partition changes to boot.ini before finalizing the process. You will be given this error when the Partition Assistant failed to change the file, and this will cause a system start failure.

If you are able to boot your system next time after the operation, then you should no more care it. If you are not able to boot from any or all your installed system, you could insert your Windows XP installation CD and get into system failure console to fix the boot.ini with bootcfg or fixboot, for detailed instructions you can search google for "bootcfg", "fixboot".

If you have no idea how to fix the boot.ini file, you may pull off your hard drive and insert to another computer or your friend's computer as a slave disk, then start the computer and find out the boot.ini file in the C partition on your hard drive, and send it to our Support team, we will help you to fix it.

It maybe the failure connection between the disk and computer or physical error like bad sectors, you may pull out and reinsert the disk or insert to other motherboard ports, or connect it as a removable external hard drive and try again.

The above error codes are indicating the process of converting FAT or FAT32 to NTFS failure. Partition Assistant is invoking the convert.exe from windows to finish the operation, the operation fails when the windows convert.exe failed.

You may check your disk with Partition Assistant or HD Tune to find out the physical errors (Note. Our program cannot fix the bad sectors.) If the bad sectors are detected, we suggest you to apply a full backup of your disk with our free Backuper to prevent your system from being corrupted. You may try the MHDD to fix the bad sectors and we highly suggest you to fix the errors before the partition operation.

You may be given the error code when applying merging partitions. The process of merging partitions needs to copy files from one to another partition, the copying might be interrupted by unknown reasons, then the copying process fails.

With the purpose to extend NTFS partition space without restarting system or closing the running programs. Partition Assistant will invoke the system application priory to finish the extension; the operation may go wrong due to unknown reasons.

You may create an empty txt file named paextend.txt in the C:\Windows directory. The next time your run Partition Assistant, it will reboot to PreOS mode to finish the operation of enlarging NTFS partition with AOMEI himself's module when the paextend.txt detected.

BCD(Boot Configuration Data) file is used to save the boot information and partition parameters for WIN7 and higher systems. Partition Assistant will update BCD file after having changed the system partition or boot partition's position, either when the disk index ID has been changed after copying disk and migrating system. You will be given this error code when the process of updating BCD fails.

1. If the system is able to boot after receiving the error, then you should pay no attention to it. Otherwise you could redo the partition operation by Windows PE bootable CD created by Partition Assistant with Create Bootable CD function.

2. If your system failed to start after the operation, you may try to amend BCD with Windows 7/8 installation CD or with a third-party tool like EasyBCD. If you knows the bcdedit command line inside out, you may also use bcdedit try to rebuild BCD file with the command line from Windows 7 System Repair Disc. Or you should contact AOMEI support if you have no idea of the error.

The files not copied will be recorded in the log file (a folder named log which is located in the Partition Assistant installation directory.) we suggest that you could copy the not-copied files to another partition manually then retry the operation. Otherwise you may copy all the data manually to another partition then delete the previous partition, after that extend the partition forward to the unallocated space with Partition Assistant to realize the merging.

If the problem remains, please offer a screenshot of the disk in Partition Assistant and send the log files under the installation directory of AOMEI Partition Assistant to AOMEI support team for further analysis.

2. The operation under windows is recommended since EFS encrypted files can be processed by desktop mode. If the program under PreOS mode is definitely required, we suggest you to try finish the merging operation with Windows PE Bootable CD created by Partition Assistant.

The target partition has not enough disk space, or a single file is too large, not enough disk space to accommodate the single file. We suggest you to release some free space from the target partition and retry.

3a8082e126