Article ID: 115364, created on Dec 28, 2012, last review on Jun 17, 2016

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


A container is not pinging and is not accessible over Remote Desktop Protocol (RDP) or any other network services.

The following messages can be found in the container's event logs:

Log Name:      System
Source:        Microsoft-Windows-Kernel-General
Date:          2012-12-10 22:33:21
Event ID:      2
Task Category: None
Level:         Information
User:          SYSTEM
Computer:      CT17133
License policy-cache corruption detected.

Log Name:      System
Source:        Service Control Manager
Date:          2012-12-10 22:34:24
Event ID:      7022
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CT17133
The Group Policy Client service hung on starting.

After these events, more services also get hung in their starting state.

Stopping the container produces the following messages:

Stopping container ...
WARNING: Native API function call 'ZwWaitForSingleObject' failed, code 0x102 Tim
eout waiting for BaseNamedObjects\SC_AutoStartComplete event in session 887
WARNING: Failed to wait for SC_AutostartComplete in CT 887


Since the Group Policy Client was not started, all dependent services were also unable to start.

The exact root cause of this issue varies.


  • Incorrect content of the following registry key on the container may affect the License policy-cache:

    ProductPolicy  REG_BINARY

    Compare the contents of the ProductPolicy registry key with the one from a healthy container. If there is a difference, replace this registry key with the values from another container.

  • If the registry values are correct, or the issue remains after modifying the ProductPolicy key:

    1. Download the PSTools archive, unpack it, open the command prompt, and change your current directory to the PSTools folder.

    2. Using psexec, run the registry editor under the system account:

        C:\PSTools> psexec -s -i TERMSESSIONID regedit

      NOTE: TERMSESSIONID is the ID of the current terminal session, which can be obtained in the following way:

        C:\>qwinsta | findstr Active
      >rdp           Administrator            4  Active
    3. In the Registry Editor, navigate to HKLM\vzCTID\MACHINE\SYSTEM\Currentcontrolset\Services\gpsvc and change the "Start" value from 2 to 4.

    4. Start the container, then stop and mount it again:

      C:\> vzctl start CTID && vzctl stop CTID && vzctl mount CTID
    5. Revert the "Start" value of HKLM\vzNEWID\MACHINE\SYSTEM\Currentcontrolset\Services\gpsvc from 4 to 2.

    6. Start the container.

    The network should now be functional again in the container.

  • If the procedure does not help, try to restore the whole HKLM\SYSTEM\Currentcontrolset hive from a container backup.

Search Words

Native API function call 'ZwWaitForSingleObject' failed, code 0x102

vzctl start ERROR: QueryRegValue

Cannot RDP into container



no access to container

The Group Policy Client service hung on starting

no network

Container not running

Server offline

services are not getting started and could not RDP it

Response timeout for operation 'exec'

Failed to wait for SC_AutostartComplete

cannot start up


License policy-cache corruption detected

remote desktop

2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 6c20476fe6c3408461ce38cbcab6d03b 6f8e3eda12803cf88a9587e9782c9ed6

Email subscription for changes to this article
Save as PDF