Skip to main content

KC Plug In does not start - did not start in 120 seconds -

Article # 3035480 - Page views: 326

Article # 3035480 - Page views: 326


The KC Plug-in Service does not start. The event logs and the KC Plug-In logs don't show any errors. other than to indicate that the service did not start in 120 seconds.



One of the possible causes is that KIC Plugin is trying to resolve and UNC path and while attempting to start the service it goes in timeout.


1) Test or try to disable the UNC path that needs name resolutions. 

2) Extend the Service timeout:

  • Regedit
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\
  • Add DWORD: ServicesPipeTimeout
  • Set to 300000 (5 minutes)
  • Reboot the system


Level of Complexity 


Applies to  

Product Version Build Environment Hardware
KIC 2.8,  2.9      


Add any references to other internal or external articles


Conditional content (Pro member)
  • Was this article helpful?