Article ID: 6948, created on Nov 27, 2009, last review on May 8, 2014

  • Applies to:
  • Virtuozzo containers for Windows 4.5
  • Virtuozzo containers for Windows 4.0


1. A Windows 2003 x64 server has Parallels Containers 4.0/4.5 installed, without .NET on the host.
2. .NET 1.1 or a later version is installed inside a container (either directly or with the template).
3. User is logged in to the container using a regular account (not the Administrator account).

.NET applications do not work. To ensure this is the case, run the command below from inside the container (while logged in as a regular user, not as the Administrator):



During installation, .NET adds the following registry value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel
ObUnsecureGlobalNames (REG_MULTY_SZ):


The above values are for .NET 1.1; NET 2.x adds one more:

The values are applied at a very early stage of the OS boot, so they are not applied in containers if the values are configured in the containers registry only.


On the Hardware Node, either install .NET or create registry keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel

ObUnsecureGlobalNames (REG_MULTY_SZ):

Obcaseinsensitive (REG_DWORD):

 ... and reboot the Node.

28d0f7cc091e3b9304fa556c03f9a940 d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 d09cb2230ee0cfa720ed0f2a3cc39452 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF