Unable to delete gcode files after print, when uploaded to Web UI

Generating gcode files to a folder on my PC, then uploading to web UI to print. After print is done or stopped, I’m unable to delete the gcode files at all on my PC, get this error:
“The action cannot be completed because the file is open in COM Surrogate”.

Have not found any quick workarounds yet, will be trying to exit browser and then delete files after I send this… I suspect the web gui has left the files open.

Suggestions?

I’ve used this for years, it might not be the right way to solve your problem…but it works.

Thanks. I’m kind of hoping that maybe Sovol will come up with a fix for it, but I got around it by using task manager to stop the “COM Surrogate” process. That is what’s locking the files as soon as you use the download feature in the web interface.

1 Like

Isn’t this more an issue that the file is still opened in OrcaSlicer for editing ?
If you close the project in Orca is this issue still present ?

Maybe, I had not thought of that, but I’ll check it as soon as I slice another file.
Thanks.

I did some testing and it’s not an issue of the file being open in Orca slicer. I closed Orca after uploading my gcode file to the printer using the web interface and then I still could not delete the gcode file on my PC. Any file that is transferred from PC to printer using the upload features of the web interface cause all files to be locked by the “COM Surrogate” process. The only way to release them for deletion is to shut down the COM Surrogate process in the Task Manager.

So this is definitely a bug in the upload of the web interface.

The trouble related with COM Surrogate is explained here Fix: File is Open in COM Surrogate The solution 4 is related to the codecs to display the previous in your file explorer. I trust that is more an OS issue : Mainsail (the webui used by Klipper in the Sovol implementation) is not in charge (and not allowed by the browser) to operate directly with your own filesystem.

I’ve disabled DEP for that and I’ll see if that helps. Thanks.

Disabling DEP for that COM Surrogate in SysWow64 fixed this issue for me.
Thanks for the link.