Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working with VirtualBox on Windows 10 build 1703 #8

Open
xxandy opened this issue Sep 20, 2017 · 3 comments
Open

Not working with VirtualBox on Windows 10 build 1703 #8

xxandy opened this issue Sep 20, 2017 · 3 comments

Comments

@xxandy
Copy link

xxandy commented Sep 20, 2017

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

@mischkag
Copy link

I got the exact same issue. Has this been resolved? Cant use it at all :(

@joseph-hannon
Copy link

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:

  1. VM: Copy kdbazis.dll and kdpatch.sys to C:\Windows\System32\drivers
    from virtualKD\target\x86 or x64.
  2. VM: Run kdpatch.reg
  3. VM: In an admin command prompt run:
    bcdedit /debug on
    bcdedit /dbgsettings serial
  4. VM: Restart VM

@manurautela
Copy link

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).

image

After (Secure Boot OFF)
image

Then follow the same steps above and it works fine.
Hope it helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants