Hi,
It looks like most of the delay happens before gdb sends a reply to the first command. This could be caused by the antivirus interfering with its load, or by extremely slow disk performance. Please try starting the gdb executable manually and observe whether it also takes 16 seconds before it produces any output. If yes, please try disabling any 3rd-party software that could be interfering with this, or try experimenting to see if any other tools (e.g. gcc) get affected.