Article ID: 120552, created on Mar 14, 2014, last review on Jun 17, 2016

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


  1. Container backup creation fails with Failed to initialize snapshot error message.
  2. The following messages can be seen in the C:\vzlog\YYYY.MM.DD-vzlog:

    A=VzSrv; P=3148.61424; S=VZSRV; F=build\4.6.490.0\sources\virtuozzo\vzwin\vzmain\vzsrv\lock.c,do_lock_vps_registry,622; L=ERROR; R=58(88); C=0(0); M=88 [VzkrnlLockNFlushRegistry;2] Native API function call 'VzkrnlLockNFlushRegistry' failed, code 0x2 CTID
    A=fsresizer; P=28236.17840; S=VZSRV; F=snapshot.cpp,SWVolumeSnapshot::Init,393; L=ERROR; R=ffff(65535); C=0(0); M=65535 [] Snapshot::Init failed with 1359.


Some part of the container's registry is corrupted: some registry key exists, but its content cannot be opened.


The registry is vital system data in the container and on its corruption it is better to restore the container from the last backup.

To save the currently available data in the container, the backup can be restored to a new container and the registry copied to the existing one.

Note: PVA Agent should be 4.6.3-1734 or later if you deside to restore a backup to a separate container. Details are provided in this article.

To gather more information about such cases, the broken container can be passed to Parallels Technical support for identifying the corruption.

Search Words

Native API function call 'VzkrnlLockNFlushRegistry' failed

Can't create Volume Snapshot for C:'


Failed to initialize snapshot

Snapshot::Init failed with 1359

failed to initialize snapshot

Snapshot->Init() failed

Native API function call 'VzkrnlLockNFlushRegistry' failed, code 0x2


6c20476fe6c3408461ce38cbcab6d03b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8 e8e50b42231236b82df27684e7ec0beb 36627b12981f68a16405a79233409a5e

Email subscription for changes to this article
Save as PDF