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~~220.127.116.11","Package_for_KB2764462~31bf3856ad364e35~amd64~~18.104.22.168"" 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~~22.214.171.124","Package_for_KB2765809~31bf3856ad364e35~amd64~~126.96.36.199"" in log "C:\vz\Private\101\updates\KB2765809.info.txt" WARNING: LoadUpdateUninstallInfo(101, KB2765809) failed, error = 0x57 ...
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.
Case 1: Install all pending Windows updates on the destination node.
Case 2: Contact Virtuozzo Technical Support to investigate the case in depth.