If your running MapBasic application want to shut down the current session of MapInfo Pro, I would recomend using the End MapInfo statement.
I had a look through the release notes for v2021.1 to see if any caught my eye. I don't see anything that obviously would prevent MapInfo Pro from being shut down.
Do you have any tables open or connections to databaes open, when you try to shut it down?
Your experience clearly state that something has changed but I can't detect what.
Would you be able to try to use the End MapInfo statement instead to see if that makes any difference?
------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
------------------------------
Original Message:
Sent: 03-04-2026 08:18
From: Nicholas Evanish
Subject: MapInfo Pro v2021.1 Build 33 Process ID hangs while ending MapInfo
Peter,
Good morning. The job runs to completion; however, when the program attempts to kill the MapInfoPro.exe (using a MapBasic program referenced in my first post) that MapInfoPro.exe is no longer closing.
It looks like what is happening is the MapInfoPro.exe instance is left orphaned with a very small amount of memory usage recorded.
For example, this morning a process ran at 0015, and it completed around 0135. However, the MapInfoPro.exe process stayed running on the server (see image):

I hope this helps give more clarification as to what is now happening. This solution had worked up until (2/25/2026).
------------------------------
Nicholas Evanish
Senior Program Analyst
------------------------------
Original Message:
Sent: 03-03-2026 03:19
From: Peter Møller
Subject: MapInfo Pro v2021.1 Build 33 Process ID hangs while ending MapInfo
Hey Nicholas
Are you saying that your jobs don't shut down MapInfo Pro anymore when they are finished?
If that's so, do you know where they halt/stop in the execution?
------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data