Describe the bug
When I tried to launch WinDBG Preview version from VirtualKD, it's failed. On Windows 10, the last version of windbg can be started only as app.

To Reproduce
Steps to reproduce the behavior:

1. Install WinDBG Preview from Windows Store
2. Try to start debug with VirtualKD with WinDBG Preview type, don't change path to it!

Expected behavior
Start of WinDBG

Screenshots

Configuration (please complete the following information):

• VirtualKD-Redux version [e.g. 2019.4]:

Additional context
Fix in pull-request: (#35)

More of a query than a bug report.

I recently had to comission a test VM for Win7 (which was another story if pain). Once I had it as I wanted it my next step was to
try to get virtualKD working .... and it didn't.

I could probably do some more diagnosis if you would like me to; but a "nope, we've moved on" also works (I just reverted to my pre-VirutalKD snapshot and set up the serial port)

I was just trying VirtualKD-Redux, but it didn't work for me no matter what I tried to do
I mean the debugger just keeps Waiting to reconnect... well after I removed everything I could not use old normal debugging as it keeps Waiting to reconnect... I don't know what this software patches.

so how do I revert back I mean undo what is been done by VirtualKD-Redux both in the host and virtual machine

secure boot must be disabled before using VirtualKD-Redux

Describe the bug
DbgBreakPoint() on start appears grayed out, however after closing vmmon64.exe and reopening again it appears ungrayed. If you interact with the checkbox it gets grayed and appears unmarked however after restaring again vmmon64 it appears marked and ungrayed.

To Reproduce
Steps to reproduce the behavior:
Open vmmon64, mark
DbgBreakPoint() on start
Check that it gets grayed (not interactuable) and not marked
Close vmmon64
Open vmmon64
Check that now its not grayed and marked

Expected behavior
No need to restark vmmon to mark or unmark the option

Screenshots

Clicked once:

After closing and reopening vmmon:

Configuration (please complete the following information):

• VirtualKD-Redux 2021.0
• VMWare Workstation Pro 16.1
• Windows 10 x64 Workstation 20H2
• Windows 10 x64 Pro 20H2

Describe the bug
I did operations according to README file,but get unexpected result.

To Reproduce
Steps to reproduce the behavior:

1. Create Virtual Machine in Vmware Workstation 16.2.4 build-20089737 pro.
2. ISO file was downloaded from https://www.microsoft.com/zh-cn/software-download/windows10ISO,the version is Windows10 22H2
3. Running the file in target64 on this Virtual Machine,and an entry was created normally.
4. Then I start vmmon64.exe on my physical machine, successfully patched but can't connenct to windbg.

Expected behavior
windbg will auto start and connect the virtual machine normally

Screenshots

I have searched in google and issue in this project but get no result for me.I would appreciate it very much if someone could give me some helpful advice

Describe the bug
Debuggee never connects to debug pipe.

To Reproduce
Steps to reproduce the behavior:
Follow the installation tutorial using the configuration below.

Expected behavior
Debuggee connects to pipe and debugger breaks execution.

Screenshots

Configuration (please complete the following information):

• VirtualKD-Redux version [e.g. 2019.4]: 2021.3
• VMware or VirtualBox version [e.g. VMware Workstation 15.5.0 build-14665864]: VirtualBox 6.1.12 r139181 (Qt5.6.2)
• OS running on the host [e.g. Windows 10 1903 64-bit]: Windows 10 10.0.19043 N/A Build 19043
• OS running in the guest VM [e.g. Windows 7 SP1 32-bit]: Windows 10 10.0.17763 N/A Build 17763

Hi! I just installed the latest version of WinDBG on my new PC. However, vmmon64.exe has WinDBG Preview radio button disabled. I tried to open the windbgx.exe via the "Sideloaded windbg preview path..." but it says system cannot open this file.

Describe the bug
When I open VirtualBoxIntegration in my host, I get the following exception:

To Reproduce
As suggested in the doc, Vbox is closed.
Just run VirtualBoxIntegration.exe with or without admin priv.

Expected behavior
A GUI to be able to enable the VM.

Configuration (please complete the following information):

• VirtualKD-Redux version [e.g. 2019.4]: VirtualKD-Redux-2020.5
• VMware or VirtualBox version [e.g. VMware Workstation 15.5.0 build-14665864]: VirtualBox 6.1.18
• OS running on the host [e.g. Windows 10 1903 64-bit]: Windows 10 19042 20H2 64 bits.
• OS running in the guest VM [e.g. Windows 7 SP1 32-bit]: Windows 7 SP1 64-bit

Additional context
Add any other context about the problem here.

Cheers.

Latest version 2020.5 doesn't work with latest Windows 8.1 x64 (Build 9600). All default installation steps followed, after restart and disabling driver signature requirements it doesn't start a debugger.
VM is shown in GUI without PipeName and other following stats.

Windows 10 x64 works fine.

"cn_windows_7_professional_with_sp1_x64_dvd_u_677031.iso" can not boot

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Configuration (please complete the following information):

• VirtualKD-Redux version [e.g. 2019.4]:
• VMware or VirtualBox version [e.g. VMware Workstation 15.5.0 build-14665864]:
• OS running on the host [e.g. Windows 10 1903 64-bit]:
• OS running in the guest VM [e.g. Windows 7 SP1 32-bit]:

Additional context
Add any other context about the problem here.

Hi,
Can't using your mod on Windows Server 2003R2 x86 (en_win_srv_2003_r2_enterprise_x64_with_sp2_vl_cd1_x13-48614.iso)
The BSOD happened on logging in.
Reinstalling the OS is not helped.

00 ba6085f8 80826c77 00000003 00000002 00000000 nt!RtlpBreakWithStatusInstruction
01 ba608644 80827b84 00000003 00000000 e2571a98 nt!KiBugCheckDebugBreak+0x19
02 ba6089dc 80827f7d 00000044 e2571a98 00000d7c nt!KeBugCheck2+0x5ea
03 ba6089fc 8081e54d 00000044 e2571a98 00000d7c nt!KeBugCheckEx+0x1b
04 ba608a34 f75ead33 8f3e01a8 8ff5b460 ba608a58 nt!IopfCompleteRequest+0x2f7
05 ba608a44 8081e185 902ca2b8 900d8f28 900d8f28 termdd!IcaDispatch+0x13d
06 ba608a58 808fb411 ba608c04 902ca2a0 00000000 nt!IofCallDriver+0x45
07 ba608b40 80939f4d 902ca2b8 00000000 8f3ee9d8 nt!IopParseDevice+0xa35
08 ba608bc4 80936066 00000000 ba608c04 00000040 nt!ObpLookupObjectName+0x5c1
09 ba608c18 808ed0b5 00000000 00000000 00000001 nt!ObOpenObjectByName+0xea
0a ba608c94 808ee36b 000b3204 c0100000 00c9f538 nt!IopCreateFile+0x447
0b ba608cf0 808f0faa 000b3204 c0100000 00c9f538 nt!IoCreateFile+0xa3
0c ba608d30 8088b658 000b3204 c0100000 00c9f538 nt!NtCreateFile+0x30
0d ba608d30 7c8283ac 000b3204 c0100000 00c9f538 nt!KiSystemServicePostCall
0e 00c9f500 7c826ba9 74d9121e 000b3204 c0100000 ntdll!KiFastSystemCallRet
0f 00c9f504 74d9121e 000b3204 c0100000 00c9f538 ntdll!NtCreateFile+0xc
10 00c9f560 74d9148b 000b3204 0009e8b0 00000032 ICAAPI!_IcaOpen+0x59
11 00c9f580 74d923a7 000001c0 000b3204 00000001 ICAAPI!_IcaStackOpen+0x78
12 00c9f5a4 7655b2f3 000001c0 00000003 00000000 ICAAPI!IcaChannelOpen+0x41
13 00c9f6d4 76552263 000afe48 00c9fd10 00c9f8a0 termsrv!WaitForConsoleConnectWorker+0x144
14 00c9f858 765567bb 00000000 00000170 00000001 termsrv!WinStationNotifyLogonWorker+0x3db
15 00c9f89c 77c80125 0009e930 00c9fcc0 00000000 termsrv!RpcWinStationNotifyLogon+0x9e
16 00c9f8f0 77ce53e1 7655671d 00c9fae0 00000010 RPCRT4!Invoke+0x30
17 00c9fcf8 77ce55c4 00000000 00000000 0009ebe4 RPCRT4!NdrStubCall2+0x299
18 00c9fd14 77c7ff0a 0009ebe4 000b8f48 0009ebe4 RPCRT4!NdrServerCall2+0x19
19 00c9fd48 77c803bf 7656f984 0009ebe4 00c9fdec RPCRT4!DispatchToStubInCNoAvrf+0x38
1a 00c9fd9c 77c802e5 00000020 00000000 7657589c RPCRT4!RPC_INTERFACE::DispatchToStubWorker+0x11f
1b 00c9fdc0 77c8117d 0009ebe4 00000000 7657589c RPCRT4!RPC_INTERFACE::DispatchToStub+0xa3
1c 00c9fdfc 77c81291 0009e978 000b6280 000b7170 RPCRT4!LRPC_SCALL::DealWithRequestMessage+0x42c
1d 00c9fe20 77c88688 000b62b8 00c9fe38 0009e978 RPCRT4!LRPC_ADDRESS::DealWithLRPCRequest+0x127
1e 00c9ff84 77c887a2 00c9ffac 77c8873d 000b6280 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x430
1f 00c9ff8c 77c8873d 000b6280 00000000 00000000 RPCRT4!RecvLotsaCallsWrapper+0xd
20 00c9ffac 77c7b03e 0009b070 00c9ffec 77e6484f RPCRT4!BaseCachedThreadRoutine+0x9d
21 00c9ffb8 77e6484f 000b6360 00000000 00000000 RPCRT4!ThreadStartRoutine+0x1b
22 00c9ffec 00000000 77c7b023 000b6360 00000000 kernel32!BaseThreadStart+0x34

I haven't fully characterized this yet but it appears that deploying this update (its marked as preliminary or some such) breaks VirtualKD.

I did a full update of Win11 (10.0.22000.593) and it was OK then I applied KB5012643

Ver now reports (10.0.22000.652) and VirtualKD no longer works. Further Trying to reinstall gives the popup

Cannot create KDBAZIS/DLL: Access is Denied

I have the VM snapshotted if you need me to prod further

Configuration

• VirtualKD-Redux version 2021.3
• VMware or VirtualBox version VMware 16.2.3 build-19376536
• OS running on the host Win 10 10.0.19043.1645
• OS running in the guest Win 11 10.0.22000.652

Hello. VirtualKD-Redux Build errors in Visual Studio 2022 on Windows 11

Ошибка RC1015 cannot open include file 'afxres.h'. kdbazis-kernel C:\temp\vkd\Guest\kdbazis\kdvm.rc 11
Ошибка RC1015 cannot open include file 'afxres.h'. kdpatch-kernel C:\temp\vkd\Guest\kdpatch\kdpatch.rc 11
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vminstall E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vminstall E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240
Ошибка C2065 E_BOUNDS: необъявленный идентификатор kdclient E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 449
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vminstall E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vminstall E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240
Ошибка C2065 E_BOUNDS: необъявленный идентификатор kdclient E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 449
Предупреждение Missing VIX header. VMware Workstation Pro must be installed during build for snapshot support. kdclient C:\temp\vkd\Host\kdclient\CL 1
Ошибка C2065 E_BOUNDS: необъявленный идентификатор kdclient E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 449
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vminstall E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vminstall E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240
Ошибка RC1015 cannot open include file 'afxres.h'. vmxpatch C:\temp\vkd\Host\vmxpatch\vmxpatch.rc 11
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vmmon E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vmmon E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240
Ошибка C2065 E_BOUNDS: необъявленный идентификатор vmmon E:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcoll.h 240

--------- make.bat builds error -------------

  "c:\temp\vkd\VirtualKD-Redux.sln" (целевой объект по умолчанию) (1) ->
   "c:\temp\vkd\Guest\vminstall\vminstall.vcxproj" (целевой объект по умолчанию) (5) ->
   (Целевой объект ClCompile) ->
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(240): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Guest\vminstall\vminstall.vcxproj]
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(240): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Guest\vminstall\vminstall.vcxproj]
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(240): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Guest\vminstall\vminstall.vcxproj]
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(240): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Guest\vminstall\vminstall.vcxproj]
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(240): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Guest\vminstall\vminstall.vcxproj]
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(240): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Guest\vminstall\vminstall.vcxproj]


   "c:\temp\vkd\VirtualKD-Redux.sln" (целевой объект по умолчанию) (1) ->
   "c:\temp\vkd\Host\kdclient\kdclient.vcxproj" (целевой объект по умолчанию) (3) ->
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(449): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Host\kdclient\kdclient.vcxproj]
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(449): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Host\kdclient\kdclient.vcxproj]
     e:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\atlmfc\include\atlsimpcol
   l.h(449): error C2065: E_BOUNDS: необъявленный идентификатор [c:\temp\vkd\Host\kdclient\kdclient.vcxproj]

