I downloaded the Windows 10 1809 and Server 2019 ISOs the day they became available so I can start working on my templates.
I built the templates with EFI, paravirtual for the C drive and vmxnet3 adapter. I've been using this combo for other versions of windows 10/8/7and windows server 2008r2/2012r2/1016 without issue.
So far Windows 2019 (with desktop experience) seems to be ok at least for a basic vm and guest customization. Haven't tried anything else yet.
Windows 10 1809 on the other hand is very, very slow to reboot after the initial install or even just rebooting after making some changes post install. After installing the OS it took 10-15 minutes for the initial windows setup stuff (user, security settings, etc) to appear . I tried a VM set to BIOS and it seemed faster but was still quite slow. Server 2019 and other versions of windows 10 have no issue.
The hosts are esxi 6.5 and 6.7.
I haven't had a chance to try every combo of BIOS/EFI/vmxnet3/e1000e/paravirtual/lsi sas to see if one is the cause of the issue but was wondering if anyone else had noticed any issues or if it was just me?
Same problem here:
VMware ESXi, 6.7.0, 13644319
Storage connected via fiberchannel
Windows 1803: normal boot
Windows 1809 with snapshots: slow boot
Linked Clones (and golden image) with Windows 1809: slow boot
It is a very annoying situation that VMware let's its customers down in this case 😞
Not sure what is different on mine but I created a VMFS 5 data store and composed a new set of VMs on this data store but have not noticed any significant difference in boot times (Win 10 1803). Still seems to hang for upwards of 20 minutes just spinning at the Windows splash screen.
Thanks for this info - exact same issue we're experiencing. Doesn't matter if it's Win 10 1803, 1809, or 1903 - VMFS5 of VMFS6, using Pure Storage or vSAN. I also completely left out Horizon and just composed a Win10 VM in vSphere from a template, and THAT helped. It seems if you create all dedicated Win10 VM's from a template (which won't have associate snaps) the issue is fixed, but that's only a workaround (if you have the host resources).
I see this in the release notes which seems like the issue in question:
PR 2292798: Virtual machines with Microsoft Windows 10 version 1809 might start slowly or stop responding during the start phase if they are running on a VMFS6 datastore
If a virtual machine is with Windows 10 version 1809, has snapshots, and runs on a VMFS6 datastore, the virtual machine might either start slowly or stop responding during the start phase.
This issue is resolved in this release.
We installed 6.5 U3 (Build 13932383) today and all VDI desktops feel snappier. Overall feeling with me and my colleagues is that this update also improved performance for us.
Our floating desktops are stored on local VMFS 6 SSD storage.
We were not affected by the slow boot issue so i can't say if this update indeed fixed that.
Edit: we did some measurements and logintimes on average dropped from about 30sec to 20sec!