I have a small excel file that is launched by the scheduling application every 15 minutes.
Functions in excel cells read data from different places on the network and store them in cells in this excel file. Everything works perfectly.
The VBA code then saves the file and executes Application.Quit.
In a previous excel version, it worked great. Starting with the upgrade to 2016, Application.Quit closes the "excel interface", but the task manager shows a hundred "Excel.exe" that are still sitting there, using up to 40 MB of memory.
The attached image shows only five excel.exe in the task manager, since at the moment the computer is running less than two hours. But after 24 hours there are about 100 of them. Thus, the computer crashes in a few days.

Thanks for the ambulance. I am not sure that I should give my answers here by editing my original question.
Here is the code. Actual cell values ββare updated in the cells themselves. There is an Add In that reads values ββfrom some PLCs in our factory. Everything works perfectly.
Private Sub Workbook_Open() Application.CalculateFull ActiveWorkbook.Save Application.Quit End Sub
When the excel file is launched, it is updated and closed. This worked for many years until we upgraded to 2016. Application.Quit will force excel to completely go away. Not now.
source share