Hey y’all, I have been trying to get windows to install on top of Fedora for a while now and I couldn’t get it to work. First as anyone would probably thing, I just took the ISO of windows made it bootable in a USB and tried to install it and It didn’t work.
We will talk about the specification later or what might be the cause
New my big brain kicked to action and I thought why don’t I just use my SSD inside a virtual machine and wipe it there instead. well It did work and I was able to boot to windows but only inside the virtual machine I couldn’t boot to windows from my laptop and I couldn’t get the boot entry to show on GRUB (well I did only once though since I tried to reinstall it many times trying different things.
As for my setup I have a MSI Workstation Laptop, I have a NVME SSD and a Normal 2.5" SSD. I have Fedora 40 Installed on my NVME and as for the 2.5" one It has windows (new install so its fine If I need to remove it). I was hoping anyone here could help me get Windows (evil OS) running with GRUB. More info about my setup:
❯ sudo fdisk -l Disk /dev/sda: 111.79 GiB, 120034123776 bytes, 234441648 sectors Disk model: GIGABYTE GP-GSTF Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: B4BF64C3-A973-4873-B1E9-E01C592EB1DBDevice Start End Sectors Size Type
/dev/sda1 2048 206847 204800 100M EFI System
/dev/sda2 206848 239615 32768 16M Microsoft reserved
/dev/sda3 239616 233322495 233082880 111.1G Microsoft basic data
/dev/sda4 233322496 234438655 1116160 545M Windows recovery environmentDisk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: THNSN5128GPU7 TOSHIBA
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9D78AB35-283C-445E-B9A2-B1460DE74A10Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1230847 1228800 600M EFI System
/dev/nvme0n1p2 1230848 3327999 2097152 1G Linux extended boot
/dev/nvme0n1p3 3328000 250068991 246740992 117.7G Linux filesystemDisk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
❯ sudo os-prober /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
❯ lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT NAME FSTYPE SIZE MOUNTPOINT sda 111.8G ├─sda1 vfat 100M ├─sda2 16M ├─sda3 ntfs 111.1G └─sda4 ntfs 545M zram0 8G [SWAP] nvme0n1 119.2G ├─nvme0n1p1 vfat 600M /boot/efi ├─nvme0n1p2 ext4 1G /boot └─nvme0n1p3 btrfs 117.7G /home
For anyone curious about how I got the SSD to run inside the VM here is the command:
sudo virt-install --name windows_install \ --memory 4096 \ --vcpus 2 \ --disk /dev/sdX,bus=sata \ --cdrom /path/to/installationFile.iso \ --os-variant win10 \ --connect qemu:///system \ --boot uefi \ --features smm=on \ --machine q35
Replace the X in ‘/dev/sdX’ with your own drive id or whatever