1 5 6 7 8 9 Previous Next 126 Replies Latest reply on Oct 10, 2020 10:44 AM by bobyuen Go to original post Branched to a new discussion.
      • 120. Re: windows 10 1809 slow
        mav2201 Lurker

        Just wanted to say here that after a long night of troubleshooting, our issues were solved by putting all the disks for our composer clones on a SATA controller instead of the LSi one.

         

        Machines went from freezing on boot to 20 second startups on Win 10 1910.

         

        Tested on ESXi 7.0 and 6.7U3, using Horizon 7.11 and vCenter 7.0

         

        Thanks

        • 121. Re: windows 10 1809 slow
          Preetam Zare Expert

          I'm correct to say,  you change the controller on master image to SATA?

          With Great Regards,
          TechS
          vExpert 2012-2017 | VCP3-5 | VCAP5-DCD | VCP-NV | vSAN Specialist | VDI | Germany
          • 122. Re: windows 10 1809 slow
            HPU-ADM Enthusiast

            The test vm (SATA or LSI controller) is on a vmfs 6 store AND has a snapshot?

            • 123. Re: windows 10 1809 slow
              mevaibhav Lurker

              So did the Patch from VMWare Engineering solve this issue ?

              • 124. Re: windows 10 1809 slow
                abugeja Enthusiast

                Is there a fix for this or to just move away from 1809 to a later build version?

                 

                Our issue isnt that its slow in performance but Windows 10 just uses so much more CPU than Windows 7 even at idle. Do 1909 or above address this?

                • 125. Re: windows 10 1809 slow
                  castroanth Novice

                  I tried the same thing on one of my linked clone VDIs:

                   

                  -Win10 1909 VM

                  -ESXi 6.5

                  -Horizon 7.9

                  -VMFS 5 Datastore (It was on VMFS 6 previously, I changed to a VMFS 5 on another suggestion from someone, it may have helped slightly but still was taking far too long for a simple reboot)

                   

                  Changed the virtual disk to bind to a SATA controller instead of the default LSI SAS controller. Took my boot time from 15 min+ to 15 seconds. I'll be changing the master image to the same config and test with an entire pool.

                   

                  UPDATE:

                  After changing the controller on the master image to a SATA controller, my VMs got stuck in the customizing state indefinitely. After a frustrating all nighter, several hours on the phone with VMware (who blamed my version of Win10 and Horizon), and totally rebuilding my image, I figured out, in my case at least, I HAD to have a SCSI controller added to the parent image, even if my disk was attached to the SATA controller.

                  • 126. Re: windows 10 1809 slow
                    bobyuen Enthusiast

                    We've only recently started using Windows 10 with Horizon and noticed the slow boot. It was only yesterday I figured out that my performance boot time was related to the number of snapshot I had with my Windows 1909 and 2004 image.

                     

                    It was only this morning that I Googled and found this discussion only to find out that his boot issue has been going on for quite some time since this post was done on Oct 18, 2018. It's only 8 days away from being 2 years and no resolution

                     

                    Anyways I thought I chime in and say that I've been having problems too with 1909 and 2004. I read through and found the KB articles that VMware recommends using the older 1809 image.

                     

                    In my tests when using 2004 build. It took about 7 Sec to boot with no Snapshot. Additional snapshots would add about 20-30 sec to the total boot time.

                     

                    My environment :
                    6.7.0.13006603

                    Horizon 7.12 build 15770369

                    Storage, Netapp FAS8200,  VMFS6

                     

                    All I can say is that I hope they have a fix as this causes massive problems with Horizon and Instant clones. Horizon has a certain threshold limits and requires the OS to boot by a certain time before the provision task fails. Yesterday I thought I had a DHCP problem but it turns out to be Windows 10 taking forever to boot causing it to fail causing a trickling effect.

                     

                    Anyways I opened a support with VMware to keep them working on this issue. I know more today about this problem with Windows 10 than when I started. Maybe its time to move back to Windows 7. LOL

                     

                    Bob

                    1 5 6 7 8 9 Previous Next