Предупреждений: 1
Ошибок: 11

Who can tell you what?

Hey, I noticed that VMware Workstation Pro recently released version 16.0.0, does VirtualKD-Redux still work?

Have a nice day! 😄

Every now and then (more now than then), when I shut down a VM, the status of the VM in VirtualKD is showing as green and the WinDbg window isn't closing even though I have it set to do so when the VM is shut down.

stiil got "Still cannot find RPC dispatcher table. Try another VMWare version :-("

Describe the bug
I cannot get VirtualKD to work. I've followed the tutorial, including installing the certs on the host. Virtualbox fails to load kdclient64.dll

To Reproduce

• Close VB
• Run VirtualBoxIntegration
• Enable my freshling installed Win10 VM
• Start vmmon64
• Go back to VirtualBoxIntegration window, click Launch VirtualBox
• In virtual box, boot the Win10 VM
• Popup that VB cannot load kdclient64.dll
• Cannot attach debugger (clicking on Run Debugger doesnt do anything)

Expected behavior
I expected the Run Debugger to do its thing.

Screenshots

Configuration (please complete the following information):

• VirtualKD-Redux version 2020.5
• VirtualBox Version 6.1.18 r142142 (Qt5.6.2)
• OS running on the host: Windows 20H2 OS Build 19042.804
• OS running in the guest: Windows 1809 OS Build 17763.1039

Describe the bug
In cn_ windows_ 7_ enterprise_ with_ sp1_ On x64 system, the vminstall program in the installation target64 folder cannot be started. It always enters the automatic repair interface of windows system.

To Reproduce
Steps to reproduce the behavior:
1.Install pure win7 SP1
2.Install vminstall under the target64 folder
3.Restart boot, there will be an this BUG

Expected behavior
It should be a normal boot

Screenshots
1.

2.

Configuration (please complete the following information):

• VirtualKD-Redux version 2020.3
• VMware or VirtualBox version VMware Workstation 16.0.0 build-16894299
• OS running on the host Windows 10 1809 64-bit
• OS running in the guest Windows 7 SP1 64-bit:cn_windows_7_enterprise_with_sp1_x64_dvd_u_677685.iso

Additional context
Nothing

The reason may be Microsoft（ https://msrc-blog.microsoft.com/2022/04/05/randomizing-the-kuser_shared_data-structure-on-windows/ ）As a result of the randomization of SharedUserData , the content on SharedUserData does not have the write attribute, and the content with the write attribute is mapped to the MmWriteableSharedUserData address (they all point to the same physical memory at the same time, and the address is randomized with the MiProtectSharedUserPage function. Therefore, the kdreceivepacket function should not be used directly.This is my suggestion for change. I'm sorry my English is very poor.

