Kernel Transaction Manager (KTM)
Before Vista, applications had to do a lot of hard work to recover from errors during the modification of files and registry keys. Windows Vista implements a generalized transaction manager called the Kernel Transaction Manager (KTM) which provides “all or nothing” transaction semantics. This means that changes are committed only when the associated transaction is completed and commits.
The KTM is extensible through third-party resource managers and coordinates between the transaction clients (the applications) and the resource managers.
The registry and NTFS have been enhanced to provide transaction semantics across all operations and is used by the Windows Update service and the System Protection services.
Vista also picks up the Common Log File System (Clfs.sys) introduced in Windows Server 2003 R2, which provides efficient transaction logging facilities.
Transaction APIs
Transactions can span modification across one or many registry keys, files, and volumes. By using the Distributed Transaction Coordinator (DTC) transactions can coordinate changes across files, registry, databases, and MSMQ.
Transactions are relatively easy to use in Vista with the introduction of the new transaction command, which allows scripts to participate in the transaction process.
The Windows API also has a new set of API functions:
-
CreateTransaction
-
SetCurrentTransaction
-
CommitTransaction
-
RollbackTransaction
The kernel has IoCreateFile, which now has an ExtraCreateParameters which specified the transaction handle.