0

I have dual boot Win10 & Debian on my PC. I want to boot the Debian inside Win10 using Hyper-V. I came across this :

Can't put offline disk 0 on windows 10

and this :

https://superuser.com/a/674714/519592

I read that if I want to use the physical installation of Linux inside the hyper-v,I should put offline the disk 0 where Debian is installed but Windows 10 refuses to do that. This is the structure of the disks of my comp :

pic

I want to put offline the disk0,because the partition of 103.51 GB contains the Debian installation that I want to boot with the hyper-v.

I tried to do it in several ways :

1) Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\Mario Zio> set-disk 0 -isOffline $true
set-disk : Operation not supported on a critical disk.
Activity ID: {a7af4f39-1847-4ec4-9c26-85605f61ba5b}
At line:1 char:1
+ set-disk 0 -isOffline $true
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (StorageWMI:ROOT/Microsoft/..._StorageCmdlets) [Set-Disk], CimException
    + FullyQualifiedErrorId : StorageWMI 41009,Set-Disk

2) in safe mode with networking : nothing

3) disabling the paging file for the disk 0,but it is not enabled,as you can see here :

2

4) Previously I installed the tool Ext2Mgr system driver for Windows. I thought that it could keep locked the drive 0,but I removed it and I restarted the comp,but the drive 0 still can't be put offline.

5) other ideas ?

UPDATE :

For an unknown reason,it doesn't work anymore. I've enabled the hyper-v,but it says that the linux virtual machine failed to start. Check the attached screenshots :

1) 1 2) 2 3) 3 4) 4 5) 5

4
  • 2
    Dati on disk 0 is a active system partition, which means it has the Windows Boot Manager that booted the current system on it. You probably have to move it to C: (i.e. install a copy with bcdboot C:\Windows /s C: and make sure your BIOS(/UEFI) (legacy) boot the disk where C: is on)
    – Tom Yan
    Commented Sep 13, 2017 at 12:15
  • fixed with neosmart bcdedit,by installing the Windows boot manager on Disk 1 and removing it from Disk 0. Thanks man.
    – Marietto
    Commented Sep 14, 2017 at 9:27
  • it doesn't work anymore. I've updated the question.
    – Marietto
    Commented Sep 14, 2017 at 14:14
  • But that's a different issue? Check your BCD for the hypervisor option.
    – Tom Yan
    Commented Sep 17, 2017 at 10:46

1 Answer 1

0

solution : bcdedit /set hypervisorlaunchtype auto

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .