>2 YEARS LATER
>virtualbox still doesnt work on win10
2 YEARS LATER
Other urls found in this thread:
poweronplatforms.com
pastebin.com
twitter.com
Wat
Yes it does, you shit brained fucktard.
it doesn't run any vm at all for a huge chunk of users, including me. and as of now it doesn't seem like there is a fix for whatever problem it seems to have with ntdll.dll.
PEBKAC
listen here you little shit
Works for me.
>2 years later
>they run win10 on raw hardware
Try this: INSTALL LINUX!
Did you try using 32-bit guest operating systems? VirtualBox can't run 64-bit guest operating systems unless you have a special option configured in BIOS. This is a CPU problem, not a Windows problem.
Then KVM with virt-mananger
still doesn't work.
i have intel 6700k OC'd to 4.5ghz. i have tried running at normal clock. i have enabled (and disabled) all of its virtualization features in mobo. i have tried disabling windows defender. i have installed 3 different versions. i have tried 4 different linux distros. i have tried changing every setting i can think of and have been changed by others online (successfully) yet no matter what I still get this error message. I've googled a little bit and people who are getting logs like mine havent found solutions either.
this is not my fault, it is either windows or the VB devs.
here's the log: pastebin.com
Yeah fuck Win10 and Virtualbox.
uh I have Win 2016 running on a KVM hypervisor.
sounds more like you're retarded.
i, too, read the first post of a thread and reply immediately
>it doesn't run any vm at all for a huge chunk of users
[citation needed]
then use a nonshit hypervisor.
since you're a winbabby faggot, you can try hyper-v which will likely work extremely well with wangblows guest OSes.
You can download VMware Workstation directly from VMware for free, and use a product key from Google. It has no license checks at all, just paste in a key.
>wangblows guest os's
so i take it you didn't see "debian2" written in big bold letters
Your problem seems to be "Windows 10", not "Virtualbox".
ok faggot.
use hyper-v and fuck off winbabbby.
Works on my machine.
>it's been 2 calendar years since win 10 was released
Fuck off you're wrong
VMware has problems on W10 too. Had to give extra permissions to some folder or disable UAC or something...
>huge chunk of users
Got a source for that bullshit?