>2 YEARS LATER >virtualbox still doesnt work on win10

Wat

Yes it does, you shit brained fucktard.

>>59132354
>>59132260
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.

>>59132239
>>59132468
PEBKAC

>>59132603
listen here you little shit

>>59132239

Try this:
http://www.poweronplatforms.com/enable-disable-hyper-v-windows-10-8/

>>59132239

Works for me.

>>59132239
>2 years later
>they run win10 on raw hardware

>>59132635
Try this: INSTALL LINUX!

>>59132239
>>59132468
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.

File: 1487402283499.jpg (24KB, 504x393px) Image search: [Google]

24KB, 504x393px

>>59132803
Then KVM with virt-mananger

File: 1467520320313.png (29KB, 258x352px) Image search: [Google]

29KB, 258x352px

>>59132635
still doesn't work.
>>59132839
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: http://pastebin.com/xkmzyTVL

File: Capture.png (57KB, 756x487px) Image search: [Google]

57KB, 756x487px

>>59132239
>>59132468
Yeah fuck Win10 and Virtualbox.

>>59132239
uh I have Win 2016 running on a KVM hypervisor.

sounds more like you're retarded.

>>59132986
i, too, read the first post of a thread and reply immediately

>>59132468

>it doesn't run any vm at all for a huge chunk of users

[citation needed]

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

>>59133032
>wangblows guest os's
so i take it you didn't see "debian2" written in big bold letters

>>59132239
>>59132468
Your problem seems to be "Windows 10", not "Virtualbox".

>>59133122
ok faggot.

use hyper-v and fuck off winbabbby.

>>59132239
Works on my machine.

File: pepe time.jpg (32KB, 545x362px) Image search: [Google]

32KB, 545x362px

>it's been 2 calendar years since win 10 was released

File: birthday.png (84KB, 658x901px) Image search: [Google]

84KB, 658x901px

>>59133730
Fuck off you're wrong

>>59132239
VMware has problems on W10 too. Had to give extra permissions to some folder or disable UAC or something...

File: 1482080883808.png (96KB, 382x491px) Image search: [Google]

96KB, 382x491px

>>59132468
>huge chunk of users
Got a source for that bullshit?