November 2026
BackupKit 2026.11.3
A big backup to a USB disk keeps its pace from the first file to the last, and a restore that runs into a problem keeps what came back.
Backups
- • A big backup to another drive keeps its pace. Each file backed up to a USB disk or another drive of your PC cost a little more than the one before, so a backup of a whole laptop slowed to a crawl after its first hour. The last file now costs what the first did: in our test, 176,000 files went to a USB disk in about the time Windows takes to copy them itself.
- • The progress bar moves during a big file. A large video or disk image backed up to another drive held the bar still until it was done. It now moves as the file is copied.
- • Stop takes effect in the middle of a big file. Stopping a backup to another drive waited for the file being copied to finish. It now stops at once, and no half-copied file is left behind.
- • BackupKit stays quick after a big backup. Browsing your PC’s folders after a large backup was slower until BackupKit was restarted. It no longer is.
Backups to servers and cloud storage
- • Many small files go much faster to SFTP, FTP and FTPS servers. BackupKit used to wait for the server’s answer at every step of every file. It now sends those steps together and spends far less time on its own bookkeeping. This speeds up backups that are not compressed into one file, and file transfers.
- • Big files no longer crawl to a distant SFTP server. Each block used to wait for the server’s reply, so the distance to the server set the speed. Now your connection does.
- • Uploads to OneDrive are up to twice as fast. Files up to 250 MB now go in one piece instead of being cut into chunks. Google Drive and big files on Dropbox gain too, by less. If you are on a slow or metered connection, Settings > Transfers has a new option, Upload big files in chunks, so that less is sent twice after a drop.
- • A dropped connection no longer ends a backup. SFTP, FTP, FTPS, Google Drive, OneDrive and Dropbox now wait up to two minutes for the connection to come back, then carry on. A big file on Dropbox, over 150 MB, used to fail at any drop.
- • Work on servers and cloud storage no longer slows down the more you use BackupKit. BackupKit keeps a record of what it has listed on each storage. Replacing a file there, or renaming or deleting a folder, read that whole record, so it got slower over time: about two seconds a file once the record held a few hundred thousand items. It now reads only what it changes.
Creating a backup
- • Add a storage while you choose where the backup goes. The list of storages in the folder picker now has Add storage, so you can connect MEGA, Google Drive or any other storage without leaving Create Backup.
- • The folder picker no longer freezes on a big folder. Opening a folder of thousands of files, or a USB disk that had gone to sleep, held up the window while it loaded. It now loads without holding anything up.
Restores
- • A restore that runs into a problem keeps what came back. If some files could not be restored, everything that had come back was thrown away. Now the files that weren’t there are put in place, nothing that was there is replaced, and BackupKit names what didn’t come back.
- • One file that can’t be restored no longer stops the rest. A file with a very long path ended the restore of a compressed backup, and nothing came back. It now fails on its own, named, and the rest is restored. Long paths that the temporary folder pushed over Windows’ limit are restored too.
- • Restoring to the original folder keeps what you’ve added since. A restore replaced each folder whole, so files created after the backup went to the Recycle Bin with the old folder, and so did the folder’s own icon and settings. It now puts back the backup’s files one by one and leaves everything else as it is.
- • A file renamed only in its capitals is restored over. If a file or folder had been renamed since the backup only in its upper and lower case — Report.docx to report.docx — the restore failed. It now replaces it.
- • A restore’s temporary files are removed right away. Restoring a compressed or encrypted backup unpacks it into a temporary folder. If its closing message was left open, that copy, gigabytes at times, stayed on the disk until BackupKit next started. It is now removed before the message appears.
- • Restoring to the original folder on a server is faster. On FTP, SFTP, a NAS or Dropbox, a restore listed the whole folder again for every file it replaced. It now looks up each file on its own.
Files and transfers
- • My Computer is now This PC, laid out the way File Explorer has it. Desktop, Documents, Downloads, Music, Pictures and Videos come first, then your disks and USB drives, then your mapped network drives, each group under its own heading. Documents, Music, Pictures and Videos used to sit apart, under “Personal folders” in the folder tree. They are now with the rest, in the tree too, in the same order.
- • Copying files on your PC shows how far it is, and can be stopped. Copying a big file or folder in BackupKit’s file browser — to a USB disk, say — showed “Copying items...” until it was done, with no way to stop it. It now shows how much has been copied out of how much, with a button that stops the copy. A stopped copy leaves no half-written file.
- • Pausing and resuming a transfer straight away no longer loses a file. Resumed within a second or so, a transfer could call itself complete while a file was still on its way. When the transfer was a move, the original was then removed, and the file ended cut off at the destination and gone from where it was. A transfer now pauses once the files in flight have stopped.
- • A stopped upload no longer leaves a broken file on an FTP or SFTP server. Close the stopped transfer, and BackupKit removes the part it had sent under the file’s real name. Pause still keeps it, so Resume can carry on from it.
- • Stopping an FTP transfer no longer breaks the connection. After a stopped transfer, every later backup or transfer on that server could fail with “Malformed PASV response” until BackupKit was restarted. The connection is now closed and opened afresh.
- • Moving a folder to another drive works. Moving a folder from one drive to another in the file browser, such as from your desktop to a USB disk, failed with “Source and destination path must have identical roots”. BackupKit now copies it, shows how far it is, and removes the original once all of it has arrived. Stopping it leaves the original as it was.
- • Names sort the way File Explorer sorts them. Sorted by name, a folder called “Symphony No. 10” came between “No. 1” and “No. 2”. Numbers in names now count as numbers, so 2 comes before 10, in the file list and in the folder tree.
- • BackupKit started from a command prompt or a script is complete. Started that way, BackupKit could come up without some of its parts, backups and Scheduled Transfers among them, until it was next restarted.