What question did this study set out to answer?

The aim is to understand why EXCEL.EXE processes remain active following C# automation of Excel.

July 29, 2026Open Access

Why EXCEL.EXE Processes Remain After C# Excel COM Automation — Reference Release Patterns and the Replacement Decision (archived 2026-07-27)

Key Points

The aim is to understand why EXCEL.EXE processes remain active following C# automation of Excel.
Analysis of COM reference counting and the RCW mechanism
Evaluation of the two-dot rule trap and Marshal.ReleaseComObject
Comparison of COM interop with Open XML SDK and ClosedXML
EXCEL.EXE processes persist due to improper reference management in C# automation.
The two-dot rule trap complicates object lifetime, resulting in orphan processes.
Alternatives like Open XML SDK provide a more reliable approach for Excel interactions.

Abstract

A practical look at why EXCEL.EXE processes remain running after automating Excel from C# via Microsoft.Office.Interop.Excel, explained through COM reference counting and the RCW mechanism. Covers the two-dot rule trap, the Marshal.ReleaseComObject vs. GC release patterns, the last-resort technique of identifying the PID from the window handle, and when to replace COM interop with Open XML SDK / ClosedXML. Archived version of https://comcomponent.com/en/blog/excel-com-interop-process-remains/, as published on 2026-07-27. The live article is maintained and may change after this date. First published 2026-07-03.

اسأل الذكاء الاصطناعي

Bookmark

View Full Paper