Troubleshooting Guide: Error 1369 – Registry Subtree Transaction State Incompatible
Why This Error Happens
Error 1369 occurs when the Windows Registry’s Kernel Transaction Manager (KTM) detects that a registry subtree is either mid-transaction or locked in a state that conflicts with a new read/write request. This typically happens due to an abruptly terminated transacted registry operation (often caused by a system crash, forced shutdown, or power failure) that leaves stale transaction metadata attached to a registry key. Corrupted registry hive files or improperly closed transactional sessions from applications using RegCreateKeyTransacted or similar APIs are the most common root causes.
Step-by-Step Resolution Guide
Step 1: Run System File Checker and DISM
- Open Command Prompt as Administrator (search “cmd”, right-click, “Run as administrator”).
- Execute:
sfc /scannowand allow it to complete fully. - Follow up with:
DISM /Online /Cleanup-Image /RestoreHealth - Restart the machine once both commands finish successfully.
Step 2: Check and Repair Registry Hives
- Navigate to
C:\Windows\System32\configand verify no.LOG1,.LOG2files are abnormally large or corrupted (indicates incomplete transactions). - Boot into Advanced Startup (Settings > System > Recovery > Advanced Startup > Restart Now).
- Select Troubleshoot > Advanced Options > Command Prompt.
- Run:
chkdsk C: /f /rto repair underlying disk errors that may be corrupting the transaction log.
Step 3: Clear Stale Kernel Transaction Manager (KTM) Data
- Open Registry Editor (
regedit) as Administrator. - Locate the specific subtree referenced in the error (check Event Viewer under Windows Logs > System for the exact key path).
- Right-click the affected key, export it as a backup
.regfile first, then delete and manually recreate the key structure if it’s non-critical. - Avoid deleting system-critical keys (e.g., under
HKEY_LOCAL_MACHINE\SYSTEM) without verified backups.
Step 4: Restore from a System Restore Point
- Open “Create a restore point” from the Start menu search.
- Click “System Restore” and choose a restore point dated before the error first appeared.
- Follow the wizard to roll back system and registry state, then restart and confirm the error is resolved.
Alternative or Verification Steps
- After completing the steps, reproduce the original action that triggered Error 1369 (e.g., installing software, running a script) to confirm it completes without the error.
- If the issue persists, use
Event Viewer(Windows Logs > System, filter by Event ID 1369) to identify the exact faulting module, and consider a targeted in-place upgrade repair via Windows 11 installation media if registry corruption is widespread.