In going through the code for the new 2010 DirectRT v2010.2.103.1115, I've noticed a potential cause for a delay *if* IP licensing is being used. It's going to to the internet to compare and validate the IP rather than simply getting the value from Windows. It was a security measure but I expect it could add a variable delay to the startup of a DirectRT session because the IP check is run any time a session is run. Are the delays mentioned in the posts above tending to be happening on machines with IP licenses? If so, why don't we try a manual (i.e., m10... ) license on one of them and see if that resolves it. If so, then we'll fix the IP coding so that it will not slow down the start of any given session.