Jump to content
5 posts in this topic

Recommended Posts

Hi, I had a perfect multiboot setup with Windows 10 and MacOS High Sierra, with just those two options available in my Clover GUI. This has been working well for a week. However I installed a few things in Windows, namely APFS for Windows by paragon (an APFS read-only driver for windows) and my APFS SSD mounted successfully. But when I restarted I noticed only the Windows 10 option in Clover. I cannot for the life of me get into Mac OS now. In Win10 the APFS disk isn't mounting anymore. I have tried uninstalling the Paragon software. I have tried arranging boot order in EasyUEFI. Nothing seems to work. I'm locked out of that partition. Is there a way in the Clover Shell64 to force loading of either the recovery partition (which i had hidden) or force loading of the correct macos partition? how do I also mount the EFI partition in windows10?

 

Please if you have any ideas I'd be very appreciative.

 

  • Like 1

Hi, I had a perfect multiboot setup with Windows 10 and MacOS High Sierra, with just those two options available in my Clover GUI. This has been working well for a week. However I installed a few things in Windows, namely APFS for Windows by paragon (an APFS read-only driver for windows) and my APFS SSD mounted successfully. But when I restarted I noticed only the Windows 10 option in Clover. I cannot for the life of me get into Mac OS now. In Win10 the APFS disk isn't mounting anymore. I have tried uninstalling the Paragon software. I have tried arranging boot order in EasyUEFI. Nothing seems to work. I'm locked out of that partition. Is there a way in the Clover Shell64 to force loading of either the recovery partition (which i had hidden) or force loading of the correct macos partition? how do I also mount the EFI partition in windows10?

 

Please if you have any ideas I'd be very appreciative.

Hi there,

 

Take a look here it might help you solve your problem:

 

http://www.insanelymac.com/forum/topic/326494-how-to-make-clover-default-bootloader-after-installing-windows-on-uefi/

You can create a custom entry for your macOS bootloader using the same principal explained in the topic

  • Like 1

Unfortunately it doesn't work. I already tried something similar just after my first post as I managed to get the EFI partition to mount in windows with mountvol and then using elevated Explorer + +

 

For me there was not a bootmgfw.efi only a bootmgfw-orig.efi.

 

I just tried the solution you recommended however and I renamed the Windows Boot manager entry as macOS High Sierra and set the file to be EFi/Boot/bootx64.efi or something like that. I moved it to the top. But nothing changes. And when I log back in, the Windows Boot manager entry has been recreated at the top of the list. My other entries are here. Perhaps you can help figure out what is wrong:-

 

Windows Boot Manager          Boot part: 0: (FAT32, 200MB, ESP)

\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI 

 

Clover start bootmgfw-orig.efi at EFI      Boot part: 0: (FAT32, 200MB, ESP)

\EFI\CLOVER\CLOVERX64.EFI

 

macOS High Sierra      Boot part: 0: (FAT32, 200MB, ESP)

\EFI\BOOT\BOOTX64.EFI

 

In that order of preference. As I mentioned, I moved the order but it reset itself this way.


I restarted again and now the boot options have changed again:

 

"UEFI OS" is bootx64 Efi

"Hard Drive" is Bios boot specification Device

"Clover start bootmgfw-orig.efi at EFI"

"Windows Boot Manager" is back

UEFI:CD/DVD Drive

UEFI:Removable Device

UEFI:Network Device

 

I tried to boot Clover using a backup config which doesn't hide the Recover partition, but it doesn't show the Recovery partition even still.

 

I am assuming that there is some problem with the APFS. Perhaps it needs some Disk Utility scan from the Recovery Partition. However, as I understand it, now with these infernal APFS drivers, the Recovery sector is behind the container. So you cannot actually access it if you lose access to APFS. 

 

Anyone got any other ideas? It's taken me a week to install everything I have this far and was going great, I'd hate to lose that much work and have to reformat and start again.

  • Like 1

Unfortunately it doesn't work. I already tried something similar just after my first post as I managed to get the EFI partition to mount in windows with mountvol and then using elevated Explorer + +

 

For me there was not a bootmgfw.efi only a bootmgfw-orig.efi.

 

I just tried the solution you recommended however and I renamed the Windows Boot manager entry as macOS High Sierra and set the file to be EFi/Boot/bootx64.efi or something like that. I moved it to the top. But nothing changes. And when I log back in, the Windows Boot manager entry has been recreated at the top of the list. My other entries are here. Perhaps you can help figure out what is wrong:-

 

Windows Boot Manager          Boot part: 0: (FAT32, 200MB, ESP)

\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI 

 

Clover start bootmgfw-orig.efi at EFI      Boot part: 0: (FAT32, 200MB, ESP)

\EFI\CLOVER\CLOVERX64.EFI

 

macOS High Sierra      Boot part: 0: (FAT32, 200MB, ESP)

\EFI\BOOT\BOOTX64.EFI

 

In that order of preference. As I mentioned, I moved the order but it reset itself this way.

I restarted again and now the boot options have changed again:

 

"UEFI OS" is bootx64 Efi

"Hard Drive" is Bios boot specification Device

"Clover start bootmgfw-orig.efi at EFI"

"Windows Boot Manager" is back

UEFI:CD/DVD Drive

UEFI:Removable Device

UEFI:Network Device

 

I tried to boot Clover using a backup config which doesn't hide the Recover partition, but it doesn't show the Recovery partition even still.

 

I am assuming that there is some problem with the APFS. Perhaps it needs some Disk Utility scan from the Recovery Partition. However, as I understand it, now with these infernal APFS drivers, the Recovery sector is behind the container. So you cannot actually access it if you lose access to APFS. 

 

Anyone got any other ideas? It's taken me a week to install everything I have this far and was going great, I'd hate to lose that much work and have to reformat and start again.

Just to make sure, did you click "Save" button on the BootIce after changing the boot order? If you don't save the changes they won't take place after rebooting.

 

If you can mount the EFI partition in windows and make see the \EFI\BOOT\BOOTX64.EFI then you can make it the default bootloader.

 

Or you can use a macOS Bootable USB disk and boot into macOS and the re-install the clover to fix the boot partition.

Addition: The EFI partition is outside of the APFS Container and the recovery partition is created inside the APFS container, so if you loose access to the APFS container you will lose access to the recovery partition and all the other partitions that are inside the container.

×
×
  • Create New...