Still problems with COM surrogate

At least a couple of months ago this was brought up but, there are still problems with COM surrogate.

I am posting this here (OS specific) because I am assuming this is a Win only problem, but could be wrong.

I deal with a lot of files and am constantly having to shut down LIghtBurn, go into Task Manager and close all the instances of COM surrogate in order to move or delete a file.

When we close a file it’s corresponding COM surrogate process needs to also close.

Very big pain in the rear.

Since this is the closest thing to a bug report mentioned within the software, am assuming that LIghtBurn staff monitor these posts. Someone please let me know if that is not the case. Surprised there isn’t a category here dedicated to bug reports.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.