About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When you clone a Windows VM or deploy it from a template with a customization specification, two programs run inside the new guest in turn. First VMware's customization tool applies the specification and prepares Sysprep. Then Windows Sysprep runs its specialize and out-of-box (OOBE) passes, which set the name, the network, the domain membership and a new security identifier (SID). If the VM comes up with the template's name, no address, or not joined to the domain, each stage leaves a log inside the guest. Read VMware's logs to see whether its part finished, then the Sysprep logs to see what Windows did next.
What the error means
TechDocs: "When the new virtual machine starts for the first time, the guest operating system runs finalization scripts to complete the customization process. The virtual machine might restart several times during this process." Errors are not shown in vCenter in detail: "If the new virtual machine encounters customization errors while it is starting, the errors are logged to %WINDIR%\temp\vmware-imc."
KB 397424 shows the hand-over in guestcust.log. After VMware's steps, it logs Creating sysprep copy in dir:'C:\sysprep1008' and schedules guestcustutil.exe post-run HandleCustomizationCompleted. The KB calls this the point "which means guest customization is done and we're handing off the process to sysprep". A fault after that line is a Windows Sysprep fault, not a VMware one.
Some failures never reach either log. The requirements page lists three that stop customization early: "The latest version of VMware Tools must be installed on the virtual machine or template", "The guest operating system being customized must be installed on a disk attached as SCSI node 0:0", and support for the guest in the Broadcom Compatibility Guide.
Likely causes
| Cause | What you see | Source |
|---|---|---|
| Old VMware Tools on older Windows (Windows Server 2012 R2 and earlier; Windows 8.1, 7 and Vista) | toolsDeployPkg.log: "Command Completed with exit code -107374151" | KB 311937 |
| Setup paused waiting for input | VM sits at a Windows prompt; "incorrect product key or an invalid user name" | TechDocs |
| Network set before Windows found the NIC | guestcust.log: netsh interface ip set address, "Element not found." |
KB 431655 (Cloud Director 10.6) |
| Sysprep specialize or OOBE error | setuperr.log and setupact.log entries in Panther | KB 344729, Microsoft |
| Domain membership not applied | The VM is not in the domain after customization | netsetup.log, which holds "information about workgroup and domain membership" (KB 342899) |
| Template not on SCSI 0:0, or Tools missing | Customization does not start | TechDocs requirements |
| Harmless line mistaken for the fault | "OpenService FAILED 1060" | KB 397424 |
The last row matters. KB 397424: "This is a normal error in guestcust." "The absence of the "VMware Guest OS Customization Task" service (error 1060) is expected and does not impact customization success." Do not stop reading at it.
Prove the cause before changing anything
These steps only read. Open the new VM's console, or log in with a local administrator account if the VM is reachable.
1. Look at the console first. "If the guest operating system pauses when the new virtual machine starts, it might be waiting for you to correct errors, such as an incorrect product key or an invalid user name. To determine whether the system is waiting for information, open the virtual machine console." A Windows Setup prompt on screen answers the question without any log.
2. Read VMware's customization logs in %WINDIR%\temp\vmware-imc (C:\Windows\Temp\vmware-imc\):
guestcust.log: each step VMware ran, with its command and exit code. Find the firstWARNorfailedline other than the 1060 line, and check whether the sysprep copy andpost-runlines appear.toolsDeployPkg.log: whether the package was unpacked and run. KB 342899 calls the same filetoolsDeployPkg.txtand uses it to check "If there were any problems with the extraction and deployment of the customization package onto the guest operating system".- KB 342899 adds
C:\WINDOWS\TEMP\customize-guest.log: "This file has details of the customization properties, so if a particular virtual machine does not pick up a field correctly, you can verify what was passed to the virtual machine from this file."
3. Check the VMware Tools version. KB 342899 reads it from the VM's vmware.log with grep toolsVersion vmware.log. For KB 311937's exit code, the fix starts at "10.3.0 or later".
4. Read the Sysprep logs. KB 344729 names the two files to start with, setupact.log and setuperr.log, and three folders for Windows Vista through Windows Server 2025: C:\Windows\Panther, C:\Windows\Panther\UnattendGC and C:\Windows\System32\sysprep\Panther. Microsoft's Sysprep page maps them to passes:
| Pass | Log path |
|---|---|
| Generalize | %WINDIR%\System32\Sysprep\Panther |
| Specialize | %WINDIR%\Panther |
| Unattended Windows Setup actions (OOBE) | %WINDIR%\Panther\Unattendgc |
Microsoft's order: "review the entries in the Setuperr.log file first, then the Setupact.log file second, and then other log files as needed." KB 342899: setuperr.log "should be 0 bytes in size if no errors occurred during installation." Microsoft describes Setuperr.log as a "High-level list of errors that occurred during the specialize phase of Setup. The Setuperr.log file does not provide any specific details.", so open setupact.log for the detail behind each entry. Microsoft's Deployment Troubleshooting page puts driver failures in %windir%\inf: Setupapi.offline.log for "Driver failures during the Component Specialization sub-phase of the Setup specialize phase" and Setupapi.dev.log for "Driver failures during the oobe phase of Setup."
5. For domain join faults, read netsetup.log. KB 342899 lists it as containing "information about workgroup and domain membership". KB 342899 gives no folder: "Search for these files in the Windows file system." KB 344729 lists C:\Windows\Debug\netsetup.log, but only under Windows XP and 2003. On current Windows, search the guest for netsetup.log, starting in C:\Windows\debug and C:\Windows\Panther.
6. For network faults, compare adapters. KB 342899: netsh interface ip show config displays "all of the adapters in the computer with their current IP addresses". Compare the adapter names with the netsh command in guestcust.log.
Example (illustrative): a Windows Server 2025 VM cloned with one vCPU boots with the right name but a DHCP address. guestcust.log shows netsh interface ip set address failing with "Element not found.", and no later WARN lines. The Sysprep logs are clean. This matches KB 431655's race between customization and the network driver.
Fix
Fix the source template or the specification, then deploy a fresh VM to test it, so the result is not mixed with the failed attempt.
Old VMware Tools (exit code -107374151). KB 311937 offers three ways: "Upgrade the VMware tools version to 10.3.0 or later.", install Microsoft update KB2999226, or install the "Visual C++ Redistributable for Visual Studio 2015". Update Tools in the template, then convert it back. Disruptive step: a Tools upgrade in the template may need a guest restart.
Setup waiting for input. Correct the product key, user name or other field in the specification. TechDocs adds: "After you deploy certain Windows operating systems that are not volume licensed, you might need to reactivate your operating system on the new virtual machine."
Network not ready (one vCPU). KB 431655 resolution: "Configure the virtual machine with 2 or more vCPUs." Its cause: "When only 1 vCPU is assigned, the VMware Tools customization process may trigger before the Windows OS has finished identifying the NIC hardware and loading the necessary network drivers." The KB tests only VMware Cloud Director 10.6 and does not mention vCenter. The same Element not found. line on a one-vCPU VM in vCenter is likely the same race, and adding a second vCPU is a low-risk test.
Sysprep errors. Follow the first entry in setuperr.log. KB 397424: "Ensure that all sysprep and imaging tools used are compatible with the target Windows version", "confirm that no third-party software interferes with OOBE processes", and "Engage Microsoft support to assist in troubleshooting sysprep issues."
Domain join. KB 342899 names netsetup.log as the file to read and gives no fix steps for a failed join. As general advice, check that the new VM can resolve and reach a domain controller through DNS, and that the account in the specification is allowed to join computers to the domain.
Requirements not met. Move the system disk to SCSI 0:0, install current VMware Tools, and check the guest in the Compatibility Guide before the next clone. Disruptive step: changing the template's disk controller needs the template powered off.
Duplicate SIDs. TechDocs: "Windows 11 (versions 24H2 and 25H2) and Windows Server 2025 enforce SID uniqueness checks, and duplicate SIDs on these systems can result in inaccessible shared network folders, failed Remote Desktop Protocol (RDP) connections, and Failover Clustering errors." "always use Sysprep when cloning or duplicating a Windows installation". A VM that skipped customization should be replaced by a properly customized clone. Risk: do not put a VM with a duplicate SID into production or a cluster.
Confirm the fix
- The new VM boots to the logon screen without a Setup prompt.
guestcust.logshows thepost-runhand-over and no unexplainedWARNlines.setuperr.logis empty or holds no new entries.- The computer name, IP settings and domain membership match the specification.
What to watch afterwards
- Template VMware Tools version, kept current.
- vCPU count of small Windows Server 2025 templates.
- Specification changes to keys, accounts and network settings; test each change on one clone first.
- Sysprep compatibility of any imaging or security software in the template.
Read next
Related articles you may want next.
- TroubleshootingLinux VM Customisation Sets the IP but Skips Your ScriptDiagnose skipped Linux guest customisation scripts in vSphere 8: check the VMware Tools script gate, pre/post phase and documented timeout.Read article
- VMwareHow to build and validate Windows Server templates for VMwareCreate a repeatable image with deliberate identity preparation and two-clone acceptance testing.Read article
- VMwareVMware Tools Not Running or Out of Date: What It BreaksRead VMware Tools running and version status correctly, see which guest operations depend on it, and pick the maintenance route for Tools or open-vm-tools.Read article
Risks and limits
- KB 342899 and KB 431655 are written for Cloud Director. KB 342899 says "Customization in VMware Cloud Director is done in the same way as in vCenter Server", and its log list applies to vCenter guests. KB 431655 tests only Cloud Director 10.6.
- Sysprep's own failures are a Windows matter; Microsoft's documentation and support cover them.
- Windows versions may add or move log files.
NetLeverage runs its own hosting on VMware vSphere, vCenter and ESXi. Talk to an engineer.
Sources
- Customize Windows During Cloning or Deployment — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- Guest Operating System Customization Requirements — Broadcom TechDocs, Last Updated October 28, 2026, accessed 17 November 2026
- Locations of sysprep log files (KB 344729) — Broadcom, Updated On 07-23-2025, accessed 17 November 2026
- Guest OS Customization failing with the following error "[SC] EnumQueryServicesStatus:OpenService FAILED 1060:" (KB 397424) — Broadcom, Updated On 05-14-2025, accessed 17 November 2026
- Guest OS Customization fails on some Windows installed VMTools version before 10.3.0 (KB 311937) — Broadcom, Updated On 06-03-2026, accessed 17 November 2026
- Troubleshooting guest operating system customization issues using VMware Cloud Director (KB 342899) — Broadcom, Updated On 09-03-2026, accessed 17 November 2026
- Guest OS customization fails when deploying Windows Server 2025 with 1 vCPU (KB 431655) — Broadcom, Updated On 03-03-2026, accessed 17 November 2026
- Sysprep Process Overview — Microsoft Learn, page metadata date 2021-10-08, accessed 17 November 2026
- Deployment Troubleshooting and Log Files — Microsoft Learn, page metadata date 2021-05-02, accessed 17 November 2026
This article was originally published on .