To allocate free disk space for a dual boot system with Fedora 40 and Windows 10, you must first shrink the Windows partition to create unallocated space. This is done using the built-in Disk Management tool in Windows before installing or resizing the Linux partition.
The process requires careful attention to partition types and file systems to ensure both operating systems can coexist without data loss. By reserving space correctly, you allow the Fedora installer to recognize the available drive area and configure the bootloader properly.
Preparing Windows 10
Before touching any Linux tools, you need to carve out room on your hard drive from the perspective of Windows. This ensures that the physical sectors are marked as free and ready for a new file system. Start by backing up important data, as partitioning operations always carry a slight risk of corruption if interrupted.
Press
Win + X and select
Disk Management from the context menu. Alternatively, you can run
diskmgmt.msc from the Run dialog. Locate your main Windows partition, which is typically labeled as
C: and formatted as NTFS. Right-click this volume and choose
Shrink Volume.
Windows will query the volume to determine how much contiguous free space is available. Enter the amount of space to shrink in megabytes (MB). For example, entering
51200 will create 50 GB of unallocated space. Click
Shrink and wait for the operation to complete. You should now see a black bar labeled "Unallocated" next to your C: drive.
Booting into Fedora Installation Media
Insert your Fedora 40 USB installer and boot from it. During the startup process, select the option to install Fedora. When you reach the installation type screen, choose
Custom Partitioning or
Blivet-GUI depending on your preferred interface. The default automatic installation might try to resize existing partitions, which can be risky if not configured correctly.
If you use the default Anaconda installer, look for the option to manually configure storage devices. Select the disk that contains the unallocated space. It is crucial to identify the correct disk to avoid wiping your Windows data. The unallocated space will appear as a large block with no file system assigned.
For a standard dual-boot setup, you do not need to create complex RAID or LVM configurations unless you have specific performance needs. Simple ext4 partitions are sufficient for most users. Ensure that the EFI System Partition (ESP) is shared between Windows and Linux. This allows GRUB to manage the boot process for both OSes.
Configuring Partitions in Fedora
In the custom partitioning view, select the unallocated space. Create a new mount point for your root file system. Set the size to your desired allocation, leaving some space for swap if you prefer a separate swap partition over a swap file. Modern Fedora versions often use a swap file within the root partition, so a dedicated swap partition is optional.
Format the new partition as
ext4. Assign the mount point as
/. If you create a home partition, format it as ext4 and assign
/home. Verify that the ESP is mounted at
/boot/efi. This is critical for the bootloader to function correctly.
After configuring the partitions, review the summary. The installer should show that it will write changes to the disk. Proceed with the installation. Once finished, reboot the machine. You should see the GRUB menu offering choices for Fedora and Windows Boot Manager.
Post-Installation Verification
After logging into Fedora, open a terminal to verify the disk layout. Use the command
lsblk to list all block devices. You should see your new partitions listed alongside the Windows drives. Check the sizes to ensure they match what you allocated during the shrinking phase.
Run
df -h to confirm that your root and home partitions are mounted correctly and have the expected capacity. If you created a separate swap partition, check its status with
swapon --show. If using a swap file, verify it exists in the root directory.
It is also wise to test booting into Windows 10 from the GRUB menu. This confirms that the shared EFI partition is accessible to both operating systems. If Windows fails to boot, you may need to repair the bootloader using Windows recovery media. However, proper initial configuration usually prevents this issue.
For more details on managing disk layouts after installation, consider reading about
Resizing Non-Primary Disk Partitions: Windows and Linux Coexistence. This resource provides deeper insights into adjusting space later if needed.
Frequently Asked Questions
Can I shrink my Windows partition while it is running?
Yes, you can shrink the C: drive while Windows is active using the Disk Management tool. This creates unallocated space without needing to boot from external media. Always ensure you have enough free space within the volume to perform the shrink operation successfully.
What happens if I delete the wrong partition during Fedora installation?
Deleting the wrong partition will result in permanent data loss for the files stored on that volume. Always double-check the disk labels and sizes before confirming any deletion in the installer. Using custom partitioning mode gives you full control and reduces the risk of accidental formatting.
Do I need to format the unallocated space before installing Fedora?
No, you do not need to format the space beforehand. The Fedora installer handles the creation of the file system automatically. Attempting to format it in Windows or another tool might interfere with the installer's ability to detect the raw space.
How do I switch between Fedora and Windows at startup?
You switch between operating systems using the GRUB bootloader menu that appears when you start your computer. Select the desired entry using the arrow keys and press Enter. If the menu does not appear, hold the Shift key during boot or check the BIOS settings for boot order.
Is it safe to keep Windows and Linux on the same physical drive?
Yes, it is safe and common to dual boot on a single drive. Both operating systems can access their respective partitions without interfering with each other. Just ensure they share the EFI partition correctly to maintain a unified boot experience.