tracywang's Posts

Let me know your latest Hyper-V and Device guard status when you install a new one, thanks. (It would be straight forward if you attach a screenshot or send the support bundle again)
This is the Device Guard vbs status in my system info. (Type "System info" in Windows search box, check system Summary) This is yours. Please note, the "A hypervisor has been detected" mea... See more...
This is the Device Guard vbs status in my system info. (Type "System info" in Windows search box, check system Summary) This is yours. Please note, the "A hypervisor has been detected" means you have already enabled the Hyper-V, when you disabled, you should see the similar status like above screenshot.
BTW, you did not hit the BSOD because you haven't enabled the secure boot in BIOS, so you will see "Credential guard and device guard" is enabled but not running in the system info.
Thanks for your support bundle, it really helps to find the problem. Form the system information, I found in your Windows 10 host, the "Device Guard Virtualization based security" is enabled. ... See more...
Thanks for your support bundle, it really helps to find the problem. Form the system information, I found in your Windows 10 host, the "Device Guard Virtualization based security" is enabled. We have published the kb and please follow the steps to disable the credential guard and device guard. Windows 10 host where Credential Guard or Device Guard is enabled fails when running Workstation (2146361) | VMware KB
Thanks for using Workstation. In that case, you can open the VM directly if you have the disk read & write privilege.
My Windows 10 version is: 10.0.14393. (1607) And Windows update say: Your device is up to date, Last checked: Yesterday, 6:37PM. The Win 10 image iso I was used is: en_windows_10_enterpris... See more...
My Windows 10 version is: 10.0.14393. (1607) And Windows update say: Your device is up to date, Last checked: Yesterday, 6:37PM. The Win 10 image iso I was used is: en_windows_10_enterprise_version_1607_updated_jul_2016_x64_dvd_9054264.iso Could you let me know your Iso name? BTW, I am still waiting for your Support bundle, which would let me compare our system's difference.
FYI, I personally have a test PC which installed 1607, the WS 12.5.2 works great on it. So your support bundle is really important to us. Thank you.
To collect support bundle, go to Help -> Support -> Collect Support Data.... You log info is very important to us, since your issue seems not a general issue, it may specific to a particular e... See more...
To collect support bundle, go to Help -> Support -> Collect Support Data.... You log info is very important to us, since your issue seems not a general issue, it may specific to a particular environment (hardware or software or combine) to reproduce.
Thanks for using Workstation. I feel sorry for what you have experienced. Could you collect the support bundle and send it to me, so that we can have a look? And we can also have a try in the hou... See more...
Thanks for using Workstation. I feel sorry for what you have experienced. Could you collect the support bundle and send it to me, so that we can have a look? And we can also have a try in the house based on the logging/environment info. My email is: twang at vmware.com if you do not want to attach the bundle to the forum. Thank you.
Thanks for using Workstation. Could you try to reinstall your VMware Tools? Thanks.
Thanks for using Workstation. Cloud you tell me what is your host and guest? Thanks.
Hi DaveyDaveDav, Thanks for using Workstation. This is an issue we are tracking internally. There is an easy fix you can have a try: Go to both your WS server and your dad's machine, check ... See more...
Hi DaveyDaveDav, Thanks for using Workstation. This is an issue we are tracking internally. There is an easy fix you can have a try: Go to both your WS server and your dad's machine, check config.ini under: C:\ProgramData\VMware\VMware Workstation Change the authd client port number from 903 to 902. e.g. authd.client.port = "902" Then reboot both machines and have a try.
Hi Jwermeil, Did you remove vmnet1 and VMnet8 in 12.1.1? If you have tried my workaround in this thread but failed to resolve the issue, could you send me a copy a support bundle? To collec... See more...
Hi Jwermeil, Did you remove vmnet1 and VMnet8 in 12.1.1? If you have tried my workaround in this thread but failed to resolve the issue, could you send me a copy a support bundle? To collect support bundle, there are couple of ways: 1. From Workstation UI: Go to Help -> Support -> Collect Support Data... and upload the support bundle zip file. (If you have any issue to run the UI, you can use method 2) 2. For Workstation Player/Workstation Pro: Go to Player/Workstation Pro installation path: C:\Program Files(x86)\VMware\VMware Player (VMware Workstation), find the vm-support.vbs and double click it. Upload the vmsupport-2016-*-*.zip to the forum, or if you do not want to upload to here, you can send it to me directly. My email is: twang at vmware.com Thank you for your understanding and appreciate it.
Thanks for your feed back. Ralf and Andy, I hope to confirm one thing, after you applied the workaround, did your VM able to connect to vmnet0 as bridged network? The workaround would not make t... See more...
Thanks for your feed back. Ralf and Andy, I hope to confirm one thing, after you applied the workaround, did your VM able to connect to vmnet0 as bridged network? The workaround would not make the vmnet0 always visible in Virtual Network Editor(VDE), you have to give admin privileges to get it visible. So, there are two different issues. 1. Invisible vmnet0 is expected when VDE does not have admin privileges. 2. After applied the workaround, if you give the VDE admin privileges, but the vmnet0 is still invisible and vm cannot use bridged mode, please let us know. TO Andy, For current 12.5 version, we do not recommend you delete any default network adapter, any changs to these default network adapters (vmnet0,vmnet1,vmnet8) would trigger the vmnet0 stop working issue. And restore default would not help. I think you have to apply the workaroud again. Thank you.
Hi ILuvNips, Yes, the biggest problem is "Remove the VMnet1 and VMnet8" will break your bridged network. To apply user's habit of remove the VMnet1 and VMnet8, the workaround I provided is ke... See more...
Hi ILuvNips, Yes, the biggest problem is "Remove the VMnet1 and VMnet8" will break your bridged network. To apply user's habit of remove the VMnet1 and VMnet8, the workaround I provided is keep the VMnet1 and VMnet8 and uncheck the "Connect a host virtual adapter to this network", so you would not hit the bug and you would not have VMnet1 and VMnet8 on your host and the most importantly, the bridged network will work after reboot.
Hello Guys, We noticed that not all the user reproduced the Bridged issue. The user who reproduced this issue has a similar habit that is removed the VMnet1 and VMnet8 in Virtual Network Edito... See more...
Hello Guys, We noticed that not all the user reproduced the Bridged issue. The user who reproduced this issue has a similar habit that is removed the VMnet1 and VMnet8 in Virtual Network Editor. We have a workaround which works in house. This workaround is purposed for the user who wants to use Bridged Network only and does not want to see the NAT and Hosted only network adapter on the host. Could you guys try it out and give me your feedback? Appreciate. 1. Uninstall the 12.5 2. Reboot the host. 3. Install the 12.5 4. Reboot the host. 5. Open Virtual Network Editor, give the admin privilege to the Editor by Click the Change Settings button. (Skip this step if you login the Host OS as administrator and there is no “Change Settings” button) 6. Do not remove VMnet1 and VMnet8, instead, select VMnet1, uncheck “Connect a host virtual adapter to this network”, select VMnet8, uncheck ”Connect a host virtual adapter to this network”. 7. Run ifconfig, there is no VMnet1 and VMnet8 adapter. 8. Run a VM check the bridged network is working 9. Reboot the Host, run a VM to check the network again.
Thank you Guys for confirming. We have a workaround which works in house. Could you guys try it out and give me your feedback? Appreciate. 1. Uninstall the 12.5 2. Reboot the host. 3. Instal... See more...
Thank you Guys for confirming. We have a workaround which works in house. Could you guys try it out and give me your feedback? Appreciate. 1. Uninstall the 12.5 2. Reboot the host. 3. Install the 12.5 4. Reboot the host. 5. Open Virtual Network Editor, give the admin privilege to the Editor by Click the Change Settings button. (Skip this step if you login the Host OS as administrator and there is no “Change Settings” button) 6. Do not remove VMnet1 and VMnet8, instead, select VMnet1, uncheck “Connect a host virtual adapter to this network”, select VMnet8, uncheck ”Connect a host virtual adapter to this network”. 7. Run ifconfig, there is no VMnet1 and VMnet8 adapter. 8. Run a VM check the bridged network is working 9. Reboot the Host, run a VM to check the network again. This workaround is purposed for the user who wants to use Bridged Network only and does not want to see the NAT and Hosted only network adapter on the host.
Hello Guys, I have received a couple of support bundles from you. (Thanks for your greatest support! Really Appreciate!!) With everyone's help, we found one way to reproduce the issue is "Manu... See more...
Hello Guys, I have received a couple of support bundles from you. (Thanks for your greatest support! Really Appreciate!!) With everyone's help, we found one way to reproduce the issue is "Manually removed VMnet 1 or/and VMnet 8 in Virtual Network Editor, then reboot the host, the vmnet0 will missing" So I want to know anybody removed the VMnet1 or/and VMnet8 on your Workstation? If you did not remove VMnet1 or/and VMnet8 but also reproduced the Bridged network issue, please let me know as well. Thank you very much. Best regards, Tony
Hi Ralf, Thanks for providing the detailed info. We are actively investigating this issue now. If you can send us your support bundle, that will be very helpful. To collect support bundle, ... See more...
Hi Ralf, Thanks for providing the detailed info. We are actively investigating this issue now. If you can send us your support bundle, that will be very helpful. To collect support bundle, there are couple of ways: 1. From Workstation UI: Go to Help -> Support -> Collect Support Data... and upload the support bundle zip file. (If you have any issue to run the UI, you can use method 2) 2. For Workstation Player/Workstation Pro: Go to Player/Workstation Pro installation path: C:\Program Files(x86)\VMware\VMware Player (VMware Workstation), find the vm-support.vbs and double click it. Upload the vmsupport-2016-*-*.zip to the forum, or if you do not want to upload to here, you can send it to me directly. My email is: twang at vmware.com Thank you for your understanding and appreciate it.
Hi Camge, I am glad to know your workaround works (That workaround is what we expected to work as well). After you apply the workaround, did you reproduce the bridged networking not working is... See more...
Hi Camge, I am glad to know your workaround works (That workaround is what we expected to work as well). After you apply the workaround, did you reproduce the bridged networking not working issue anymore? If you reboot the host after applying your network, is there any network issue persistent? Thank you for providing the info to us. Appreciate. Best regards, Tony