I don't know if this is normal or not, but it takes mRemoteNG 17 seconds to start-up on my one year old computer.
I did the test in 1.7.3-beta and the same in 1.7.4-RC3-portable and exactly the same problem. It just takes 17 seconds to startup.
1. I downloaded free tool Process Monitor from Microsoft web page: https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx
This is very simple program to use, just unzip and run exe file.
2. Then create a filter to monitor only "mRemoteNG.exe" process.
3. Clear monitoring if present.
4. Start capturing.
5. Start mRemoteNG process.
6. Stop capturing when process is started up (GUI visuble).
See attachment it looks like "mRemoteNG" gets into "Process Profiling" for 15 seconds. I don't know what this is, do you have any clue?
Exactly the same happens every time I startup mRemoteNG, 17 seconds needed every start-up.
P.S. This is not a regression bug. This problem is already present in 1.7.3-beta, but pretty much annoying to wait such a log time to start-up.
Windows 7 SP 1 with latest updates
Using mRemoteNG portable