Practical review identifies reasons for lingering EXCEL.EXE processes after C# automation, suggesting alternative solutions.
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.
No takes yet. Share an insight, caveat, or question.
Go Komura (2026) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: