When Control-M Managed File Transfer is based in windows, file transfer jobs are hanging in executing status. Transfer starts but it doesn't proceed.

Set the Control-M Agent in debug mode (by running agdbglvl 4) and at the ctmaft.log you will find messages like below:
Once complete, turn off debug with the command:  agdbglvl 0

2017-12-01 12:34:33,916 INFO [Thread-119822] (AgentNotifier:47) - Sending <FILE_TRANS 0ttw1 00023 1300790> to 127.0.0.1:31647
2017-12-01 12:34:34,025 ERROR [Thread-119805] (AgentNotifier:54) - Unable to notify:
java.net.ConnectException: Connection refused: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)

This "Sending <FILE_TRANS xxxxxxxxxxxxxxxxxx> to 127.0.0.1:31647" occurs thousand times in short time.
The connection refused is about half of those times

OR

2018-06-19 14:02:06,439 WARN [Thread-35] (AFTConfigManagerImpl:140) - Key not found: com.bmc.aft.configurable.disableWinLocalImpersonation
2018-06-19 14:02:06,439 INFO [Thread-35] (WinLocalWrapper:162) - LogonUser
2018-06-19 14:02:06,439 WARN [Thread-35] (AFTConfigManagerImpl:140) - Key not found: com.bmc.aft.configurable.disableWinLocalImpersonation
2018-06-19 14:02:06,439 INFO [Thread-35] (WinLocalWrapper:320) - ImpersonateLoggedOnUser

We can see that Sending <FILE_TRANS 0ozz1 00023 1300790> to 127.0.0.1:31647 failed. About this error, please change the port as described below:

Please modify the <agent>/cm/AFT/data/cm_container_conf.xml and change <Port>AVAILBLE_PORT</Port> (31647 is not availble port)

For impersonation add/update the key in aft_configurable.properties file from <agent>/cm/AFT/data/

com.bmc.aft.configurable.disableWinLocalImpersonation=Y

Restart the Control-M Managed File Transfer Container to take the changes effect.

If the above can't be done for now, you can change the profiles with Windows to use FTP passive. FTP Passive is used to solve issues when the server has firewall and can't connect to client in specific port.

When using PASSIVE Port the servers generating port that client is connected where is Active mode the client generare port for server but if the server can't connect that job is stuck.

You can see it in http://slacksite.com/other/ftp.html