Article ID: 124459, created on Feb 14, 2015, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Windows 6.0

Symptoms

Container was migrated/restored to a PCW6.0 node with a different update level than on the original node.

Start of the container fails with error:

C:\Users\Administrator>vzctl start 101
Starting container ...
Container 101 raised hard error with a status C0000135
Shutdown initiated while waiting for Winlogon in container 101
Container 101 system process terminated unexpectedly

With verbose output, there are plenty of messages related to missing updates:

C:\Users\Administrator>vzctl start 101
...
NOTICE:  Cannot find update KB2764462 on the HN, removing it from Container 101
WARNING: Incorrect line "DP:"Package_for_KB2764462~31bf3856ad364e35~amd64~~6.2.1.0","Package_for_KB2764462~31bf3856ad364e35~amd64~~6.2.1.0"" in log "C:\vz\Private\101\updates\KB2764462.info.txt"
WARNING: LoadUpdateUninstallInfo(101, KB2764462) failed, error = 0x57
NOTICE:  Cannot find update KB2765809 on the HN, removing it from Container 101
WARNING: Incorrect line "DP:"Package_for_KB2765809~31bf3856ad364e35~amd64~~6.2.1.0","Package_for_KB2765809~31bf3856ad364e35~amd64~~6.2.1.0"" in log "C:\vz\Private\101\updates\KB2765809.info.txt"
WARNING: LoadUpdateUninstallInfo(101, KB2765809) failed, error = 0x57
...

Cause

General behavior on PCW6.0: all updates available on the hardware node are installed into all containers, and there is no uninstallation procedure. When a container gets migrated/restored to another server, it gets the file set of the most recent updates installed on that host. The presence of obsolete updates may result in broken links inside the container, belonging to these particular MS KBs, but to no effect on the overall functionality, as there will be more recent versions used by the system.

Case 1: DST host is not patched with all available Windows updates, SRC host had more recent updates installed. In this case broken links will appear for the missing updates and cause the container start-up failure.

Case 2: DST host is patched with all available Windows updates. The root cause of broken links should be investigated in each particular case.

Resolution

Case 1: Install all pending Windows updates on the destination node.

Case 2: Contact Virtuozzo Technical Support to investigate the case in depth.

Search Words

PVCfW6.0

Broken links

Broken container after restore on another hardware node

vzcore

Container does not start

black screen after starting a container

system process terminated unexpectedly

restored container

raised hard error with a status C0000139

container will not start after windows update

raised hard error with a status C00001

container won't start

6f8e3eda12803cf88a9587e9782c9ed6 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 965b49118115a610e93635d21c5694a8

Email subscription for changes to this article
Save as PDF