I’ve followed these steps on two different (as in, different clusters in different cities) VMware ESXi 6.5 Build 7388607 hosts, with the same result: Provision virgin Windows 10 x64 VM with EFI boot, 4GB RAM, 2 vCPU, 50GB HDD, LSI Logic SAS controller, VMXNET3 NIC, HW compatibility version 13 Mount en_windows_10_business_edition_version_1803_updated_aug_2018_x64_dvd_5d7e729e.iso to install Enterprise edition 1803 build 17134.228 from scratch Choose all defaults, provision local account for domain-join option When installation finished, install VMware tools and reboot Check Microsoft for updates, which installs CU 2018-08 (KB4346783) bringing build to 17134.254 Join computer to AD domain and reboot, log in with domain account with local admin permissions Open Feedback Hub and sign in with domain account, works Launch Edge and open multiple external and internal web sites, works Enable Insider Preview builds (associate domain account) for Active Development Fast Ring, reboot Check Microsoft for updates, which installs RS5 1809 build 17751.1 Launch Feedback Hub, works Launch Edge, internal web sites connect, but external web sites all get “Hmmm…can’t reach this page” errors…MSN, Google, Facebook, LinkedIn, you name it Verify Internet connectivity works, and open all web sites just fine with IE Install latest version of VMware Tools (10.2.1) and reboot, no change with Edge behavior Concerned that if Edge is broken, what else is broken If I follow these steps (as close as possible) using VMware Fusion 10.1.3 on macOS, using the same AD domain and domain account as above, there are no Edge problems. Conclusive theory/question: Windows 10 x64 Enterprise 1809 build 17751.1 has Edge problems when hosted on ESXi 6.5 7388607 ? This is concerning, as we have over a dozen W10 Enterprise VMs used by support personnel, running in the main ESXi 6.5 environment. Upgrades to 17751.x will be suppressed unless this issue is resolved.
I'm experiencing a similar issue but on Workstation instead of ESXi, and with VMware tools 10.3.0. I think the UWP apps somehow has issues traversing the network via vmxnet3 vNIC in the more recent Insider builds. I created another vNIC using e1000e, and disabled/disconnected the one using vmxnet3. UWP network issues were gone. I also submitted the issue in the Feedback Hub.
Why do recent builds on fresh install have to reboot before creation of a user at OOBE? This started happening from 1803 onwards.
Noticed this too, however only happends on Clean EN-US install for me. On SV-SE it doesn't. It also occured on 1709 for me.
I think I've found the cause of the Edge problem, and it has nothing to do with VMware. On your Ethernet adapter, disable (uncheck) IPv6. If you have multiple adapters, disable it on all of them. Boom! Edge broken. I've reproduced this on virtual and physical machines.
This happened to me too. After I deletedC:\Windows\software distribution, it started to work normally again
I'm having a issue which I am not sure relates to RS5, my camera is dark in all applications but it has never been dark in any previous Windows versions.
I've heard nothing about RS5 being the last of Win 10. That would be a godsend, an early Christmas, because no longer will anyone have to fear that someone at Microsoft got bored and decided it'd be a good idea to take control away from end-users and so far are blessed they kept the "ExcludeWUDriversInQualityUpdate" registry setting (disable driver updates in Windows Update settings) intact despite hiding it from the GUI in 1803 when it was present in 1709. Or any option really, they wake up and it's like "Dude, we should totally punk consumers by taking away this option from them and force them to use the OS how we want it to be used. What are they gonna do, switch to Linux? They certainly can't 'upgrade' to Windows 7!" They are just changing the codename scheme as far as I know, so after RS5 it'd be "19H1" or something.