static PKUSER_SHARED_DATA NtSharedUserData = SharedUserData;
static PKUSER_SHARED_DATA *KdvmSharedUserData = &NtSharedUserData;

NTSTATUS SearchPattern(IN const UCHAR *pattern, IN UCHAR wildcard, IN ULONG_PTR len, IN const VOID *base, IN ULONG_PTR size, OUT PVOID *ppFound)
{
ASSERT(ppFound != NULL && pattern != NULL && base != NULL);
if (ppFound == NULL || pattern == NULL || base == NULL)
return STATUS_INVALID_PARAMETER;

for (ULONG_PTR i = 0; i < size - len; i++)
{
    BOOLEAN found = TRUE;
    for (ULONG_PTR j = 0; j < len; j++)
    {
        if (pattern[j] != wildcard && pattern[j] != ((const UCHAR *)base)[i + j])
        {
            found = FALSE;
            break;
        }
    }

    if (found != FALSE)
    {
        *ppFound = (PUCHAR)base + i;
        return STATUS_SUCCESS;
    }
}

return STATUS_NOT_FOUND;

}

NTSTATUS GetMmWriteableSharedUserData()
{
NTSTATUS status = STATUS_SUCCESS;
PCHAR resultPtr = NULL;
UNICODE_STRING routineName;
PVOID FsRtlDismountComplete = NULL;

RtlUnicodeStringInit(&routineName, L"FsRtlDismountComplete");
FsRtlDismountComplete = MmGetSystemRoutineAddress(&routineName);
if(FsRtlDismountComplete == NULL)
    return STATUS_SUCCESS;

status = SearchPattern((const UCHAR*) "\x48\x8B\x05", 0xff, 3, FsRtlDismountComplete, 0x16, (PVOID*)&resultPtr);
if (NT_SUCCESS(status) == TRUE)
{
    // MmWriteableSharedUserData
    KdvmSharedUserData = (PKUSER_SHARED_DATA *)(resultPtr + (ULONG_PTR)(*(PULONG)(resultPtr + 3)) + 7);
}
return STATUS_SUCCESS;

}

