ntbackup: File restore from old bkf files on current Windows

Microsoft removed ntbackup from all OS versions after XP and Windows 2003. However, there is still the option of restoring old bkf files free of charge. A guest post by Jo Arnold

Ntbackup was available on Windows XP, Windows Server 2003, Windows 2000 and Windows NT 4.0. The backups created with ntbackup at the time packed everything into a file with the ending “.bkf”. Ntbackup wasn't just intended to back up the SystemState – which is roughly comparable to today's restore points. Ntbackup can be operated using scripts and with Scheduled Tasks a good automation system could be created that could write to disk as well as tape drives.

Since e.g. B. XP was still supported until 2014, so there are probably some people who still have bkf files on their data partitions. Unfortunately, you can no longer open the created bkf files without preparatory work. Before deleting such backup files, some people would like to know, just to be on the safe side, whether there is something in them that was previously considered lost or forgotten.

However, the ntbackup.exe required to open the bkf files does not run automatically because it requires three very old DLL files: ntmsapi.dll, query.dll and vssapi.dll. It is therefore very pleasing that someone has already taken the trouble to look through the old Windows installation media and made this small collection available as a ZIP.

Once extracted, ntbackup.exe and the three DLL files end up in a folder and can be started immediately.

What needs to be taken into account

A SystemState backup created with ntbackup is only suitable for the system at that time on the hardware at that time. It wouldn't produce a good result if System32 and the registry from XP ended up in Win 11. At best, perhaps a chimera with a usable taskbar and start menu would be created? But it is more likely that Windows is destroyed.

However, a SystemState backup can also include the file system or parts of it with user data, or the bkf file only contains data from the file system.

Anyone who uses ntbackup to view old bkf content and possibly starts a backup of files on a system that is not the original source should normally deactivate the restoration of the original authorizations (SID) available in ntbackup. There are many reasons for this, the explanation of which would go beyond the scope. The authorization of the target folder is then automatically adopted for the restore.

The following path C:Users%username%AppDataLocalMicrosoftWindows NTNTBackup is also created. A log file is created for each action in the Data subdirectory. Read bkf structures but no files are saved in the catalogsXY subdirectory.

Ntbackup is legacy and using it in production for purposes other than those described here is neither an advisable nor future-proof solution.

Happy restore with ntbackup

Info and download: