#120 Slow startup time on domain joined machines (when not connected to office network)

[Paolinux]

Hi there,

I've noticed a significant delay (several minutes) in start up time when executing MSYS2 binaries on a domain-joined machine when the latter is not connected to a the office network, e.g., at home. Note that Cygwin or mingw binaries on the same machine execute without any problem. The OS is Windows 8.1.

Disconnecting the network adapter completely solves the issue. Disconnecting the netlogon service (while still be connected to the network) noticeably reduces the startup time (half a minute vs. several minutes) but it does not completely eliminates the problem.

If binaries are invoked from within a another binary (e.g., a shell), then no subsequent delay is observed.

I've tried to dig a bit into this with procmon and I've noticed that msys binaries generate a lot of network activity and establish several TCP connections. Cygwin and mingw, instead, do not seem to generate any network activity.

Similar or related behaviours has been reported elsewhere, e.g.,

http://stackoverflow.com/a/1868223

http://www.hydrus.org.uk/journal/emacs-netlogon.html

but I couldn't find any conclusive solution.

Could you please look into this? I really like msys2 but this issue makes it very hard to use.

Let me know if you need any more information,

Thanks!

[Sundaram Ramaswamy]

Although this may not be a complete fix, there's a possible workaround which worked for some, discussed here: https://github.com/Alexpux/MSYS2-packages/issues/138#issuecomment-70813762

[Paolinux]

Thanks Sundaram! It worked great!

[David Macek]

Closing. New issues can be filed on GitHub.