Windows 10 Hosts

[FrederikB]

In the meantime I will rollback to Win8.1 since I have little belief in the short term fix.

So .. this morning rolled back to Win8.1 .. not a great deal, well done microsoft. I blamed Vbox 5 on Win10 of course as the reason. Started Vbox .. same error! Tried to deinstall 5.0.1 since it is beta - now the deinstaller claimed it couldnt find the msi .. of course that was 'back to the future' in Win10 .. luckily the 5.0.0 exe could 'repair' then reinstall - recreate vmdks - same error! Since maybe some of the 5.0.1 installation was left over (and there was!!) I decided to deinstall VB completely and go back to 4.3.30 - recreated the raw disk vmdks - problem fixed.
From there reinstalled the 5.0.0 release, extension pack while not recreated the vmdks, startup - fine
To be sure, recreated the vmdks, startup - fine.

So...99% certain this is a Vbox 5.0.1 beta problem. Very strange how they could suddenly mess up with the rawdisk access.
The 1% is for the combination Win10 Vbox 5.0.0, which might or might not produce the disk access errors. But I've done enough testing for now and 5.0.0 is unusable for me because of the bridge network issue.

@mpack any advice to start a new topic under Windows Hosts or file a bug report against Vb5.0.1 beta?

[Giusi]

Hi

for me
win 10 64 bit host , upgrade from win 8.1,
win xp guest

no sound , solved with the workaround found here,

no network, ex: - bridge- , apart of the default - NAT -
this is instead still unsolved in my case

this with vb 5.0.0 and all its test builds up to the very latest one

cheers

[musty]

Hi,
Since version 4.12 i have no chance with VirtualBox.
Yesterday, i upgraded my windows 8.1 to windows 10 and installed VB 5.0 juste to test.
First start, no go : errors messages like others versions.

So i restarted it with admin right... and Voila everythings works.
I quit VB and restarted it with standard user: and it works again.
After a total reboot of my computer, it still works.
I reinstalled my network card and the bridge mode works too..

I m going to do some tests for sound...
--------------------------------------------------------------------------------------
Windows 10 Pro + VirtualBox 5.00 r101573 + Avast 10.3.2225

[Giusi]

@musty:

which guest s.o you use?

are you running vbox.exe in compatibility win 8 mode?

"I reinstalled my network card"..:
which exact steps have you done?

cheers

[FrederikB]

@mpack any advice to start a new topic under Windows Hosts or file a bug report against Vb5.0.1 beta?

Started a new topic under Windows Hosts named "Vbox 5.0.1 errors in accessing raw disk for Linux guest".
Issue closed for Win10 for now.

Update August 24, 2015: the raw disk read/write access problem was acknowledged and processed as ticket 14425 https://www.virtualbox.org/ticket/14425 and has been fixed in release 5.0.3.

Update August 24, 2015 second post - upgraded to Win10, only to find 5.0.3 may have fixed the disk access (dont know) but it broke again the bridged networking which would work in 5.0.1. Rolled back to Win 8.1 again.

[DefenderII]

latest testbuild 102010 still fails to start from the first time; need 3 failed boots before it starts. Sound problem not fixed

[Wernher]

The sound workaround with sound paying when you start up the guest bothered me as it meant I had to start up a song, mute it start up a virtual box and then unmute again. I then started playing around with various options, hoping ga I will find perhaps a service that I can start or change defaults on so that I don't need to go through this whole rigmarole. Although I haven't yet discovered that magic service. I did find out that I can start Groove Music, without playing any music and if i then start the VBox Guest session, my sound will work. I tried this a number of times and it works constantly.

The option to start VirtualBox as admin, makes no difference and I still can only get NAT to work and sound also still only works with the work around.

I am running W10 latest release and VirtualBox 5.0.1.101902

I have a theory about the sound, that it is one of the Windows 10 Audio Services that causes the issue. So I tried monitoring the services to se if there is a service starting or changing its activity when I kick off Groove Music but haven't een able to pick anything up. When I stop audio endpoint, both VirualBox and Groove Music loses sound. If I restart all the Audio services, only Groove Music recovers sound but not VirtualBox. So this must then lie deeper in the virtualisation and I know too little to do any fault finding on that.

[kapitansky]

Windows 10 Pro
VB 5.0.1 r102010

Wi-Fi connection

I'm not able to select bridged mode for VB network adapter - it reports about invalid settings. Only NAT mode is working fine for me, but in NAT mode I'm not able to connect to VM using ssh

[Giusi]

i confirm yr experience and Wernher 's one

hope vb dev's will able to fix it also for people who has upgraded win 8.1 to win 10 host

[s1lenc3]

I haven't really read the whole topic, thus, I'm not up to date with the latest news and I do not know if someone has already asked/answered this, so I'll just simply ask. When will the Virtual Box officially support Windows 10 as a host? I need to reinstall my laptop's OS, yet I can't do that without being sure that I will not have to waste my time dealing with the encountered problems regarding virtual machines. The computer is being continually used for working purposes, therefore, I cannot spare any time for this. Again, sorry if I'm asking something that has already been answered. I don't really have time to do the research either.

[loukingjr]

There is no 'official' date but suffice it to say it will be announced when it's ready.

[Darjeeling]

Hello,

Finally VB v5.0.1 102010 is working on my Windows 10 64bits.
Using Linux Mint 17.2 64 bits as guest.

Two problem still remain:
1 - If I try to drag&drop to the guest VB crashes
2 - no support for USB 2 and 3

Anyway, thanks for all VB team !!

[Giusi]

suffice it to say it will be announced when it's ready.

..but this is simply the usual behaviour..or not..?!!



any way for me still not solved:

win 10 home 64bit host
win xp sp3 pro ed guest

[HappyCharcher]

When i try to install on my Windows 10 PRO, thr VB 5.0.1 or the new 5.0.2 both just freeze on install, and nothing happens... someone with this problem?

[chryana]

In case anyone is interested, raw disk access works fine with version 5.0.2 102096. VirtualBox is now working well on Windows 10, at least for me.