Mount Windows NTFS Partitions Safely on Ubuntu
Last fact-checked: July 2026.
Learn safe ways to access and auto-mount Windows NTFS partitions in Ubuntu using Files, udisksctl, UUIDs and fstab, with BitLocker warnings.
Ubuntu can normally read and write an NTFS data partition without adding a legacy repository or importing a third-party signing key. For occasional access, use the Files app. Configure /etc/fstab only when the same partition must mount automatically at a fixed location on every boot.
Choose the least complicated method
- Use Files for occasional access. It mounts the partition for your user and avoids a permanent system configuration.
- Use
udisksctlwhen you want the same desktop-managed mount from a terminal. - Use
/etc/fstabonly for a fixed mount point needed at boot or by applications. A typing error can delay startup, so back up the file and validate the entry.
These instructions assume an internal NTFS data volume that you are authorized to access. They do not cover repairing NTFS, bypassing encryption, resizing partitions, or installing Ubuntu. Do not experiment on the only copy of important files.
Preflight checks in Windows
Disable Fast Startup for a shared writable volume
Windows Fast Startup saves part of the system state instead of performing a completely fresh shutdown. A dual-boot NTFS volume can therefore appear hibernated to Linux. The safest arrangement for a volume that both systems write is to disable Fast Startup in Windows: open Control Panel, go to Hardware and Sound > Power Options > Choose what the power buttons do, select Change settings that are currently unavailable, clear Turn on fast startup, and save. Then shut Windows down normally.
A one-time full shutdown can be requested from an elevated Windows terminal with shutdown /s /t 0, but it is not a substitute for disabling Fast Startup if you will share the volume regularly. Microsoft's Fast Startup explanation describes how the hybrid shutdown works.
Check BitLocker or Device Encryption
In Windows, open Settings > Privacy & security > Device encryption or search for Manage BitLocker. If the target volume is encrypted, do not assume an ordinary NTFS mount will unlock it. Confirm that your recovery key is backed up before changing encryption settings. The easiest safe option is often to copy the required files from Windows to an unencrypted exchange drive.
If you decide that Ubuntu must access the partition directly, follow the current Ubuntu Desktop documentation for turning off BitLocker in Windows and allow Windows to finish decrypting before returning to Ubuntu. Decryption changes the volume's security and can take time. Do not start it without a backup and a recovery key.
Identify the correct partition in Ubuntu
Open Terminal and run:
lsblk -fLook at FSTYPE, LABEL, UUID, SIZE, and MOUNTPOINTS. An NTFS partition normally shows ntfs or ntfs3. Use the size and label to confirm it; never select a device only because it happens to be called /dev/sda3. Device names can change when drives are added or firmware order changes.
Example output might identify the intended volume as /dev/nvme0n1p4 with UUID 61DB7756DB7779B3. Your values will be different. If you cannot identify the partition confidently, stop.
Method 1: mount with the Files app
- Open Files.
- Under Other Locations or in the left sidebar, select the Windows volume.
- Authenticate if Ubuntu asks.
- Open a small, noncritical text file and save a copy to confirm write access.
- When finished, click the eject/unmount icon beside the volume. Close files and applications using it first.
The desktop normally mounts removable and internal user-selected volumes under /media/$USER/. The exact folder name may follow the volume label. Do not add an fstab entry if this behavior already meets your needs.
Method 2: mount with udisksctl
Use the device path found with lsblk -f:
udisksctl mount --block-device /dev/nvme0n1p4The command prints the mount location. To unmount that one volume after closing files:
udisksctl unmount --block-device /dev/nvme0n1p4This is safer than a blanket command such as umount -a, which attempts to unmount many filesystems and is inappropriate beginner guidance. The Ubuntu udisksctl manual page documents the command.
Method 3: create a careful UUID-based fstab entry
Use this method only if you need a stable location such as /mnt/windows-data. First record your numeric user and group IDs:
id -u
id -gOn a typical first desktop account both are 1000, but use the values shown on your machine. Confirm the UUID again:
lsblk -fInstall Ubuntu's supported NTFS userspace driver only if the ntfs-3g command is missing or your intended configuration requires it. Use Ubuntu's normal repositories, not an old PPA or a repository copied from a blog:
sudo apt update
sudo apt install ntfs-3gCreate the mount point and back up the current configuration:
sudo mkdir -p /mnt/windows-data
sudo cp --preserve=all /etc/fstab /etc/fstab.backup-before-ntfsEdit the file with a terminal editor:
sudo nano /etc/fstabAdd one line, substituting your real UUID, user ID, and group ID:
UUID=61DB7756DB7779B3 /mnt/windows-data ntfs-3g uid=1000,gid=1000,umask=022,windows_names,nofail,x-systemd.device-timeout=10s 0 0What the important fields do:
UUID=...identifies the filesystem more reliably than/dev/sdXY.uidandgidassign visible ownership because NTFS does not use Linux ownership in the same way.umask=022lets the owner write while preventing write access for other local users. Do not useumask=000unless unrestricted local write access is an explicit requirement you understand.windows_namesrejects names Windows cannot use.nofailallows boot to continue if the optional volume is absent.x-systemd.device-timeout=10slimits how long boot waits for the device.- The final
0 0avoids using the Linux boot-time filesystem checker on NTFS.
The Ubuntu fstab manual documents UUID syntax, and the ntfs-3g manual documents NTFS-specific options.
Validate before rebooting
Save the file, then check its syntax:
sudo findmnt --verify --verboseCorrect every error that refers to the new line. If the partition is already mounted through Files, unmount that one volume with its eject icon first. Then test only the new target:
sudo mount /mnt/windows-data
findmnt /mnt/windows-dataCreate and remove a harmless test file as your normal user:
touch /mnt/windows-data/ubuntu-write-test.txt
rm /mnt/windows-data/ubuntu-write-test.txtDo not reboot until the mount succeeds and findmnt shows the expected device. If testing fails, restore the backup:
sudo cp /etc/fstab.backup-before-ntfs /etc/fstabRead-only mounting when you are uncertain
Read-only access is the better choice when you only need to rescue files or when the Windows shutdown state is uncertain. For a temporary test:
sudo mkdir -p /mnt/windows-readonly
sudo mount -t ntfs-3g -o ro /dev/nvme0n1p4 /mnt/windows-readonlyReplace the device path with the one you verified. When finished, close all files and unmount only that mount point:
sudo umount /mnt/windows-readonlyA read-only mount does not fix a hibernated or damaged filesystem. If Ubuntu reports that NTFS is inconsistent, return to Windows, unlock the volume if needed, run Windows' supported disk check, and perform a full shutdown. Do not use a force option to silence the warning.
Troubleshooting without risking the data
- "Volume is hibernated" or "unsafe state": boot Windows, disable Fast Startup, close applications, and shut down fully.
- BitLocker or encrypted volume: stop and use Windows with the recovery information available. Do not paste an encryption key into an unknown command or website.
- Wrong owner: check
id -uandid -g, then correct the matchingfstabvalues. - Boot delay: start from recovery mode or a live USB if necessary, restore the saved
fstab, then validate it again. - I/O errors or disappearing drive: stop writing and back up readable data. Check cables and drive health; mount options cannot repair failing hardware.
The safe default is simple: use Files, keep backups, let Windows close NTFS cleanly, and reserve permanent mounting for a real need.
Comments