- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can confirm, this is still not working correctly with Windows 10 1903 and all the latest updates for Esxi 6.7 with VMFS 6, completely unusable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same problem here:
VMware ESXi, 6.7.0, 13644319
VMFS 6
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 ![]()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We created a datastore VMFS5 and it soon solved the problem. Any prediction of vSphere 6.7 U3?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Issue to be fixed in a future ESXi release for 6.5 and 6.7 . ETA might be (Q3 2019) .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So 6.5u3 dropped, however i still don't see this fixed in the resolved section, anyone else?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this an issue in 6.7?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Experiencing this in ESXi 6.5 U2 with VMFS6. We are looking to determine whether or not this will be resolved in ESXi 6.7, either U2 or the upcoming U3.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
New vcenter update doesn't fix it. Booting time is up to 5-6 minutes on VMFS5.
Still waiting for the fix..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Anyone know when ESXi 6.7 Update 3 is going to be released which rumor has fixes this problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nathan,
I am experiencing the same issue but using Insta clone, will this resolution work with Insta Clone as well?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm not sure, we unfortunately do not have licensing to use instant clones.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm not to 1809 yet in our Horizon Deployment, but from my understanding of the issue, it wouldn't matter if its in instant clone or not.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
what version of w10 are you running? non-persistent linked clones?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ESXi 6.7 Update 3 was just released. Has anyone tested this yet to see if the the slowness is gone with VMFS6 datastores?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
at the bottom of page 6, summacollege reported that 6.5u3 did fix this issue, no reports of anyone with 6.7u3 reporting from what i can tell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We're getting the updated scheduled (probably a week or two out), and I will report back on findings once that's done.