sysprogs / VirtualKD

218 stars 86 forks source link

VirtualKD-3.0 VirtualBoxIntegration.exe cannot run ! #4

Open ChengChengCC opened 7 years ago

ChengChengCC commented 7 years ago

According to the document, but when I run the virtualBoxIntergration.exe , it throw an execption . image

ajkhoury commented 7 years ago

I have the same issue, only imminent on Windows 10.

shauleiz commented 7 years ago

Same here. Any known workaround?

ajkhoury commented 7 years ago

I compiled it myself with .NET 4.5 and it works fine. Just compile it yourself.

shauleiz commented 7 years ago

@dude719 thank you for the tip. Does it mean that it is currently compiled for another version of .net? Which one?

LiamKarlMitchell commented 7 years ago

image Same issue on windows 7 x64 SP1

Confirmed re-compiling my self fixed it. VirtualBoxIntegration.zip

ysimhony commented 6 years ago

Ineed. Worked for me too.

saleo commented 6 years ago

thanks @LiamKarlMitchell for the great work, would save time a lot!

im not sure if its the general case that it must keep opened when vmmon.exe running, otherwise the latter would say sth like "...cannt patch on-the-fly, need regsvr32 vboxkd64.dll...", and in fact, i cannot get the regsvr32 run for a whole day after several tries!

saleo commented 6 years ago

one more point: occasionally if vmmon64 say the "cannot patch..." again, you may disable and enable to get things back to normal.

Diastro commented 6 years ago

Hitting the same issue... Any update?

DownWithUp commented 6 years ago

I'm on Windows 10 x64 (1803) And getting the same issue with virtualBoxIntergration.exe I downloaded the source and re-built virtualBoxIntergration.exe and that seemed to fix the problem. Here is my compiled version, if it happens to work for anybody. Win10-64bit.zip

tfrist commented 5 years ago

Thanks @DownWithUp. Your version works for me. Windows 8 x64.

hail2m15 commented 3 years ago

Compiling it myself did the job for me too.. Thanks for the tip.

seonhwi07jp commented 3 years ago

Windows 10 x64(20H2)

I rebuild virtualBoxIntegration.exe and fix this problem. Here is recent version of virtualBoxIntegration.exe.

VirtualBoxIntegration.zip