Skip to main content

Troubleshooting

A task does not run or aborts​

A task runs only while its initial conditions remain stable. Check the paths and storage locations of the backups, the source and target drives, the drive names and the network access rights, and run Check task under Tasks & Reports.

A task that uses network shares must run under a user account with access to them; the SYSTEM account does not reach all shares. If the full backup and the backups of changes are in different directories, clear Suppress user prompts during execution, otherwise the task aborts when it cannot find the preceding backups. If the base backup was moved, update its location in the task. See Tasks and Manage tasks.

An imported task does not run​

Imported tasks are not enabled automatically. Check them, adjust drive letters, paths and network conditions that differ from the source computer, and enable them. See Manage tasks.

No e-mail notifications arrive​

Configure the SMTP access data and the sender under Program settings > Notification first and send a test e-mail. If the mail server enforces strict authentication, enter the host name of the mail server in the Domain field. Then select the recipient and the events in the task. See Program settings.

The target medium is too small​

If the target runs out of space during a backup, O&O DiskImage asks for an additional target path. For a restore or duplication to a smaller disk, use the file-based method. See Restore drives.

The system partition cannot be restored​

The system partition cannot be overwritten while Windows is running. Start the computer from the boot medium or the RecoveryPartition and restore from there. See Restore the entire system.

The restored or duplicated system does not start​

The usual cause is an incomplete selection: not the entire disk was selected as the target, Delete layout was not selected when the target layout was created, only individual source partitions were selected instead of the entire disk, or the bootable drive hangs on a controller that is not initialized at boot time. Always back up and restore or duplicate the entire system disk. For different hardware, enable Adjust dissimilar hardware afterwards (M.I.R.), and supplement the adaptation manually under Tools > Change Computer Properties if needed. See Dissimilar hardware (M.I.R.).

The computer does not start from the boot medium​

Set the boot order in the BIOS/UEFI setup or in the boot menu so the medium starts first; the order chosen in the boot menu usually applies to the current start only. Disable Secure Boot if the Windows PE medium does not start, start in the same boot mode (UEFI or Legacy/CSM) in which the medium was created, and use a USB 2.0 port if the stick is not detected on a USB 3.0 port. If the medium is still not detected, recreate it. See Boot medium and O&O DiskImage ToGo.

A disk, a RAID array or the network is missing in the recovery environment​

The driver of the storage controller, the NVMe SSD, the RAID controller or the network adapter is missing. Load it on the Drivers tab of the O&O System Settings dialog from a USB stick or a driver CD. In most cases the cause is a missing RAID, AHCI or NVMe driver, or a changed BIOS setting such as the RAID/IDE/AHCI mode. See Load drivers.

A BitLocker drive cannot be backed up or restored​

In the recovery environment, an encrypted volume must be unlocked with the recovery key first – the user password and the TPM do not work there. A restored drive stays encrypted only when it was backed up with the direct forensic method; after a backup of used sectors it is no longer encrypted. See BitLocker.

The validation fails​

Possible causes are a wrong password or corrupted data, errors during compression, backup files modified by the user or by other programs such as antivirus software, and defective storage media. A backup that fails validation cannot be relied on: create a new backup and validate it. Let every validation run to the end; after Skip or Cancel the result is not guaranteed. See Backup information and validation.

A backup cannot be mounted​

Only backups that are available locally can be mounted; copy a backup from a network drive to a local disk first. Install the O&O DiskImage driver when the program asks for it. In a Remote Desktop session, log in again if mounted drives do not appear. If Windows reports that a VHD/VHDX file could not be mounted or contains no recognizable partitions, the message can usually be ignored. See Virtual drives.

Access denied on a mounted drive​

The files were created under another Windows installation or user account, so their security IDs differ. If necessary, enable the Administrator account and access the files with it – carefully, because administrator rights allow far-reaching changes.

Two disks with the same signature​

After a duplication, O&O DiskImage changes the disk signature of the target, so both disks can be connected at the same time. If a cloned system is deployed to several computers, change the computer name and the SID with Tools > Change Computer Properties from the boot medium. See System tools.

A backup of changes cannot be created or restored​

A backup of changes needs its base backup: the last backup for incremental backups, the last full backup for differential backups. A restore needs the whole chain – the full backup and all backups of changes up to the desired state. Keep them together; merge a long chain into a new full backup with Tools > Merge Backup. See Backup of changes.

The copy becomes inconsistent during a duplication​

If the source drive is not locked, O&O DiskImage buffers changes in a cache of limited size; when the cache is full, changes reach the target directly and the copy can become unusable. Lock the drive under Copy options > Advanced > Read process, or stop write-intensive processes such as a defragmentation during the copy. See Clone drives.