Article ID: 119081, created on Dec 9, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo containers for Windows 6.0
  • Virtuozzo containers for Windows 4.6
  • Virtual Automation


  1. A container is running, but cannot be entered with vzctl:

     >vzctl enter 57571 
     ERROR: Response timeout for operation 'exec' 
     Environment is not changed. 
     Command 'enter' is successfully finished 
  2. On stopping the container, the following error is received:

    vzctl stop 57571
    WARNING: Native API function call 'ZwWaitForSingleObject' failed, code 0x102 
    Timeout waiting for BaseNamedObjects\SC_AutoStartComplete event in session 57571
    WARNING: Failed to wait for SC_AutostartComplete in CT 57571 
  3. It is not possible to connect to the container over RDP.

  4. Container spends long time in starting\stopping cycle and following error can be found in the vzlog:

    T=2015.01.11 23:24:24.149; A=VzSrv; P=2316.1424; S=VZSRV; F=build\4.6.490.0\sources\virtuozzo\vzwin\vzmain\vzsrv\klpc.c,KlpcProcessMessage,106; L=INFO; R=0(0); C=0(0); M=135 []  Container 123 requested REBOOT action


Some services are hanging inside the container, leading to the malfunctioning of other services by dependencies.


Copy the System.evtx log from %vzroot%\root\%ctid%\c\windows\system32\winevt\Logs, open it on the host and try to locate the problematic service.

If there is a clearly identifiable non-starting service, it can be disabled:

  1. Stop the container

  2. Mount the container:

    vzctl mount CTID
  3. Open the registry editor on the host (regedit.exe), and disable the faulty service inside the container:


    Set "start" -> 4

  4. Start the container.

If there is no clear evidence as to which service cannot start properly, contact Parallels Technical Support for assistance.

Additional information

Other causes of a failing vzctl enter may include:

117863 RDP Attacks
113519 No privileges to execute cmd.exe inside the container

Related articles

115821 PVA Agent service is stuck in "START_PENDING" state

112775 Cannot connect to a container using RDP

Search Words

stuck in starting

Timeout waiting for BaseNamedObjects\SC_AutoStartComplete event in session

requested REBOOT action


vzctl starting

Windows has encountered a critical problem and will restart automatically in one minute


code 0x102

container locked

Container not running

Connection to vzagent was closed

Environment is not changed

Response timeout for operation 'exec'


Failed to wait for SC_AutostartComplete

System Services

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8 319940068c5fa20655215d590b7be29b 6f8e3eda12803cf88a9587e9782c9ed6 6c20476fe6c3408461ce38cbcab6d03b 0dd5b9380c7d4884d77587f3eb0fa8ef c62e8726973f80975db0531f1ed5c6a2

Email subscription for changes to this article
Save as PDF