You need a file from Fedora, but you are stuck in Windows
You booted into Windows to finish a presentation, only to realize the configuration file you need lives on the Fedora partition. You plug in an external drive formatted as ext4, and Windows Explorer shows nothing but empty space. You need the data now, not after a reboot. You cannot simply click the drive and copy the file.
Windows does not understand the ext4 filesystem. Fedora uses ext4 by default because it is fast, reliable, and integrates with the Linux kernel. Windows uses NTFS. The two filesystems store metadata differently. Windows has no built-in driver to read ext4 inodes or block groups. You need a bridge to access the data.
Windows does not speak ext4
ext4 stands for fourth extended filesystem. It manages data using inodes, block groups, and a journal to ensure consistency. The journal records changes before they are written to the main filesystem. If the power fails, the journal allows the system to recover without corruption.
Windows NTFS uses a Master File Table and a different journaling structure. The Windows kernel cannot parse ext4 metadata. When you select a drive letter for an ext4 partition, Windows sees the raw disk blocks but cannot map them to files. You need a component that understands ext4 to interpret the data.
Third-party Windows drivers exist, but they carry risks. Many are outdated, lack read-write support, or can corrupt the ext4 journal if the system crashes. The safest approach uses the Windows Subsystem for Linux. WSL runs a real Linux kernel inside Windows. That kernel includes the official ext4 driver. You get native filesystem support without installing risky third-party software.
Mount read-only. Writing to an ext4 partition from Windows can corrupt the journal and leave Fedora unbootable. Use read-only access unless you have a specific reason to modify files.
Mount the partition with WSL
WSL provides a Linux environment where you can mount the ext4 partition safely. WSL2 is the current standard. It runs a lightweight virtual machine with a full Linux kernel. This kernel can mount ext4 partitions directly.
First, confirm WSL is installed and check the version. You need WSL2 for reliable disk access.
wsl --list --verbose
# List installed distributions and their WSL version
# Look for VERSION 2 in the output
# If you see VERSION 1, convert with wsl --set-version <Distro> 2
If WSL is not installed, open PowerShell as Administrator and run wsl --install. Reboot after installation. The default distribution usually installs automatically.
Next, identify the disk containing the Fedora partition. Windows assigns disk numbers, not device paths like /dev/sda. You need the disk number to expose the disk to WSL.
diskpart
# Open the disk management utility
list disk
# Display all physical disks and their sizes
# Identify the disk that matches your Fedora drive size
exit
# Return to the command prompt
Note the disk number. If your Fedora drive is Disk 2, you will use PhysicalDrive2. Do not confuse the disk number with the partition number. WSL exposes the entire disk, and you will select the partition inside WSL.
Expose the disk to the WSL2 virtual machine. This step makes the physical disk available as a block device inside the Linux environment.
wsl --mount \\.\PhysicalDrive2
# Pass the physical disk through to the WSL2 VM
# Replace PhysicalDrive2 with the disk number from diskpart
# This command creates a device node inside WSL, typically /dev/sda
If the command fails with The disk is already mounted, skip this step. The disk is already available. If you see Access is denied, run the command from an Administrator PowerShell prompt.
Now mount the ext4 partition inside WSL. Use the ro flag to mount read-only. This prevents any writes that could damage the filesystem.
wsl mount -t ext4 /dev/sda2 /mnt/fedora -o ro
# Mount the ext4 partition read-only to prevent corruption
# /dev/sda2 is an example; check /dev/sda* for your partition
# /mnt/fedora is the mount point inside the WSL filesystem
# The -o ro flag ensures no writes occur during access
If you are unsure which partition holds the data, list the block devices inside WSL.
lsblk
# Show block devices and their mount points
# Look for the partition with the ext4 filesystem type
# The partition name will appear as /dev/sda1, /dev/sda2, etc.
Unmount the partition when you are done. Leaving a partition mounted can lock the disk and cause issues when you boot back into Fedora.
wsl umount /mnt/fedora
# Unmount the filesystem to release the disk
# Always unmount before switching back to Fedora
# This ensures the disk is not in use by the WSL VM
Unmount before reboot. A locked disk can prevent Fedora from mounting the root filesystem and stop the boot process.
Verify the mount
Check that the partition is accessible and the files are visible. Run these commands inside the WSL terminal.
ls -l /mnt/fedora
# List files and directories to confirm access
# You should see your home directory, /etc, or other Fedora paths
df -h /mnt/fedora
# Show disk usage and mount options
# Verify the mount shows ro in the options column
If the output shows your files and the mount options include ro, the setup is working. You can copy files out of the WSL environment to Windows. Files inside WSL are accessible from Windows Explorer at \\wsl$\Ubuntu\mnt\fedora (replace Ubuntu with your distro name).
Common errors and how to fix them
Errors usually stem from disk locking, permission issues, or dirty filesystems. Address the specific error message rather than guessing.
If you see mount: /dev/sda2: permission denied, you are likely running the command without sufficient privileges. Run the mount command inside WSL with sudo.
sudo mount -t ext4 /dev/sda2 /mnt/fedora -o ro
# Use sudo to gain permission to mount the block device
# WSL may require root privileges for direct disk access
If you encounter mount: /dev/sda2: device is busy, another process has the disk open. Check for existing mounts or other WSL instances using the disk.
mount | grep sda
# List all mounts involving the sda device
# Identify any existing mount points using the partition
umount /mnt/old-point
# Unmount the conflicting mount point before retrying
If the error mentions The filesystem has errors, run fsck, the ext4 journal is dirty. This can happen if Windows hibernated while the disk was in use, or if a previous mount crashed. Do not force mount. Boot into Fedora and run sudo fsck -y /dev/sda2 to repair the filesystem.
# Boot into Fedora and run this command
sudo fsck -y /dev/sda2
# Check and repair the ext4 filesystem
# Replace /dev/sda2 with your actual partition path
# This clears the dirty flag and fixes metadata errors
If wsl --mount fails with The disk is not ready, the disk might be marked as read-only in Windows. Clear the attribute using diskpart.
diskpart
# Open disk management
select disk 2
# Select the disk number
attributes disk clear readonly
# Remove the read-only attribute if present
exit
Run journalctl first. Read the actual error before guessing. The WSL logs often contain the root cause of mount failures.
When to use WSL versus other tools
Choose the method that matches your workflow and risk tolerance.
Use WSL when you need a safe, read-only view of an ext4 partition without installing third-party drivers.
Use a shared exFAT partition when you need to move files back and forth between Fedora and Windows regularly.
Use Ext2Fsd only when you are on an older Windows version that cannot run WSL and you accept the risk of filesystem corruption.
Use ntfs-3g on Fedora when you need to read a Windows NTFS partition from Linux.
Stay on the upstream Workstation if you only deviate from the defaults occasionally.