This issue typically occurs if MATLAB is setup to checkout additional tools from a network license or if there is an environment variable (LM_LICENSE_FILE) set for another program. If there is an LM_LICENSE_FILE variable set on the machine, this variable will tell MATLAB and all other FLEXnet applications where to obtain licenses. Typically LM_LICENSE_FILE is set to point to a license server. For either scenario, if MATLAB is setup to check out additional toolboxes from a network license server, and there is no connection, this will delay the time it takes to start MATLAB when disconnected.
If MATLAB is set to a license server for additional toolboxes, the only workaround for the slow startup is to remove the license file that points MATLAB to the license server, or to point MATLAB to the standalone license file only. For more information about this process, see the Related Solution "Why does MATLAB get stuck in the "Initializing" state or take a long time to start?"
If there is an LM_LICENSE_FILE variable set to point to a license server and MATLAB does not use this license server, you can resolve this issue by renaming LM_LICENSE_FILE to the environment variable specific to the product that connects to the license server. Each FLEXnet application looks for LM_LICENSE_FILE as well as a variable that is specific for the vendor of the FLEXnet application. For example, MATLAB uses MLM_LICENSE_FILE. If you rename LM_LICENSE_FILE to the vendor specific variable, MATLAB will ignore the variable and use its own licensing. Refer to the vendor of your other FLEXnet applications to find out the appropriate variable for your other product.
