Article ID: 116980, created on Aug 28, 2013, last review on May 8, 2014

  • Applies to:
  • Virtuozzo containers for Windows


There is a BSoD on vzsrv service start after installation of PVC updates. Call stack may vary.


If KSAL Database is getting locked by a kernel thread, it might not be replaced upon PVC updates installation, causing problems like non-starting vzsrv service, or BSOD on vzsrv start.

Check version & modification date of KsalDB.dat file in folder:

    C:\Program Files\Parallels\Containers\Extras\

If it is outdated - you should replace it manually.


1) Disable KSAL service:

    C:\>sc config vzksal start= disabled
    [SC] ChangeServiceConfig SUCCESS

2) Reboot the host in order to unlock current KSAL database file.

3) Find the most recent ksalDB.dat file in updates "cache" directory (it will be always in x86 folder on x64 nodes):

    C:\Program Files (x86)\Parallels\PVC updates\Parallels Virtuozzo Containers 4.6 update **VZU4600XX**\Install\VIRTUOZZO_MAIN_DIR_AMD64\Extras\

4) Replace old ksalDB.dat with the one found in step #3, it resides in directory (please note the difference in path, it's not x86 directory):

    C:\Program Files\Parallels\Containers\Extras\

5) Enable KSAL service back:

    C:\>sc config vzksal start= demand
    [SC] ChangeServiceConfig SUCCESS

6) Start VZSRV service:

    C:\>net start vzsrv

Search Words





d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8

Email subscription for changes to this article
Save as PDF