Yeah, that error code is a pain. It usually pops up when a background service or a driver tries to do something that requires a transaction, but the Kernel Transaction Manager (KTM) is corrupted or disabled. I've seen it on Windows Server 2016 and even on Windows 10 Pro. The fix is straightforward, so let's get to it.
The Direct Fix: Reset the Kernel Transaction Manager
Open an elevated Command Prompt (right-click > Run as administrator) and run these commands in order:
net stop ktmrm
net stop ktm
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\KtmRm" /v Start /f
reg delete "HKLM\SYSTEM\CurrentControlSet\Services\KTM" /v Start /f
net start ktm
net start ktmrm
sc query ktmrm
sc query ktm
This stops the services, deletes the registry keys that might be set to disabled, and restarts them. Then check the status – both should say RUNNING.
If the services won't start, you might need to set the start type manually:
sc config ktm start= demand
sc config ktmrm start= demand
net start ktm
net start ktmrm
What if the services won't start at all?
If you get an error like 'The service cannot be started' – that's a deeper problem. The KTM service depends on the Microsoft Distributed Transaction Coordinator (MSDTC). Check that too:
net start msdtc
If MSDTC is stopped, start it. Then retry KTM.
Why This Fixes It
Windows uses the Kernel Transaction Manager to handle atomic operations – things like file system transactions or registry writes that need to either fully happen or fully roll back. When KTM gets into a bad state, any process that tries to call CreateTransaction() gets this error. Deleting the Start registry values forces the services to use their default configuration, which is demand start. That's why the error disappears – the transaction manager can actually process the request again.
I had a client last month whose backup software started throwing this error every night. It was because a previous Windows update had changed the KTM service startup type. Two commands and it was fixed.
Less Common Variations
Sometimes the error isn't about the service state. Here are other triggers I've seen:
- Corrupted TxF (Transaction NTFS) metadata: If you're using Transactional NTFS (like with some older database apps), a corrupted $TxF file can cause this. Run
chkdsk /fon the affected drive. - Antivirus interference: Some security software hooks into transaction APIs. Temporarily disable your AV and see if the error goes away. If yes, whitelist the app that's throwing the error.
- Resource exhaustion: If the system is low on memory or handles, KTM can't create new transactions. Close memory-hungry apps or reboot.
- Driver issues: Outdated storage drivers sometimes cause this. Update your chipset and storage controller drivers.
Prevention – Keep It From Coming Back
Now that it's fixed, here's how to avoid a repeat:
- Don't disable KTM or KtmRm manually. Some 'system optimizer' tools do that. Avoid them.
- Keep Windows updated. Microsoft has fixed several KTM bugs over the years. Install those updates.
- Check your database software's requirements. If you're running an app that relies on TxF, you might need to switch to a newer version because Microsoft has deprecated TxF in newer Windows versions. That's a bigger project, but worth planning.
If the error reappears after a week, you might have a deeper corruption. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files.
That's it. You should be back to work. If not, drop me a comment and I'll help you dig into the event log.