Unable to log in to a Windows virtual machine after it has been converted with VMware Converter
search cancel

Unable to log in to a Windows virtual machine after it has been converted with VMware Converter

book

Article ID: 337620

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

This article identifies why you are unable to log into a Windows operating system after it has been converted with VMware Converter.
If you use a VMware Converter to convert a physical or virtual machine, you may experience these symptoms:
  • During the boot process, the virtual machine does not log in to the desktop.
  • The dialog box Loading your personal settings displays, followed by Save your settings. However, the desktop does not appear, and the Welcome to Windows logon screen displays again.
  • You see this error:
[Limited Virtual Memory]
Your system has no paging file, or the paging file is too small.

Environment

  • VMware vCenter Converter 4.0.x
  • VMware vCenter Converter 4.1.x
  • VMware vCenter Converter 4.2.x
  • VMware vCenter Converter Standalone 4.0.x
  • VMware vCenter Converter Standalone 4.3.x
  • VMware Converter 3.0.x
  • VMware vCenter Converter Standalone 5.0.x

Cause

Microsoft has identified this as an issue with certain Windows operating systems. This issue does not specifically pertain to VMware Converter, and it can be seen in other types of cloning software.
 
Windows operating systems contain entries in the registry and certain configuration files that identify where the operating system was originally installed. Drive letters in Windows operating systems are based on Globally Unique Identifiers (GUID) for each volume. If the volume GUID of the boot drive is modified, it can prevent Windows from logging in to the desktop.
 
When a drive is resized during a conversion with VMware Converter, the resulting volume may have a different GUID. Windows tracks drive letter assignments by the GUID, and if this has changed it re-enumerates the drive letters. This can cause the system volume to become C:\, even if it was previously a different letter.
 
This can occur when the source system is converted with VMware Converter and when the Windows operating system is installed on another drive besides the default of C:\ (such as D:\). This issue also frequently occurs when the source server hosts Citrix Presentation Server software. This is not an issue with Citrix, but is due to the way the Windows operating system is installed in that environment.

Resolution

You need another Windows operating system to connect to the converted machine and modify the registry.