formosabc's Posts

Yes, how difficult is it to try the upgrade out before GA? If you expect every one to terminate vmware.exe process from task manager (Note that there is the option for single process and ALL process.... See more...
Yes, how difficult is it to try the upgrade out before GA? If you expect every one to terminate vmware.exe process from task manager (Note that there is the option for single process and ALL process. If you terminate ALL vmware.exe processes, even the upgrade process is terminated) then you might want to declare that in big bold letters next time BEFORE the update is downloaded to everyone's system?  Idiots.  
I can confirm VMWare Workstation Pro 15.5 upgrade fixes blank vm guest boot up screen.  I understand that Windows 10 1903 is not supported for Workstation Pro 14 (maybe??) but VMWare should have ... See more...
I can confirm VMWare Workstation Pro 15.5 upgrade fixes blank vm guest boot up screen.  I understand that Windows 10 1903 is not supported for Workstation Pro 14 (maybe??) but VMWare should have at least released an announcement indicating this upgrade is needed... I spent hours trying to figure this out and even deleting a guest OS and then recreating a guest OS... had this information been easier to find it would have made my life easier... I would have felt better about VMWare. Tip:  Do NOT use Windows 10 as your VMWare Workstation Pro host.  Use a "Windows Server" OS instead to avoid this "forced purchase" upgrade by VMWare.  I now have Hyper-V set up on a separate hardware so that I do not have to be dependent on VMWare in the future... go ahead and pull that "force the consumer to pay for a VMWare upgrade" trick again, I'm ready. 
That's a bit shady for VMWare to be using this tactic to force people to pay for an upgrade to fix a problem that was caused by a free update from Microsoft. 
Bit frustrating to search online for the longest time with very scattered and limited information, only to find out there are many folks who also subscribe to this same problem.  I'm running into... See more...
Bit frustrating to search online for the longest time with very scattered and limited information, only to find out there are many folks who also subscribe to this same problem.  I'm running into the black screen during guest boot up then have to force killing the vmware.exe process to shut it down.  I have to reboot the machine to try again.  I used to have OpenVPN & NordVPN installed, but uninstalled them after reading some places online where people mentioned that was part of the problem.  I sometimes can boot up the guest after deleting the lck files, but then they auto-regenerate. VM Name.vmdk.lck VM Name.vmx.lck xxxxxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxxxxx.vmem.lck (randomly generates letters and numbers for the "x") If I can boot up the guest then it runs, but then I have to eventually shut it down.  I power it off and it's a toss up as to if it will power up again or show just a black screen while powered on.  I'm not sure what else to do.  I have tried to clone the VM, but that resulted with the same black screen.  I have deleted all the .lck files, but I thought that worked before but other times it does not work.  Also, if one guest boots up, another guest may not boot up and gets stuck.  So I essentially have not been able to power up all my VMs I used to use together. I have ended up deleting one of my VM guest that has not booted up to desktop successfully even one time, but others I would prefer not deleting. Host is Windows 10 1903. VMWare Workstation Pro 14.1.7 build 12989993
FYI, issue resolved.  I was just about to reinstall the OS through my USB stick but decided to poke around the OS repair "Advanced options".  Next, noticed the "System Restore" option, it seemed ... See more...
FYI, issue resolved.  I was just about to reinstall the OS through my USB stick but decided to poke around the OS repair "Advanced options".  Next, noticed the "System Restore" option, it seemed to have one system restore point listed on the same day the power outage occurred.  I'm not sure what triggered it to create the system restore point?  With nothing else to lose, I selected that and it recovered everything except for the VMWare Workstation Pro program.  It showed my original Network Connections that included VMnet1 and VMnet8.  I just had to install VMWare Workstation Pro again and looks like everything is back in order once again.  This saved so much potential time for me.  Happy happy, yay yay! 
Attempted to "Restore Defaults" from the Virtual Network Editor but that did not fix it.  "Network Reset" on the other hand, it removed all my network adapters and unfortunately I am no longer ab... See more...
Attempted to "Restore Defaults" from the Virtual Network Editor but that did not fix it.  "Network Reset" on the other hand, it removed all my network adapters and unfortunately I am no longer able to reinstall the network drivers.  I tried to install the original network driver (e.g. XPS-8910_Network_Driver_TTTGW_WN32_1.0.0.32_A00.EXE) but the installation package would hang forever during the GUI install process before displaying something like "installation is taking longer than normal, do you want to continue?", either options "Yes or No" just ends the installation.  Well, "Yes" ends with installation successful, but not really installing anything.  "No", aborts the installation I think.  I also tried to update the yellow bang network driver from Device Manager and it also fails to install the driver (I unpackaged the network driver contents into a folder), always seems to just hang on the GUI process for 10-20 minutes.  Welp, thanks for the suggestions anyways.  I might end up with a few broken programs but I think I'll go ahead and reinstall the OS, because I do need the VMs *sigh*. 
Thanks for replying, So I checked the following screenshots below but still did not see VMnet generate: and: Guest network adapters are settings are set to the following: They are ... See more...
Thanks for replying, So I checked the following screenshots below but still did not see VMnet generate: and: Guest network adapters are settings are set to the following: They are configured using NAT so that only the host can reach the guest systems.  I realized that even though the guest system can ping the host IP address, it is unable to UNC to the host share (it used to work no problem).  Very strange, but alas... if I must reinstall the OS, it is what it is.  I'll take any other suggestions if you have them, thanks.
My Windows 10 x64 1709 recently went through a power outage.  I did not shut down my VMWare Workstation Pro 14.1.1 build-7528167 before my UPS was scheduled to shut down the OS.  Totally my fault... See more...
My Windows 10 x64 1709 recently went through a power outage.  I did not shut down my VMWare Workstation Pro 14.1.1 build-7528167 before my UPS was scheduled to shut down the OS.  Totally my fault after reviewing the UPS configuration set up.  I didn't lose any data, however, VMWare Workstation Pro software did end up becoming corrupt.  Since it was installed on a separate hard drive, I had to reinstall VMWare Workstation Pro.  Guests are back up and running.  However, on the host machine the VMware Network Adapter VMnet1, VMnet8, etc that used to be there are no longer present.  VMnet adapter missing: From my other system that has a working VMWare Workstation Pro environment, it has the expected VMnet adapters: I have attempted to REPAIR the installation, but that did not resolve the issue.  I have attempted to uninstall and reinstall VMWare Workstation Pro 14, keeping the VMWare configuration settings, but that did not generate the VMWare adapters.  I do see during the installation phase that it attempts to generate the adapters but I am not sure if it is trying to generate the VMnet adapters on the host or if that is something else, but in the end it does not reproduce the VMnet1/VMnet8, etc. What happens is that I can ping the host machine from the guest virtual machine, but I cannot ping the guest virtual machine from the host machine.  The guest virtual machine can reach out to the internet just fine.  So question, do I need a VMnet adapter in order for the host machine to reach the guest virtual machine?  Am I identifying the problem here or am I looking at an unrelated issue?  If I need those VMware VMnet adapters, how do I get the VMnet to regenerate short of reinstalling the OS?  Anything in the registry I can change/delete/add to start over for the VMWare Workstation Pro without having to dramatically affect all my guest machines (20+)? On a side note:  VMWare needs to create some kind of suspend feature that works with UPS so that before the UPS can shut down VMWare Workstation Pro can safely suspend all guest machines before the host OS shuts down. Thanks for any assistance on this subject.
Anyone verify that Workstation 9 PXE boot feature not working?  I didn't try this in Workstation 8, but it does not work for me in Workstation 9.  Thanks.
I had the same problem too, before I found this thread.  My set up is Windows 7 x64 SP1, 8 GB memory, Q6850 cpu, with over 1TB (RAID 1) of disk space.  I have two Windows 2K8 R2 SP1 running (DC a... See more...
I had the same problem too, before I found this thread.  My set up is Windows 7 x64 SP1, 8 GB memory, Q6850 cpu, with over 1TB (RAID 1) of disk space.  I have two Windows 2K8 R2 SP1 running (DC and Exchange), one Windows 7x64 SP1, Windows XP SP3 and a 3rd party system management appliance (KACE KBOX) running in the environment.  I can power up all VMs and still have approximately 1GB of physical memory left. My previous VM was the Workstation v7 and it worked flawlessly with almost the same set up. I did not upgrade from Workstation 7 to Workstation 8 because my hard drive crashed (did not have RAID 1 set up at the time) because the dog yanked the power cord and the hdd never recovered.  My current system is fresh install of Windows 7 and also fresh install of Workstation 8, no back recovery was used (had none).  So, everything is fresh installed and configured.  I have NAT environment setup. Have been trying to find a fix for this issue for over two weeks but wasn't really eager since my VMs were not really set up complete.  Now that the environment has been set up the way I want it I really wanted to contact VMWare customer support to get this resolved... but finding this forum was easier than finding out how to reach out to support (not even sure if I am eligible for technical support). The work around to disable FDD actually worked for me tonight.  After following the suggestion, I have been testing the VMs all evening and have not experienced the annoying freeze that lasts a few seconds at a time previously.  Still would like to see if this issue can be resolved by some Workstaton patch from VMWare support... not a big deal breaker since I don't really need to use floppy drives. Oh yes, thanks for the work around solution.