What is earliest version of Vbox that supports Win 10 guests?

[Adam2112]

Due to my corporate IT locking down privileges on my computer, Virtual Box V5 will install properly but won't run any virtual machines. IT has no solution for this, but it seems that Vbox V4.3.12 works well. However, I cannot seem to get Win 10 to install. I have reviewed many of the suggestions in this forum, and so far nothing helps - they mostly assume everyone is on Vbox V5. In the VM settings the type of guest options stop at Windows 8.1 so I don't think this version supports Win10. I might be able to move to Vbox V4.x above 4.3.12 if there is a version that supports Win10 guests.

Thanks.

[mpack]

The Windows 10 preview installed just fine for me when I was still using 4.3.12. You had to use the Win8.1 OS version since 4.3.12 didn't know about Win10. There was a problem with the guest additions which was fixed by using slightly later GAs.

That all said, in the long term 4.3.12 is a dead end.

I won't comment on your v5 problems since you've given no information on it.

[socratis]

Virtual Box V5 will install properly but won't run any virtual machines

You wouldn't mind sharing the exact error, would you? Otherwise it's kind of moot to talk about remedies.

If you say that your 4.3.12 is working OK, then you may have been bitten by the Hardened Security that took place right after 4.3.12. Take a look at Discussion of Problems due to Hardened Security to get a feeling of what's going on (warning, it's 320 messages long ). Usual culprits are antivirus, theme changers, debuggers, etc.

If your computer is locked due to IT restrictions, you can only hope that (I will take a leap of faith and assume) your antivirus gets "compatible".

As for the support of Windows 10 clients, even the most recent versions/revisions of VirtualBox are still trying to iron out bugs that are creeping in due to the constant update cycle that Microsoft has introduced with this version.

[michaln]

As for the support of Windows 10 clients, even the most recent versions/revisions of VirtualBox are still trying to iron out bugs that are creeping in due to the constant update cycle that Microsoft has introduced with this version.

That however affects Windows 10 hosts much more than Windows 10 guests. The OP is interested in guest support. The only component that's really affected by Windows 10 changes on the guest side is the Guest Additions.

VirtualBox 4.3.12 is definitely too old, after all it predates Windows 10.

[socratis]

The OP is interested in guest support. The only component that's really affected by Windows 10 changes on the guest side is the Guest Additions.

True, very true.

[Adam2112]

The Windows 10 preview installed just fine for me when I was still using 4.3.12. You had to use the Win8.1 OS version since 4.3.12 didn't know about Win10. There was a problem with the guest additions which was fixed by using slightly later GAs.

I will try to load a later version of GA. Thanks for the suggestion.

I won't comment on your v5 problems since you've given no information on it.

There isn't much more to state. There were several log messages in Vbox logs that components of windows were "unauthenticated" so I don't know if the issue is VirtualBox Hardened Security as indicated by other responses here, or if it is due to Corporate IT limiting my user privileges to the point Vbox needs to run something it cannot with my permissions. I don't have the permissions necessary for Vbox to run as SYSTEM or other account either.

The symptom that I see in that scenario is that the VM window opens but after the Vbox splash screen goes away, the VM locks with a black screen.

[mpack]

I will try to load a later version of GA. Thanks for the suggestion.

Note slightly later. GAs are not intended to be backwards compatible to older versions of VirtualBox. From memory it was 4.3.13 test build GAs that worked - and are no longer available, but you can try 4.3.12 and 4.3.14. I wouldn't go beyond that.

[scottgus1]

If you provide the vboxhardening.log, zipped and attached, we can possibly see what is the issue.