I try filling its dialog box out, then shutting down and relaunching the VM. No log file is being generated in the directory that I set.

Not so much a bug as a "hmmm any one else seen this?"

I just trued to update one of my VMs to 2004 from the DVD and it failed until such time as I uninstalled a particular companies driver. I am used to the funkiness for WU so that was a "whatever". The odd thing was after I got up to 2004 and reinstalled the driver would be uninstalled on reboot unless I rebooted without virtual-KD.

Once I had done that and established that the driver was there I could reboot with the debugger enabled just fine.

This is just weird and I don't have many cycles to debug it, but I wondered if anyone else had seen anything similar?

IF not, just close this issue - it isn't a bug (in VirtualKD) or anything, just weird.

Describe the bug

To Reproduce
Steps to reproduce the behavior:
Run vminstall.exe and press "Install"

Expected behavior
It works

Screenshots

Configuration (please complete the following information):

• VirtualKD-Redux version 2021.0
• VMware [e.g. VMware Workstation 15.5.0 build-14665864
• OS running on the host -- Windows 10 Pro 20H2 64-bit:
• OS running in the guest VM -- Windows 10 Pro 2004 64-bit

When using VirtualKD-Redux with existing VMs, where kdbazis.dll was installed from the original VirtualKD fork, vmmon complains about version incompatibilities:
"Warning: kdbazis.dll version x.xx was loaded ... while version 2020.5 was expected ... please upgrade"

Is the kdbazis.dll version check also so strict that it kicks in on every VirtualKD-Redux update?

Would it be possible to relax this version check, assuming that there is a way to be backwards compatible with kdbazis.dlls present in older VirtualKD/VirtualKD-Redux releases?

The version check is fine when installing new VMs but forces the user to upgrade all existing guest VMs on a VirtualKD update on the host. It would be really nice if this could be avoided, unless absolutely necessary.

host: win10 1909
virtual machine: win7 (vmware)
vmware:15.5.1 build-15018445
I have disabled driver signing enforcement, but the host is still red.

Life withouth VirtualKD would have sucked big time.

Describe the bug
When pressing Restore VM Snapshot a message appears(photo attached)
The machine has green light, is patched and when the debuger attached it breaks perfectly.

To Reproduce
Steps to reproduce the behavior:
Launch the machine atach the debugger and so on...
Press Restore VM Snapshot

Expected behavior
Restore the last snapshot of the machine? I dont really know what this button should do

Screenshots

Configuration (please complete the following information):

• VirtualKD-Redux 2021.2
• VMware 16.1.2
• OS running on the host Windows 10 21H1
• OS running in the guest Windows 10 20H2

My system is WIN10 20H2 19042.985 X64

Thanks for the great work with keeping VirtualKD alive! I would like to add a small feature request.

It would be nice if kdbazis.dll was test signed, just like it was in the original VirtualKD fork. A test signed DLL is more easily accepted in the target (I have only tested with Windows 7, but what is written below may also apply to other versions).

An x86 OS accepts the DLL automatically. An x64 OS can be made to accept by enabling the test signing boot menu option (either in the default entry, or in a separate entry):
bcdedit /set testsigning on

Test signing mode is also enabled when connecting with a kernel debugger. (which is convenient since kernel debugging is the main use of VirtualKD).

In both x86/x64 the system can be started from a simple menu selection, avoiding the need for the F8 signature disable step.

1. my host is win10 10.0.18362.356
2. VirtualKD-Redux 2020.1
   windbg preview and Custmo radio checkbox can't click, now i'm run windbg preview, File-->Attach to Kernel , replace pipe name to VirtualKD-Redux Pipe name(eg: kd_Win7_x86) , final attach success

Describe the bug
disable driver signature -> BSOD

Host:
...

To Reproduce
Steps to reproduce the behavior:

1. Copy 'target64' to Target Machine d:\target64
2. Run d:\target64\vminstall.exe
3. Click Install,and nextnextnext..
4. reboot
5. select VKD Item,F8, select disable driver signature
6. BSOD

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Configuration (please complete the following information):

• 2020.3
• VMware Workstation 16.0.0 build-16894299
• Windows 10 2004 64-bit
• Windows 10 2004 64-bit

more:

VKD-Redux + disable signature -> BSOD
windows 10 + disable signature ->no BSOD

Doesn't work on windows 7 with virtualbox 5.1. VMs don't show up. VirtualboxIntegration.exe only crashes.

Do you have plans to support Hyper-V?

I have a certificate available
I try signature to kdbazis.dll and kdbazis.dll, but it's errors if "i not disable driver sinature"
Is there a way not to “disable driver signature” ?

Can VirtualKD-Redux be modified to fix that?

Duplicate of #

Originally posted by @punzalanrhemy in #14 (comment)

Describe the bug

After I run vminstall.exe and reboot for debugging, the vmware-vmx.exe process constantly takes ~12% cpu when I stop on a breakpoint. When I resume execution, the CPU usage is not high. Also, when I resume execution the Poll Rate is around 63 - is it normal? Can you explain a bit about the Poll Rate?

I tried to to analyze the problem and then I figured out that the problem only happens when "Number Of Cores Per Processor" is not 1.

To Reproduce
Steps to reproduce the behavior:

1. Install a vm and configure "Number Of Cores Per Processor" to 2
2. Run vminstall.exe
3. Run bcdedit /debug on
4. bcdedit /dbgsettings serial debugport:1 baudrate:115200
5. Restart VM and hit ALT-DELETE (Windbg Preview)
6. The cpu goes high.

Expected behavior
I expect that CPU will be 0..

Screenshots

Not in break:

During break:

Configuration (please complete the following information):

• VirtualKD-Redux version: 2019.6
• Vmware Workstation 15.5.2 build-15785246
• Debugger: Windbg Preview / kd.exe
• OS running on the host: Windows 10.0.18363.657
• OS running in the guest VM: Windows 10 - it happened in different versions of windows 10 build 19603 and RS5.

Context

*************************************************************************************
*VirtualKD-Redux patcher DLL successfully loaded. Patching the GuestRPC mechanism...*
*************************************************************************************
Searching patch database for information about current executable...
No information found.
Waiting for VMWare to initialize (5900 ms more to wait)
Analyzing VMWARE-VMX executable...
Building list of EXE sections... 21051K of data found.
Scanning for RPC command name strings...
Finished scanning. Found 56 strings.
Searching for string references...
Found 31 string references.
Found 3 structures resemblant to RPC dispatcher table.
(address 00007FF61EFF4C38, matched pointers: 1)
(address 00007FF61EFF4C48, matched pointers: 1)
(address 00007FF61F445410, matched pointers: 29)
Analyzing potential RPC dispatcher tables...
Potential RPC table analysis complete. Found 1 candidates.
(address 00007FF61F4447E0, entries: 110, free entries: 36)
Using RPC dispatcher table at 0x7FF61F4447E0 (110 entries)
Waiting for RPC table to be initialized by VMWare...
RPC table initialized. Patching it...
Successfully patched entry #1
VMWare reset monitor activated...

I tried to understand which thread in vmware-vmx is the high CPU thread and it looks like it's some code inside vmware-vmx.exe that runs in a loop calling DeviceIoCtl to vmx86.sys (looks like a function called RunVM of VCPU) - If I suspend this thread, the VM won't have high CPU (obviously) but when I try to resume the debugger the VM gets stuck, looks like it's the thread that's responsible for virtualizing one of the virtual CPUs. I then noticed that the VM was configured for 2 cores per processor. When I changed it to 1, the problem was solved.

i am using VirtualKd Redux 2020.4 and it seems not to work with Virtualbox, it does not show the virtual machines in the list.
i am using VirtualBox 6.1.16, any idea? thanks

Describe the bug
When I run a VM and it run debugger it (and hit break) it doesn't show anything. I'm pretty sure I installed it correctly. However I'm a noob. Relatively new to programming and completely new to driver programming so it might be my fault. If so I'm sorry.

To Reproduce
Run VM, look at your application: empty box, no matter what you press

Expected behavior
It should say something like in the tutorial

Screenshots
https://imgur.com/a/e7NVdeQ

Configuration (please complete the following information):

• VirtualKD-Redux version [e.g. 2020.2]
• VMware or VirtualBox version [VMware Workstation Pro 15.5.5 build- 16285975]
• OS running on the host [Windows 8.1 PRO (last release pretty sure) 64-bit]
• OS running in the guest VM [Windows 10 PRO 1909 64-bit]

Describe the bug

VirtualboxIntegration throwing an error; vmmon64.exe unable to "patch VirtualBox in the fly" when launched - no VM visibility in vmmon64.exe.

To Reproduce
Steps to reproduce the behavior:

• Follow the Tutorial: https://github.com/4d61726b/VirtualKD-Redux/blob/master/VirtualKD-Redux/Docs/Tutorial.md
• As instructed, run VirtualBoxIntegration.exe,
• Try vmmon64.exe...

Expected behavior
Virtualbox VM should be available/usable/visible as a VirtualKD-Redux client.

Screenshots

Configuration (please complete the following information):

• VirtualKD-Redux 2022.1
• VirtualBox Version 7.0.2 r154219 (Qt5.15.2)
• Host: Windows 10 21H2 19044.2251 64-bit
• Guest: Windows 10 21H2 19044.2251 64-bit

Additional context
None

Describe the bug
Not exactly a bug, but something of note -- some versions of kdpatch.sys are being flagged as malware. For example:

https://www.virustotal.com/gui/file/c1c0bda0bd4d36288696e6f5a8b2e4d22c1862b00f74c4550e5beb8476ed8c6a/detection

To Reproduce
Steps to reproduce the behavior:

1. Grab the 2019.6 release
2. Upload the target64\kdpatch.sys file to https://www.virustotal.com/gui/home/upload

Expected behavior
File should not be flagged as malware.

1. If this is malware, please let us know so we can stop using it :-)
2. If it's not malware, maybe signing it would help? At least some of the detections appear to be heuristic-based.

