November 2026

BackupKit 2026.11.2

One folder that can’t be read no longer stops a whole backup, and BackupKit no longer piles up Windows handles the longer it runs.

Fixes

  • • One folder that can’t be read no longer stops the whole backup. A folder that was in use by another program, had just been removed, or sat on a disk that wasn’t ready ended the run with “Failed to load folders”, and nothing was backed up. BackupKit now backs up everything else and names that folder and the reason in the backup’s activity. The backup shows as completed with errors, and a restore from it warns that it is incomplete.
  • • Folders with a path of exactly 258 or 259 characters no longer end a backup. Windows could find them but not list them, which ended the run with the same message. They are listed now. With Windows’ long paths setting off, which is the default, a path too long to copy is still left out, such as a file whose full path reaches 260 characters, but each one is named and the rest of the backup goes on.
  • • BackupKit no longer piles up Windows handles while it runs. BackupKit looks at the clipboard once a second, so you can paste files copied in File Explorer. Each look left handles behind, hundreds a minute at times, for as long as the app stayed open. It now does this on one thread and leaves nothing behind.