BA735: Could not delete directory

Error code	Product	Applies to
BA735	BackupAssist	For BackupAssist 9.0.0 or later.

Description

During a File Protection (file replication) backup, BackupAssist keeps the destination mirror in step with the source, which includes removing folders that no longer exist in the source. BA735 is recorded when it could not delete one of those folders on the destination. The report's File Replication section shows the folder and the Windows error - most often error 145, "the directory is not empty", meaning a file inside it could not be removed first.

Common causes:

• A file inside the folder is locked or in use - commonly by antivirus or RMM software, or an open application handle.
• The Backup User Identity does not have delete permission on the destination or share.
• The full path exceeds the Windows path-length limit.
• On older builds, BackupAssist's own catalogue integrity file (~$bkint.db) could be left behind and block the delete - resolved by upgrading.

Resolution

Resolution 1 - Upgrade to a current build (recommended)

An older defect where BackupAssist's own ~$bkint.db integrity file was left in a folder and blocked its deletion has been fixed. If you are on an older version, upgrading to a current build resolves that case.

Resolution 2 - Clear locks and check permissions

1. Exclude the destination path from antivirus and RMM real-time scanning, which frequently hold files open.
2. Confirm the Backup User Identity has permission to delete on the destination or share.
3. If the path is very long, shorten the destination path or enable Windows long-path support.
4. Check for applications holding files open in the affected folder.
5. Re-run the backup.

Note on the backup report

The File Replication section shows this as: Could not delete directory, together with the Windows error code (often 145, directory not empty) and the folder path.

Last updated	Created	Further assistance
15th Sep 2026	18th Aug 2015	BackupAssist Support page

Download a free 30-day trial