New Windows 10 Insider Preview Fast Build 18305.1003 (19H1) - Dec. 20 Insider

slicendice said:

I think he was referring to VMWare or other virtualization platforms beyond Hyper-V. There's a lot of compatibility issues when Windows hypervisor is enabled.

No, Martin was referring to Sandbox and I wanted to tell / show that there's no need to disable hypervisor because of Sandbox.

cereberus said:

Obviously Sandbox is using a type 1 hypervisor mechanism.

I would imagine you have to disable the hypervisor in same way as for hyper-v.

This is easily done by creating a second boot bcd entry in same way as hyper-v

Worth a try.

Kari said:

No, Martin was referring to Sandbox and I wanted to tell / show that there's no need to disable hypervisor because of Sandbox.

Those day or two that Sandbox worked here, it worked with or without hypervisor and Hyper-V.

Kari said:

No, Martin was referring to Sandbox and I wanted to tell / show that there's no need to disable hypervisor because of Sandbox.

But Martin was referring to this post which clearly states that VMWare does not work with Sandbox enabled and asks if anybody has tried to use Virtual Box with Sandbox enabled. Read the post again.

slicendice said:

But Martin was referring to this post which clearly states that VMWare does not work with Sandbox enabled and asks if anybody has tried to use Virtual Box with Sandbox enabled. Read the post again.

I couldn't get VMware to run in this build at all, with or without Sandbox, Hyper-v or hypervisor.

CountMike said:

Those day or two that Sandbox worked here, it worked with or without hypervisor and Hyper-V.

So you have tested and verified that disabling hypervisorlaunchtype via BCD Edit during Windows boot does not affect Sandbox? I'm not 100% certain I trust it would work without that enabled. It's a feature that is enabled by default, no matter if any virtualization features like Hyper-V has been enabled in Windows.

If hypervisorlaunchtype = enabled then VMWare will definitely not work and will break completely. Only fix is to reinstall VMWare.

slicendice said:

Read the post again.

Toni, I do not want to start an argument, nor would I like to split hairs here, but my post was to clarify what another member posted:

Obviously Sandbox is using a type 1 hypervisor mechanism. I would imagine you have to disable the hypervisor in same way as for hyper-v.

My reply was only to that statement. therefore I said that no, you do not have to disable hypervisor to be able to run Sandbox. That is a fact, my post is correct, and I posted a screenshot to show it.

Kari

Kari said:

Toni, I do not want to start an argument, nor would I like to split hairs here, but my post was to clarify what another member posted:

Obviously Sandbox is using a type 1 hypervisor mechanism. I would imagine you have to disable the hypervisor in same way as for hyper-v.

My reply was only to that statement. therefore I said that no, you do not have to disable hypervisor to be able to run Sandbox. That is a fact, my post is correct, and I posted a screenshot to show it.

Kari

But, but... ...never mind... (sigh)

slicendice said:

So you have tested and verified that disabling hypervisorlaunchtype via BCD Edit during Windows boot does not affect Sandbox? I'm not 100% certain I trust it would work without that enabled. It's a feature that is enabled by default, no matter if any virtualization features like Hyper-V has been enabled in Windows.

If hypervisorlaunchtype = enabled then VMWare will definitely not work and will break completely. Only fix is to reinstall VMWare.

Yes but nothing, but nothing worked, VMware just wouldn't run an OS in it, program itself works until you mount any OS. GSOD and that's it. And no, reinstalling VMware didn't help either. All works fine in regular 1809.

CountMike said:

Yes but nothing, but nothing worked, VMware just wouldn't run an OS in it, program itself works until you mount any OS. GSOD and that's it. And no, reinstalling VMware didn't help either. All works fine in regular 1809.

...oh, was referring to Sandbox working without hypervisor enabled. That should not work. VMWare is a different beast, and most likely this build has broken something VMWare needs.

slicendice said:

...oh, was referring to Sandbox working without hypervisor enabled. That should not work. VMWare is a different beast, and most likely this build has broken something VMWare needs.

Yes, while Sandbox worked, it worked with or without hypervisor, I was trying to get VMware to work so I enabled and disabled all those settings.