Q: Does AOMEI Backupper support backup, restore and clone dynamic volumes?
A: For MBR dynamic volumes, you can use System Backup and Partition Backup way (System/Partition Clone). Disk Backup/Disk Clone function is not supported yet. When restoring, you can only restore to the original location or a basic disk.
For GPT Dynamic Disk, Backupper currently doesn't support backing up or cloning dynamic volumes on GPT disk. We will add this function in later versions.
Q: Does AOMEI Backupper support backing up and restoring a system drive based on UEFI?
A: Yes, it completely supports backup and restore for the UEFI system drive.
Q: AOMEI Backupper can’t find system partitions or can’t list disks when running under Windows.
A: Please check whether or not the drive is 4096 bytes per sector. You can press Win+R, type“msinfo32” in the Run box, then open Components-->Storage-->Disks, then check the Bytes/sector of the drive. Backuppercurrentlydoesn’t support backing up or cloning drives with 4096 bytes per sector. But you can save backup files to 4096 drive.
Click here to learn more details.
Q: The installation of AOMEI Backupper may require the system to be restarted but the installation will not continue after the system reboots.
A: You may need to manually delete the registry of the program and then reinstall.
Please check how to delete the registry of the program here.
Q: When reinstalling AOMEI Backupper, the following error occurs: "C:\Windows\System32\amwrtdrv.sys An error occurred while trying to replace the existing file: DeleteFile Failed; code 5. Access is denied.".
A: You may click the "Ignore" button to skip this file to reinstall.
If the problem persists, please try to thoroughly uninstall the program and reinstall the program. (Delete files in the registry) You can check more instructions here.
Q: Why need to register again when running the portable version of AOMEI Backupper Technician that has been registered already?
A: The possible reason is that another edition of the AOMEI Backupper has been installed in the current system. Two different editions cannot coexist in a system.
Q: Why can’t generate a task via importing an image file?
A: It may because the image file you imported has the corresponding task in the task list of Home screen so there was no new task being generated after importing. In this case, you need to delete the corresponding task, then import it again.
Q: Why is the Windows boot stuck at loading ambakdrv.sys?
A: It might occur when you boot the Window from the cloned disk or from a new disk on which a system or disk backup image is restored. The problem might be because there is a conflict between ambakdrv.sys (the driver of AOMEI Backupper)and other drivers of the program.
Please check the instructions here.
Q: When you connect your network drive via AOMEI Backupper, you get the message: “Failed to access the network path, please check if your username, password, and network path are correct.” or “A specified logon session does not exist. Please detect if there is a directory name behind the network path, such as "\\192.168.0.100\directory_name", not "\\192.168.0.100". If the error still exists, you can reboot and try again.......”
A: Please check if the devices or programs connected to NAS have reached the ceiling of NAS. If yes, you need to disconnect some devices or programs so that the AOMEI Backupper can connect the NAS to do the backup.
If not, please delete the "NAS.xml" file under the path C:\ProgramData\AomeiBR. After that, please connect your NAS again.
Q: Why the username and password cannot be retained and you have to configure username and password every time you run a backup to NAS?
A: We advise you to delete the NAS and then connect the NAS by inputting your IP address. If it still does not work, please delete the "NAS.xml" file under the path C:\ProgramData\AomeiBR and then re-add the NAS by inputting the IP address.
Q: Why Outlook OST and PST file not being backed up?
A: By default, AOMEI Backupper uses Windows Volume Shadow Copy Service (VSS), in this way, Outlook OST file is excluded by VSS. To solve this problem:
Press Win+R, then Run “regedit” to open Registry
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot
Delete the key-value OutlookOST
For PST file, AOMEI Backupper currently doesn’t support backup. We will improve the problem in later versions.
Q: AOMEI Backupper shows error “Failed to enable backup service. Please retry or reinstall the software…” when doing backup/sync.
A: Please check if you install AOMEI Backupper to a path contains a semicolon (;). The installation path that contains a semicolon will lead to AOMEI Backupper Service startup failure, please reinstall AOMEI Backupper into a path without a semicolon.
Please check if the ABservice.exe is not running, please manually start it in Windows Services: press Win+R, then run “services.msc” to open the Windows Services Manager, if the status of AOMEI Backupper Schedule Service is not running, please double click it, then manually click “Start” and make sure startup type is Automatic.
Click here to learn more details.
Q: AOMEI Backupper shows the error “Failed to initialize RPC service. Please retry or reinstall the software and try again." when you run a backup/sync.
A: Please first try to uninstall and reinstall Backupper and then recreate a new backup task to check if it works.
If the problem still occurs, please close the anti-virus program and firewall and then retry.
If the problem persists, please close Ransomware Protection under Windows Defender and retry.
Q: Why task schedules weren’t actually executed as the backup type you set full backup, incremental backup or differential backup in schedule settings?
A: It may because you set a scheduled task and backup scheme at the same time, but you select different backup types. For example, you select incremental backup in schedule settings while using a differential backup scheme. If so, the program will ignore the backup type you set in schedule, but take backup operation according to the setting of the backup scheme.
Q: Why cannot you run backup task again when you back up to CD/DVD?
A: AOMEI Backupper doesn’t support running backup task again when the destination is CD/DVD.
Q: Why is the backup process stuck at 0%?
A: Please check if there is anti-virus software installed on your computer.
If so, the problem is that anti-virus software prevents AOMEI Backupper.
Please remove the AOMEI Backupper from the intercept list of your anti-virus software and rerun the backup.
If the problem persists, please contact our AOMEI Support Team and attach the log folder under the installation directory of the software so that we can further analyze the problem and help you find solutions.
Q: When you configure "System Startup" in "Event Trigger" and set "Operation starts delay 2 minutes" to run scheduled backup, the backup will only run in case of system hot start, not in system cold start?
A: For cold start and hot start, we advise you to disable the "fast startup" option under Control Panel\All Control Panel Items\Power Options\System Settings. In this case, both in system cold and hot start, Backupper will run scheduled backups normally.
Q: Why the “Wake the computer to run scheduled tasks” function is configured but the PC is not awaked to run the backup?
A: Please check if you enable "fast startup" mode.
If yes, please disable the "fast startup" option under Control Panel\All Control Panel Items\Power Options\System Settings. And then, please retry.
If the problem persists, please contact our AOMEI Support Team and explain what kind of schedule backup you configured.
Q: Why can’t see the small tray of AOMEI Backupper when the scheduled backup is performed with the standard account?
A: AOMEI Backupper needs to acquire the administrator’s permission to run the interface program, while only use system permission to run the backup. The small tray is a part of the interface program. Under the standard account, AOMEI Backupper can’t get the administrator’s permission to run the interface program and so the scheduled backup will be performed without the small tray.
Q: The shutdown event backup doesn’t run after you power off the computer?
A: The shutdown event backup is based on the shutdown of windows. You can click the “shut down” or “restart” button in Start Menu to enable the shutdown event. However, if you power off the computer, it directly cuts off the power to close the computer forcibly. In this situation, the program can’t get the windows shutdown information to perform backup.
Q: The shutdown event backup doesn’t run after you shut down the computer?
A: If you are using Windows 10, please check if you turn on Fast Startup under Control Panel-->Power Options-->System settings. If yes, please close it and then check if shutdown event backup will run.
Q: There is no image file after the shutdown event backup is executed.
A: Please check the following items:
1) There may be user interaction operation when the shutdown event backup is running. Because you can’t see and respond to the interaction during shutdown, the program cancels the backup and then turn off automatically. So, the image file is not produced. We suggest that you can run the backup manually in windows to check the interaction operation and then re-edit the backup to cancel the interaction request during shutdown.
2) If you don’t see the interaction request when you run the backup manually in windows, please make the backup run again during shutdown. If there still is no image file, please attach the log files under the installation directory of the software to contact us.
Q: The event backup doesn’t run after the event occurs.
A: Please check the following items:
1) Please check if AOMEI Backupper Schedule Service is enabled in Windows Services (you can run “services.msc” to open Windows Services). If not, you can enable it manually or reinstall the software. The AOMEI Backupper Schedule Service will enable backup program to run backup when the event occurs.
2) Please check if abnotify is running in Windows Task Manager. If not, please find the abnotify.exe under the installation directory of AOMEI Backupper to run. However, if the backup task still can’t run, please reinstall the software and backup again. The abnotify will tell AOMEI Backupper Schedule Service to enable backup program when the event occurs.
3) If AOMEI Backupper Schedule Service and abnotify are run normally, but the event backup still can’t run, please attach the log files under the installation directory of the software to contact us.
Q: The event backup doesn’t run on this day after you check “Run one time every day” in event triggers.
A: If the backup task has been executed on this day, the event backup will not run again when the event occurs this day.
Q: How to make a cloned drive bootable?
A: Before disk clone, please check the following items:
1) Please first install AOMEI Backupper on the current running machine.
2) Please just run a disk clone of the current running system drive and the cloned drive can only be used to boot the current machine. If you would like to boot another system, we advise you to run a system backup on a working machine and use the feature "Universal Restore" (available in paid editions).
3) If the current system drive and the new drive are with different disk types ( for example, one drive is MBR and the other one is GPT), it is recommended to convert the disk type of the destination drive in advance to make the destination disk type consistent with the type of the source drive.
4) It is also recommended to wipe the destination drive and do defragment in advance.
5) When you configure the disk clone, please tick the option "SSD Alignment" if the destination drive is an SSD. If you would like to clone a smaller system drive to a larger one, you can use the feature "Edit Partition" and tick "Add unused space to all partitions" (available in paid editions) so all source partitions will be automatically resized to fit the entire disk space.
After disk clone, please check the following items:
1) Please make sure the new drive is connected internally, not via an external slot (for example, USB connector).
2) You may need to modify Boot Priority to select the new drive as the first boot option in BIOS/UEFI.
3) If the source disk and target disk are of different types (one uses MBR mode and the other uses GPT mode), you have to modify the Boot Mode (Legacy/UEFI) in BIOS/UEFI when you boot from the target drive.
If the cloned drive still fails to boot, please contact our AOMEI Support Team and offer some pictures of the boot error and the disks layout in Backupper Disk Clone so that we can further analyze the problem and help you find solutions.
File Sync FAQs:
Q: Why files larger than 4GB in the source directory may not be synced to the target path?
A: If the target path was located in the FAT/FAT32 partition, files larger than 4GB will not be synced to the target path because a single file larger than 4GB cannot be stored on a FAT/FAT32 partition. Please re-select another target path and try again. If the partition where the target path was located is not FAT/FAT32, please contact our technical support and send the log folder in the installation directory.
Q: In the sync, why files aren’t deleted from the target path when they have been deleted from the source?
A: For common/schedule sync, Backupper currently doesn’t support delete files from the destination when deleting from the source. You can try to use Rea-time sync and check the "target files will be deleted when deleting the source files" option in the real-time sync setting.
Real-time Sync FAQs:
Q: In a real-time sync task, why the source file has been changed, but the change is still not synchronized to the target directory?
A: In real-time sync, you may experience a problem that the file in the source directory has been changed but the change is not synchronized to the destination directory. In this case, please manually run the sync task and then check if the change can be synchronized to the destination directory.
a) If the change is synchronized to the destination directory after a manual execution, the possible cause is that the ABSync.exe is not running. Please check if the ABSync.exe is running under Windows Task Manager. If it is not running, you can find the ABSync.exe under the installation directory, right-click and manually run ABSync.exe as an administrator and then check again. And, it is recommended to close the anti-virus program and add ABSync.exe to the whitelist of the anti-virus program. If the problem still remains, please contact our support team and attach the log folder and mmf folder under the installation directory so that we can further analyze the problem and help you find solutions.
b) If the change is still not synchronized to the destination directory even after a manual execution, the problem is that ABCore.exe is not running. Please manually run ABCore.exe as an administrator and retry.
Q: After real-time sync, why files larger than 4GB in the source directory may not be synced to the target path?
A: If the partition where the target path was located is FAT/FAT32, files larger than 4GB will not be synced to the target path. Because a single file larger than 4GB cannot be stored on a partition that is formatted with FAT/FAT32. Please re-select another target path and try again. If the partition where the target path was located is not FAT/FAT32, please view the product log, or contact our technical support and send the log folder in the installation directory to us.
Q: After real-time sync, why some files or folders in the target path cannot be accessed?
A: The possible reason is that after the files or folders are synced to the target path, the character of files or folders path exceeds the maximum path character allowed by Windows system. Although the files or folders cannot be accessed, they are not damaged. You can access the files or folders by cutting the parent directory of them to other path with less character. If they are still inaccessible after cutting operation, please contact our technical support and send the log folder in the installation directory to us.
Q: After real-time sync, why some source files cannot be synced to the target path?
A: The possible reason is that SYSTEM user doesn't have permission to access the source files, but real-time sync operates files based on SYSTEM user’s permission. Therefore, some source files cannot be synced successfully. At this point, you can add SYSTEM user’s permission into the security attribute of the file and then try real-time sync again. If it still fails, please contact our technical support and send the log folder in the installation directory to us.
Q: How to view the progress of real-time sync?
A: Real-time sync temporarily has not yet used an executing interface or a tray notification to show sync progress. You only can view the progress when creating a new task and it is unable to view it later. To determine how the real-time sync is executed, you only can check the status of files in the target path or the log.
Q: In a real-time sync task, why source files cannot be immediately synced to the target path after the files have been deleted from the target path?
A: Real-time sync temporarily only supports one-way monitoring and one-way sync which mean it monitors the changes in the source files and sync them to the target path, but not to monitor the changes in the target path. Therefore, it will not perform a sync operation when any change occurs in the target path.
Note: Real-time sync tasks only support one-way sync. For example, sync from A to B. Do not create a real-time sync task from A to B, and then create another task from B to A. Otherwise, it may cause circulating sync which will increase CPU usage, make system running slow, and even lead to the source files corruption.
Q: After Word and Excel documents real-time sync, why there are many temporary files in the target path which are created when modifying Word and Excel documents?
A: Because real-time sync will monitor all the subfolders and files (include temporary files) in the source folder, temporary files will also be synced when performing real-time sync. To ensure data safety, the program provides the “target files will be deleted when deleting the source files” function in the real-time sync setting.
Q: You received the following messages when you do restore or clone: “Failed to add boot configuration, cannot enter Restart Mode. Please make a bootable disc by clicking "Tools" -> "Create Bootable Media" and boot from a CD/DVD to realize the restore operation.” Or “Failed to create the Windows PE bootable ISO image, the operation cannot proceed. Please try to make the Windows PE bootable ISO image by clicking “Tools”-> “Create Bootable Media”.”
A: If some partitions are occupied by other programs, the restore/clone operation will be performed under Restart Mode, for example, system restore to C: drive. However, AOMEI Backupper may fail to enter into Restart Mode automatically because of some unknown error, for example, the recovery environment is damaged or can’t be found. To solve the problem with the following methods:
1) Make a WinPE bootable disc by clicking "Tools" -> "Create Bootable Media" and boot from the WinPE to restore/clone.
2) Create WinPE iso (ampe.iso) via Tools-->Create Bootable Media, and then put the iso to the installation directory of AOMEI Backupper. After that, please try to restore/clone again.
Q: You received the message: “Because the system partition exists in a dynamic disk or the image file exists in a dynamic volume. You can go to Tools-> Create Bootable Media and make a Windows PE bootable CD (not Linux Bootable CD) and try again.” when you do restore.
A: If there are programs still running on the destination partition during the restore process, the program will automatically restart the computer and run Backupper from the Linux or WinPE mode to complete the restore process. This problem arises because an image file in a dynamic partition cannot be recognized by Linux environment. To solve the problem with the following methods:
1) Copy this image file to a basic partition and then restore again.
2) Click Tools-> Create Bootable Media to create a WinPE bootable media. A WinPE Bootable media is able to recognize image files in a dynamic volume. After that, please boot from WinPE bootable media to do restore.
Q: You received the message: “Because the image file exists in a share/NAS network, you need to make a bootable CD...” when you do a restore operation.
A: If the image file is saved in a shared folder or a NAS device, you will receive the above message if there are programs still running in the target partition which cannot close. To solve the problem, you only need to click Tools -> Create Bootable Media to create a bootable media. Then, boot your computer from the bootable media to complete the restore process.
Q: You get the message: “Unable to get the backup information because the image file does not exist, or it can’t be accessed...” when you click the Restore or Advanced button on a backup task of Home screen.
A: The problem might be that the task can’t locate the backup files due to unknown reasons. You need to delete the task and then re-import the backup task by browsing the backup files under Tools-->Import/Export Configuration. After that, the task will be listed on the Home screen again.
Universal Restore FAQs:
Q: After the system is restored to other dissimilar hardware computers, why cannot it boot normally?
A: Please make sure that the “Universal Restore” button is checked, because when there is a difference between the computer where the source system is installed and hardware environment of the target computer, “Universal Restore” must be chosen, and restored operating system can be sure to boot normally.
Maybe the computer disk mode (AHCI IDE RAID) is changed. Disk mode is not allowed to be changed after using universal restore. In other words, if the disk mode is AHCI while restoring the system, please stay disk mode the same as AHCI after restoring, If not, the system will not boot normally; so does IDE RAID and they need to stay the same with source disk on disk mode. (About disk mode, you can refer to the BIOS manual).
Please make sure that Universal Restore operation is run under Windows or Windows PE bootable media, because AOMEI Linux bootable media can’t support universal restore currently.
If the BIOS version of target computer that you restore system to is advanced than InsydeH20 Rev.3.7 version, you need to enter BIOS setting manually and set “OS Optimized Defaults” in the “Exit” item:
Only in this way, a different machine that is restored system will be sure to boot normally.
If the OS restored is Windows 7, you need set the parameter as “Win7 OS”.
If the OS restored is Windows 8, you need set the parameter as “Win8 64bit”.
If the OS restored is another Windows system, you need set the parameter as “Other OS”.
Q: About the problem that activation overdue is prompted by computer that applied with universal restore while it booting.
A: After restoring legitimate Windows from one computer to others, it is normal that system prompted that system need to be activated again after it booting. Due to the fact that there is limitation to use activation code, therefore, you may need to activate the system again.
Q: About the problem that software need to be activated again after using universal restore.
A: After restoring Windows from one computer to others, it is normal that billing application or software prompted that system need to be activated again after it booting. Due to the fact that there is limitation to use activation code, therefore, you may need to reactivate those billing application or software again.
Q: About the problem that computer need to install graphics card, network card, and sound card drivers, etc.
A: Universal Restore just makes sure the system can boot normally after restoring system from one computer to another. For some drivers that are not relevant to system booting, such as graphic card, network card, and sound card drivers, etc, they need you to install manually.
WinPE Bootable Media FAQs:
Q: You received the message: “Failed to create the bootable USB device...” when you clicking "Tools" -> "Create Bootable Media" to create the bootable media.
A: In the "Select Bootable Media" dialog box, choose "Export ISO File" instead of "Burn To CD/DVD" or "USB Boot Device" to create an ampe.iso file, and then burn the ISO file to USB, CD, or DVD via third-party burning tools.
Q: You received the message: “Create WinPE ISO file failed…” when you click "Tools" -> "Create Bootable Media" to create WinPE bootable media.
A: It might that there are some unknown errors in your recovery environment. You can try to recreate the WinPE by checking “Download WinPE Creating Environment from the internet”. Or, you can download and install Windows AIK or ADK from Microsoft site, and then create WinPE again. Please check more details and download Windows AIK or ADK here.
Starting with Windows 10, version 1809, you need to download the Windows PE Addon and run the included installer after installing the ADK.
Q: AOMEI Backupper can’t detect the internet under Windows or WinPE.
A: Please check the following items:
1) If you are using the virtual network that is connected to a proxy server under Windows, AOMEI Backupper can’t detect the internet.
2) If it is connected via the wireless network, AOMEI Backupper can’t detect the internet under WinPE.
3) If AOMEI Backupper can’t connect the internet in WinPE, maybe there is no network card driver. Please recreate the WinPE and add these drivers manually during creating. Or, you can check“DownloadWinPEcreating environment from the internet”, the creating environment is based on Windows 10 with lots of common drivers included, so you may not have to add drivers like network adapter or NVME/m.2, etc.
Q: When selecting to create a WinPE bootable CD, a window "Detects that there is not any writable disc, please insert a writable disc. Click "yes" to continue, or "no"." prompts up.
A: Please just create a WinPE ISO with AOMEI Backupper and then manually burn the ISO to the CD with a third-party burning program. Please check the instructions here.
Q: There is no file on the USB after Backupper has created the WinPE USB successfully.
A: Please check if the USB is an MBR USB. If it is a GPT one, please first convert the GPT USB to MBR with DiskPart or Partition Assistant and retry to create the WinPE USB.
Q: The program exits abnormally during the creation of bootable media.
A: We advise you to directly run makedisc.exe under C:\Program Files (x86)\AOMEI Backupper
And please also tick the "Download WinPE creating environment from internet" option when creating bootable media. Also, you can try to download and try AOMEI PE Builder to create a bootable disc from the following link: http://www2.aomeisoftware.com/download/pe/2.0/full/PEBuilder.exe
Q: The creation of a bootable CD process is stuck at 99%.
A: We advise you to create a legacy ( not UEFI) bootable disc and then create WinPE iso (Third option: Export ISO File), then burn it to your CD manually via the third-party burning tool (Such as Ultraiso, Rufus, ISOtoUSB, and so on ).
Or, you can try to create a WinPE bootable USB via AOMEI Backupper. There is no problem when creating a WinPE USB.
Or, you can try to create a WinPE bootable CD via AOMEI PEBuilder:
Email Notification FAQs:
Q: What does it mean about “User interaction required” in the email notification?
A: The program needs to open an interaction window that is waiting to be interacted by the user in the following situations when the program invokes the small tray to run the backup, such as schedule backup.
In the three situations, the interactive window is waiting for response three Minutes during backup/sync. If it does not get a response, the program will choose a default one to process automatically.
1) The interactive window shows that you need to restart or skip files when you back up/sync these files accessed by other programs.
2) The interactive window requires NAS username and password when the program cannot connect the NAS.
3) The interactive window shows that you need to make more space available when there is not enough space to save a backup in the destination.
In the four situations, the interactive window is waiting for response until you do it.
1) The interactive window shows that you need to insert a new CD/DVD after the last CD/DVD is used up when you back up to CD/DVD.
2) The interactive window shows that the CD/DVD will be erased after you insert the CD-RW/DVD-RW when you back up to CD/DVD.
3) The interactive window shows that you need to register when the backup starts to run if the software is not registered or the trail has expired.
4) The interactive window shows that you need to confirm the operation when the program needs to reboot into the WinPE environment to complete backup.
Q: Why does it send test email failed with the message “Sorry, failed to send text message”?
A: For Gmail Server: When you set up email notification with Gmail server, you may encounter this issue, as far as we know, it is because Google enhanced Gmail’s security level, you need to turn on access for less secure app in Google setting, then retry.
For Custom SMTP Server: AOMEI Backupper requires SMTP authentication, it does not support anonymous access. If you set up it without credentials, you will encounter this error.
Q: Why could you send a test message successfully but could not get email notifications after successful or failed operations?
A: Please make sure you use the newest version of AOMEI Backupper.
Also, please check if you have configured and enabled "Email Notifications" for the backup task. ( You can find the task and click the three-line button and click "Edit Backup" and click "Options"-"General" and check if you enabled the "Email Notifications"). If it is not enabled, please enable the feature and retry.
If you have configured the feature for the task but still do not get the email notifications (you can get a test message), please contact our AOMEI Support Team to offer screenshots of the email notification settings and attach the log folder under the installation directory of the software so that we can further analyze the problem and help you find solutions.