Screenshots

Configuration (please complete the following information):

• VirtualKD-Redux 2019.6
• VMware or VirtualBox version: n/a
• OS running on the host: Windows 10 1903
• OS running in the guest VM: Windows 7 x64

Hello. Forgive for my poor English.
I update VMware to 15.5.0 build-14665864 and I found virtualkd 3.0 down.
VirtualKD-Redux can work on Win10 os.
But it cannot work on Win7 os.
And I have no idea how to fix it.

Describe the bug
Failed to load VirtualKD library when start vm in virutalbox

To Reproduce
Steps to reproduce the behavior:

• Follow the Tutorial: https://github.com/4d61726b/VirtualKD-Redux/blob/master/VirtualKD-Redux/Docs/Tutorial.md
• As instructed, run VirtualBox7_Integration.exe, enable the vm
• Start vm in virtualbox

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Configuration (please complete the following information):

• VirtualKD-Redux version [2022.2]:
• VMware or VirtualBox version [VirtualBox 7.0.2]:
• OS running on the host [Windows 11 22h2 64-bit]:
• OS running in the guest VM [Windows 7 SP1 64-bit]:

Additional context
none

Hi,

I've followed your tutorial, booted the guest using the correct boot option, disabled driver signing, and am running vmmonitor.

Unfortunately, the light under PID is red, and there are no messages at all in the debug message window.

Hitting run debugger does nothing.

Has vmware workstation 15.5.2 broken this app?

When I open VirtualBoxIntegration.exe I get errors attached to txt files:
VirtualKD-Redux-Integration-Error.txt
VirtualKD-Old-Integration-Error.txt
First on Redux 2021.2 and second on the legacy 3.0.
I open it in host system, VM isn't opened.
I use windows 10 19042(20H2).

IDA and WinDBG debug my driver file together, and WinDBG only using KD dual-machine debugging, how to debug their own driver software