Share via

MSDTC Service Fails to Start — Service-Specific Error Code -1073737669, Local DTC Missing from Component Services

Adam Haikal 0 Reputation points
2025-08-13T09:53:32.8233333+00:00

Description

On my Windows 11 Enterprise machine, MSDTC has suddenly stopped working. It previously worked fine but now fails to start, and the Local DTC entry is missing from Component Services.

Environment

  • OS: Windows 11 Enterprise 24H2, Build 26100.4770
  • Hardware: Physical laptop
  • Network: Local workgroup (not domain-joined)
  • MSDTC usage: Required for distributed transactions to remote machines

Issue Details

  • Worked previously, stopped suddenly during multiple debug sessions — no Windows updates or configuration changes done immediately prior
  • When starting the service:
Windows could not start the Distributed Transaction Coordinator on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -1073737669.
  • In Component Services → My Computer:
    • Local DTC entry is missing
    • On “Refresh all components”:
An error occurred while processing the last operation.
Error code 8004E00F - COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator. The event log may contain additional troubleshooting information.

Request:

I need guidance on how to:

  1. Restore Local DTC in Component Services
  2. Resolve service start failure with error code -1073737669
  3. Ensure DTC can again communicate with remote machines for distributed transactions
Windows for business | Windows Server | Networking | Other

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Domic Vo 21,470 Reputation points Independent Advisor
    2025-10-07T11:34:55.5433333+00:00

    Dear Adam Haikal,

    Based on your description, it appears that the Local DTC configuration may have become corrupted or unregistered, which is preventing the service from starting and causing the missing entry in Component Services.

    Recommended Steps to Restore MSDTC Functionality:

    1. Reinstall MSDTC Components Open Command Prompt as administrator and run the following commands:
      • Code 
             msdtc -uninstall

    msdtc -install ```

     This will remove and reinstall the MSDTC service and its registry entries.
    1. Reset MSDTC Configuration After reinstalling, run:
      • Code 
             msdtc -resetlog
        This clears the transaction log and helps resolve corruption-related issues.
    2. Verify Service Status Open Services.msc and ensure that Distributed Transaction Coordinator is set to Automatic and is running. If it fails to start, check the System Event Log for any additional error details related to code -1073737669.
    3. Restore Local DTC in Component Services After reinstalling MSDTC, open Component Services again. Navigate to Console Root > Component Services > Computers > My Computer > Distributed Transaction Coordinator You should now see the Local DTC entry restored.
    4. Enable Network DTC Access (for remote transactions) Open Component Services, right-click Local DTC, and choose Properties
      • Under the Security tab: Check Network DTC Access Enable Allow Inbound and Allow Outbound Enable No Authentication Required (or adjust based on your environment) Click OK and restart the MSDTC service.
    5. Firewall Considerations
      • Ensure that the following ports are open for MSDTC communication: TCP 135 (RPC Endpoint Mapper) Dynamic RPC ports (range can be configured) You may also need to allow COM+ Network Access through Windows Defender Firewall.

    If this guidance proves helpful, feel free to click “Accept Answer” so we know we’re heading in the right direction 😊. And of course, I’m here if you need further clarification or support.

    T&B,

    Domic Vo

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.