Open xxandy opened 6 years ago
I got the exact same issue. Has this been resolved? Cant use it at all :(
Also having this issue with VMWare on Windows 10 pre and post anniversary builds. After running vminstall.exe only on shutdown does the OS column say yes.
Following instructions made it work for me in VMWare on pre-anniversary, haven't tried post yet:
I also hit the same issue with Win 10 1703
.
What you need to do is disable SecureBoot. Since Newer version of vmware workstation will have this feature to support latest VBS features that microsoft has provided. So you might need to disable it from the VMWare VM Settings in Advanced. https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/disabling-secure-boot
Before (with Secure Boot ON).
After (Secure Boot OFF)
Then follow the same steps above and it works fine. Hope it helps.
Followed instructions per: http://virtualkd.sysprogs.org/tutorials/install/
However, in vmmon64, I can't get the "OS" column to say "yes" upon start-up. It is interesting that when I shut down the guest OS, the OS column turns into "yes" - and then a brand new entry pops up - the row that has "yes" is an unusable, old entry, it seems.
In the host, the entry in the VM description file looks like:
In the guest VM, I captured a log of the operation performed by vminstall, using Process Monitor (https://docs.microsoft.com/en-us/sysinternals/downloads/procmon) -- see attachment Logfile.zip. There I can see that the installer overwrote kdcom.dll, at timestamp 2:48:39.9596648.
I can further confirm that by looking at the directory contents of windows\system32 - see attached dir.txt.
dir.txt
Logfile.zip