Page 1 of 1

VirtualBox failing installing windows tested on windows server 2012,2016,2019 logs inside

Posted: 16. Oct 2020, 18:05
by boringDog
Ubuntu works just fine.
2012 windows cannot install required files erro code 0x80070570
2016 windows cannot install required files erro code 0x80070570
2019 i am getting guru medidation

This is on a lenovo laptop 8gb ram , gtx 1050 . intel core i5 7th gen.

I have tested giving bigger /smaller ram /cores etc and also check intel virtual tech to be enaled.

Re: VirtualBox failing installing windows tested on windows server 2012,2016,2019 logs inside

Posted: 16. Oct 2020, 20:50
by hafton
i have also encountered this problem but it is intermittent most of the time it will not install but after a few tries it will usually get there only been using server 2016 and it has only been since the new update i have run into the problem

Re: VirtualBox failing installing windows tested on windows server 2012,2016,2019 logs inside

Posted: 17. Oct 2020, 00:52
by hafton
i fixed my problem
go to you windows features and make sure Hyper-V is turned off

Re: VirtualBox failing installing windows tested on windows server 2012,2016,2019 logs inside

Posted: 17. Oct 2020, 12:29
by boringDog
hafton wrote:i fixed my problem
go to you windows features and make sure Hyper-V is turned off
Hey i don't see any option saying Hyper-V in windows features . The one i see that is related it' s called windows Hypervison platform which is turned off.

Turning it on doesn't fix the issue either. Can someone please help ?


Update: Managed to install windows server 2016 ,
open command prompt run as admin
BCDEdit /set hypervisorlaunchtype off
restart your pc.
It worked.

Please do not lock this as i wanna see if it was just luck or it actually fixed the issue overall.

Re: VirtualBox failing installing windows tested on windows server 2012,2016,2019 logs inside

Posted: 17. Oct 2020, 14:39
by scottgus1
boringDog wrote:Hey i don't see any option saying Hyper-V in windows features . The one i see that is related it' s called windows Hypervison platform
Microsoft seems to have changed the name, but yes it's still the same feature.

These are the tell0tale lines in the vbox.log:
00:00:03.005552 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.076575 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
'VT-x' will read 'AMD-V' for AMD processors.

Many Microsoft services can use Hyper-V, even in Home versions. The bcdedit command most often kills off the underlying Hyper-V subsystem, which allows Virtualbox to run unimpeded.