Felix Zumstein

I can only replicate this with a quickstart project with the `--standalone` option, i.e., if the VBA code is embedded, but not when you rely on the xlwings add-in. Not...

Do you have any other add-ins around? see e.g.: https://github.com/xlwings/xlwings/issues/1469

That's right: * `xlwings quickstart zombie`, then replacing the main function with above snippet and hitting `Run main` works, i.e. cleans up Excel after quitting it. * `xlwings quickstart zombie...

Good catch! Yes, I can indeed replicate this!

thanks @panda-34 for investigating and opening an [issue with pywin32](https://github.com/mhammond/pywin32/issues/1870)!

This is fixed in 0.27.9, but since it's only a hack, I am leaving the issue open to see if the corresponding pywin32 issue (linked above) gets some attention.

To keep things simple, I have a strong preference for introducing a version check so that VBA/Python matches. It's what I already do with the new remote interpreter. With regard...

Isn't this an effect of Excel restarting and offering to recover?

Which would be in line with your observation that this only happens when the file is saved?

@wkschwartz any thoughts on this?