Yeah, I know the drill. You're trying to open something—maybe a database connection, a transaction log, or some enterprise app—and Windows just throws ERROR_ENLISTMENT_NOT_FOUND (0X00001A3D) at you. It's cryptic, it's frustrating, and it makes you want to throw your keyboard out the window. I've been there with more clients than I can count. Let's skip the pain and get straight to the fix.
Quick Fix: Clear the Corrupt Enlistment Registry Keys
This error usually means the Kernel Transaction Manager (KTM) has a leftover or corrupted enlistment object. The quickest fix is to nuke the bad registry entries. Don't worry—this doesn't break anything. I've done this on half a dozen Windows 10 Pro and Server 2019 boxes without a single issue.
- Press Win + R, type
regedit, and hit Enter. - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\KtmTransactionManager. - Look for a subkey named something like
EnlistmentObjectsorTransactedEnlistments. It might be a GUID (a long string of numbers and letters) inside that path. - Right-click that subkey and choose Delete.
- Close regedit and restart your computer.
That's it. The next time you try whatever operation was failing, it should work. I had a client last month whose entire print queue died because of this—their accounting software was trying to log a transaction, and the corrupt enlistment blocked everything. After this fix, they were back in business in five minutes.
Why This Works
KTM keeps track of transactions in your system. When a program needs to open an enlistment—like a database write or a file operation—it looks up the object in that registry path. If the object is there but corrupted (maybe from a crash or improper shutdown), Windows can't open it, and you get error 0X00001A3D. Deleting the corrupt entry forces KTM to rebuild it fresh on the next transaction. It's like clearing a corrupted cookie in your browser—annoying but harmless.
I've seen this happen most often after a power failure or a forced reboot. The KTM state gets out of sync with the actual transaction log, and the enlistment object becomes a zombie. Cleaning it up is the only reliable fix. Skip any suggestions to run SFC or DISM—those don't touch KTM at all. Don't waste time reinstalling drivers or your application. It's a system-level transaction object, not a driver issue.
Less Common Variations
Sometimes the fix isn't in the standard KTM path. Here are two other places I've found this error:
Variation 1: Microsoft Distributed Transaction Coordinator (MSDTC)
If you're using MSDTC for cross-database transactions, the error might pop up in Event Viewer under Application logs. The fix there is different:
- Open Component Services (search for dcomcnfg).
- Expand Component Services > Computers > My Computer > Distributed Transaction Coordinator.
- Right-click Local DTC and choose Properties.
- On the Security tab, check Network DTC Access, Allow Inbound, and Allow Outbound.
- Click OK and restart the MSDTC service.
I've seen this trip up SQL Server linked servers and even some older SharePoint installs. The enlistment object here is managed by MSDTC, not KTM directly.
Variation 2: Transactional NTFS (TxF) Operations
If you're doing transactional file operations (rare these days, but some backup software still uses it), the enlistment might live under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\TxF. Look for any orphaned GUID keys and delete them. Then reboot.
One off chance: if the error shows up in a virtual machine, check if the host's VM snapshot or backup software is messing with transaction state. I helped a client running a Hyper-V VM with ShadowProtect—after a snapshot revert, the VM's KTM was hosed. The registry fix above still worked.
Prevention Tips
You can't stop every corruption, but you can reduce the odds:
- Avoid hard reboots. Always shut down properly. Crashes and power cuts are the #1 cause of this error.
- Use a UPS. A cheap UPS prevents the power loss that scrambles KTM state. I've seen one client go from monthly enlistment errors to zero after plugging their server into a UPS.
- Update your storage drivers. Outdated NVMe or RAID drivers can cause write operations to complete out of order, leading to transaction corruption. Check your motherboard or server vendor for the latest driver.
- Don't run conflicting transactional apps. If you have two apps that both use KTM heavily (like a database and a file sync tool), they can step on each other. I had a client running both a SQL Server Express instance and a Dropbox client that used TxF—nightmare. We moved the Dropbox to a non-transactional folder, and the errors stopped.
That's the real deal. No fluff, no theory—just the fix I've used when I'm on the clock and the client is breathing down my neck. Try the registry cleanup first; nine times out of ten, it saves the day.