Article ID: 117008, created on Aug 29, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Windows 4.6


  1. You can see event ID 137 in the hardware node's Event Viewer :

    "The default transaction resource manager on volume \Device\VZLPBKVolumes\VZLPBKVolume{f0de34f5-77fb-4985-b938-0b307d744399} encountered a non-retryable error and could not start."
  2. Hardware node experienced unclean shutdown recently.


The NTFS transaction log got corrupted inside the container.


  1. Determine which container disk has the GUID {f0de34f5-77fb-4985-b938-0b307d744399}, indicated in the event.

    The instructions can be found in #1008

  2. Reset the metadata of the default transaction resource manager inside the container :

    vzctl exec CTID fsutil resource setautoreset true c:\

    (Replace "CTID" with the actual container's ID value hereafter.)

  3. Stop and mount the container :

    vzctl stop CTID && vzctl mount CTID
  4. Delete the corrupted transaction log files :

    del /ah D:\vz\private\CTID\root\Windows\system32\smi\Store\Machine\*.blf
    del /ah D:\vz\private\CTID\root\Windows\system32\smi\Store\Machine\*.regtrans-ms

    (Replace "D:\" with the actual disk letter and path to the directory with private areas of containers.)

  5. Start the container :

    vzctl start CTID

Search Words

encountered a non-retryable error and could not start

was error 6801

event id 137

ntfs transaction log

system process terminated unexpectedly

World Wide Web Publishing service is failing to start

The default transaction resource manager on volume

fsutil resource setautoreset

965b49118115a610e93635d21c5694a8 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 6c20476fe6c3408461ce38cbcab6d03b

Email subscription for changes to this article
Save as PDF