Here are details of my setup – in fact, I started over from scratch to document my steps.
This seems to be a new problem occurring with Windows 10, version 1709
Install of new VMware guest for the purpose of being a template
- Create new VM, named it windows_10_enterprise_version_1703
- Remove floppy drive
- Uncheck networking (for install)
- Mount ISO and enable, click OK to save settings
Install of OS on the guest virtual machine
- Boot newly created VM (windows_10_enterprise_version_1703)
- Step through the installation until completion
- Complete language settings to arrive at Windows desktop
- Enable the ‘Administrator’ account as its disabled by default
- Log out of installation user (the account I named ‘install’)
- Log into the ‘Administrator’ account
- Enter control panel, user and delete the ‘install’ user account.
- Install VMWare tools, Reboot once
- Shutdown
Prepare VM to be a template
- Edit the VM settings
- Connect networking
- Disconnect CD Drive
- Click OK
- Convert VM to a Template
Customization Specification Setup
- Create new specification, (I named mine Windows Desktop – DHCP)
- Applied registration information
- Computer Name – Use the virtual machine name
- Windows License – Left this blank (unchecked include server licensing information)
- Administrator Password – Set password, choose the option to automatically login as Administrator
- Time Zone – Set my desired time zone
- Run Once – Left this blank (blank for now, later intend on applying KMS details)
- Network – Use standard network setting (DHCP)
- Workgroup or Domain – For now just Workgroup and left workgroup name as ‘WORKGROUP’
- Operating System Options – Generate New Security ID (SID)
- Ready to complete – Clicked OK
Deploying template
- Right-click on the template – New VM from the template
- Gave a simple name – TEST01
- Selected Datacenter, Selected Cluster
- Selected Storage
- Selected Options (Customize VM) and (Power on the virtual machine after creation)
- Selected ‘Windows Desktop – DHCP’ from customized guest OS options
- Clicked Next, then Finish and wait …
Where things get stuck
- After the first boot, the guest gets an IP address from the network
- Customization starts in the background and system reboots
- When the system resumes I arrive at the following screen
- The system customization never completes, and I find my VM’s stuck at the “Let’s start with region …” screen
And, I’ll update this as soon as I find a solution, but for now… I’m stuck
Log Shared via Pastebin: https://pastebin.com/ETpuLX3U
Update: March 18, 2018
I’ve had others also test this using the latest ISO for Windows 10 – en_windows_10_enterprise_version_1703_updated_march_2017_x86_dvd, they too now encounter this same issue. So the problem seems to be with the build of Windows 10 that was released.
I am going to download another build from MSDN and see if there is a change.
Update: March 19, 2018
I was able to get this working by way of reinstalling Windows 10 using the following ISO build: en_windows_10_multi-edition_vl_version_1709_updated_sept_2017_x64_dvd
Was even able to apply Windows updates and redeploy without error.
[youtube id=”Qp1d_RzomyM” width=”600″ height=”350″]