Article ID: 126514, created on Aug 10, 2015, last review on Aug 10, 2015

  • Applies to:
  • Virtuozzo containers for Windows 4.6


On a newly deployed Windows Server 2008 (non-R2) node all new containers cannot start:

    C:\> vzctl start 101
    Starting container ...
    ctid=101 LogonUI timeout (300 secs)
    Container 101 is not started


Wrong permissions on OS template registry hive prevent containers to start. The issue is recognized as a product bug with internal ID PCWIN-22504.


The permanent fix is planned to be included in one of the next product updates. In order to fix current installation, the following workaround should be performed:

  1. Mount one of the containers.

    C:\> vzctl mount 101
    Container is mounted
  2. Open registry editor regedit and modify permissions for the HKEY_LOCAL_MACHINE\vz0_windows_2008_ent_sp1-6.0.6001-20090319\MACHINE\COMPONENTS hive. Set the same permissions as for HKEY_LOCAL_MACHINE\COMPONENTS hive (there should be 4 users, if there are only two — add the rest).

  3. If the containers created previously need to be started, mount them and change permissions for HKEY_LOCAL_MACHINE\vzCTID\MACHINE\COMPONENTS in the same way.

Search Words

LogonUI timeout

LogonUI timeout (300 secs)

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 6c20476fe6c3408461ce38cbcab6d03b 965b49118115a610e93635d21c5694a8

Email subscription for changes to this article
Save as PDF