Article ID: 1668, created on Jan 31, 2007, last review on Aug 4, 2015

  • Applies to:
  • Virtuozzo containers for Windows


After upgrading to Virtuozzo 3.5.1 SP1, I’m unable to start certain VE(s) and get the following error:

Virtuozzo API function call 'VzkrnlStartVps' failed dwErr=0x0000013D

I see the following in Event Viewer:

The description for Event ID (1) in Source (vzcore) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ; VE=1006 Driver=Tcpip DriverEntry failed C0000034


The system is starting drivers in the wrong order.


Correct the driver order so that IPSEC is loaded before TCP/IP.

1. Mount issued VE with:

vzctl mount VEID

2. Run "regedit":

3. Go to HKEY_LOCAL_MACHINE\vz{ve_id}\MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip and check the "Tag" value, e.g., "5." It is necessary to remember it. 

4. Go to HKEY_LOCAL_MACHINE\vz{ve_id}\MACHINE\SYSTEM\CurrentControlSet\Services\IpSec and check the "Tag" value, e.g., "3." It is necessary to remember it. 

5. Go to HKEY_LOCAL_MACHINE\vz{ve_id}\MACHINE\SYSTEM\CurrentControlSet\Control\GroupOrderList and open the bin:PNP_TDI value. It is shown below:
07 00 00 00 05 00 00 00
04 00 00 00 01 00 00 00
02 00 00 00 03 00 00 00
06 00 00 00 07 00 00 00

You will probably see that the "TCPIP" tag is the previous "IpSec" tag, but it should be vice versa. Thus, it is necessary to change 05 to 03 and 03 to 05 in the bin:PNP_TDI value.

5. Restart VE.

965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF