grub2-filemanager
grub2-filemanager copied to clipboard
a1ive
Windows 10 installation ISO on x86_64-efi
I have the latest Windows 10 ISO (2004) on an exFAT partition.
Boot Windows option loads the installer, I can go through the partitioning menu, but as soon as the installer starts it crashes with a general error.
Boot Map loads up until the the first menu after clicking the first Install button and then complains it has no disk drivers and can't see any fixed disks. Throws up the menu for selecting a driver to load and you can't get past it at all.
Is there something I'm missing here?
EFI is on partition 1 and the exFAT is partition 4.
The map option works as expected - it will not fully work as you found out. The Windows option should not crash - please give details of the 'general error' - picture if possible.
Are you trying to install the system on the hard drive where the Windows ISO is located? It can't be done.You need another hard drive to store the ISO.
It was to a separate fixed HDD. I just tried to recreate this in VirtualBox and it's working. May have been a weird quirk with the hardware I was booting on (some random Lenovo tower, fairly recent). I can check back with that computer beginning of next week.
"Windows could not prepare the computer to boot into the next phase of installation. To install Windows, restart the installation."
I get this error after clearing out all the partitions on the fixed HDD and starting the installation process.
https://youtu.be/FcLXN5myfHo
Explain disk setup? USB boot disk? Internal disks? What disk is the BIOS set to boot to? Is the internal disk a known good disk? Computer make/model? etc.
USB boot disk loading to rEFInd first, which then loads GrubFM
Manually booted the USB from the UEFI boot menu on the computer.
Internal disk is good. 500GB spinning rust. I was able to do a Windows install from a normal USB drive (created from Media Creation Tool) just fine.
Lenovo V520s
I am not sure of the cause.
Maybe you could look at the log files?
When you get the error - type SHIFT+F10 to get to cmd console of Windows
Then type dir /ad /s X:\WINDOWS\*.log
and use Notepad to look at the log files.
This is just a guess. The problem may be that you are booting from a hard disk which has a GPT EFI boot partition and Windows thinks that the USB EFI boot partition is the system boot partition (not sure why?) but then realises it is an external USB disk and so refuses to install the boot code/alter the BCD. The log files should give you a clue. So maybe your USB boot disk needs to just have a simple FAT32 boot partition or just MBR\Legacy partitions?
Yeah that's what I was starting to think as well. I will check the logs when I get a chance.