From my experience, the program seems to keep a process hanging when an add-in or macro runs but doesn't dispose of the objects correctly. If the object is hanging in memory then solidworks stays open.
Aside from that, there was an instance where I was working with a complex part file and trying to import dimxpert objects into the drawing automatically. When I updated the drawing to refresh the dimensions, SolidWorks would crash but leave the process running in the background.
It's hard to say what could cause it without knowing more about your or your coworker's workflow.
Do you have custom add-ins or macros? Is it one particular file that seems to give you grief?
Could you report this issue to VAR?
It never happens to me.
My guess, as Alex Burnett stated, is it is probably caused by our third party program that generates our properties(CustomTools). Either that or the macro that we use to send stuff to our E.R.P.
I will forward this to CustomTools, would you like me to report it to my VAR still?
Edit: Here is a few screenshots showing the issue occuring. In this case, it was caused by a setting in SolidWorks, don't know which tough. The reason I say it was caused by a setting is that I fixed the problem by restoring the settings to our default settings of 2016.
I was trying to open a drawing of an assembly we use for the layout of our stickers. While trying to open the drawing, it would prompt me to save or discard a certain assembly. No matter if I saved or discard the changes, the opening action would interrupt itself and I wasn't able to open the drawing afterwards. When I closed SolidWorks, the process hung
Window prompting me to save popped up. I pressed Discard changes. Program continues responding, the load bar at the bottom left corner is still present tough it doesn't load anymore.
If I press on X to close the program, it prompts me to save or discard changes. No matter which I select, the program does what I ask, then closes but the process remains hanging.
Here is the process still running without SolidWorks running
It appears from your screen shots that CustomTools is an add-in that loads with SolidWorks since the icon is in your task pane on the right hand side. If that's the case, it's likely that the add-in is watching events to try and gather the current model data whenever something changes. This requires creating and disposing of objects constantly. All it takes is one missed object in one function within the program that isn't disposed in order to cause something like this to happen.
Have you tried to go into your add-ins menu and disable CustomTools and follow the same workflow that your screenshots show? Does it still hang?
It is indeed an add-in that loads with SolidWorks. The instance that I spoke of only happens to one person in particular on a specific file. The process hanging happens to all of us tough.
We haven't tried going to the add-in menu to disable CustomTools as SolidWorks is ''closed'' when the problem occurs. We would have to think of closing it before SolidWorks in case the problem occurs.
Thanks for the troubleshooting tips Kevin Chandler, they are dully noted and I will try them a bit later as I'm in a bit of a rush today.
If you open SolidWorks and click the arrow next to options and then click add-ins.
Uncheck your add-in in this column to prevent it from starting with SW. Then close SW and verify your process has terminated.
Now you can start solidworks the add-in won't load. Try your workflow again to see if the issue still occurs.
Yes I understand that Alex, the problem doesn't occur from the get-go at the start-up of SolidWorks. It happens somewhere between the opening and the closing. I can go 2 weeks without getting the problem and then get it 3 times in the same day.
Working with CustomTools disabled is not an option either.
When I open multiple big assemblies I would also get where SW would stay open in my Background after closing. Mostly because I would reach over 50% ram on my machine.
Sysinternals (bought out by MS has Process Explorer Process Explorer - Windows Sysinternals | Microsoft Docs (no install, just run).
It's Task Manager +++.
After it starts, select "Show Lower Pane":
Then select SW in the upper pane and all of its related stuff is shown in the lower pane.
Close SW the normal way and watch Process Explorer.
SW and it's dependent(s) in the upper pane should go away as should all of the stuff in the lower pane.
If anything remains, perhaps this will be a further clue to the mystery.
If you don't want to keep seeing this:
Right-click the EXE file and select Properties. Check Unblock and then Apply & OK.
(This is the 32 bit version, I already did this for the 64 bit EXE)
There's also "openfiles.exe" which will show what's open and by whom/what.
It's an MS command line tool.
I think you need to install a service which can close the unwanted service running in background. One that can detect that you have closed the complete program and could prompt you if you would like to shut down relevant service as well. There are such utilities available on the internet. Try one available on this website: https://www.coolutils.com/