You cannot add a mounted disc or network share directly as the destination for Windows 11 File History because the feature is designed exclusively for local fixed drives. To back up to a mounted volume, you must either use a different backup tool that supports dynamic disks or map the network location to a local folder and include that folder in your selection.
Understanding File History Limitations
Windows 11 File History is a robust tool for protecting personal files, but it has strict requirements regarding its target storage. The system looks for a drive that appears as a "Local Disk" with a stable drive letter and sufficient free space. When you mount a disc, such as a physical DVD/Blu-ray drive or a virtual optical image, or when you connect a network share via SMB, these do not meet the criteria for a File History destination. The primary reason for this restriction is reliability. File History relies on continuous background indexing and shadow copy creation. Network connections are intermittent, and optical media is write-once or limited-write. If File History attempted to write to a network share, a dropped connection could corrupt the entire backup repository. Similarly, mounted discs often have changing availability states that would break the consistency of the backup chain. If you attempt to select a mapped network drive (like Z:) in the File History settings, you will likely find it grayed out or simply unavailable in the dropdown menu. This is by design. Microsoft explicitly states that File History requires a local hard drive or SSD. While some users might try to force this via registry edits or Group Policies, such actions are unsupported and can lead to data loss. As discussed in File History in Windows 11: How to Backup and Restore Your Files, the standard procedure always involves selecting a physical internal or external USB drive.Why Mounted Drives Are Excluded
A "mounted disc" can refer to two different things in Windows: 1. Optical Media: Physical CD/DVD drives. These are read-only or append-only for most user operations and lack the random write speeds required for incremental backups. 2. Virtual Mounts: ISO files mounted as virtual drives. These are temporary session-based mounts that disappear upon reboot. File History needs persistent storage that survives restarts. In both cases, the drive letter may exist, but the underlying file system behavior does not support the transactional logging that File History uses to track changes efficiently.Workarounds for Non-Local Storage
Since you cannot point File History directly at a mounted disc or network share, you need alternative strategies to achieve your goal of backing up data to those locations. Here are the most effective methods.Method 1: Use Folder Backup Instead
If you want to back up specific folders to a network location or a mounted drive, Windows 11 offers a simpler alternative called "Folder Backup." This is not the same as the full File History service, but it achieves similar results for specific directories. 1. Open Settings. 2. Navigate to System > Storage. 3. Click on Backup (or Advanced storage settings depending on your build). 4. Select Back up using File History if available, or look for OneDrive integration. 5. For direct folder syncing, consider using OneDrive's "Backup" feature which allows you to sync Documents, Pictures, and Desktop folders to the cloud, which can then be synced locally to other devices. However, for true local-to-local backups where you control the destination, third-party tools are superior.Method 2: Third-Party Backup Software
Many professional backup applications support mounting volumes, network shares, and encrypted drives. If you are using an encrypted drive like VeraCrypt, you must mount it first, then point the backup software to the mounted drive letter. For example, if you are using Acronis True Image, you can easily configure it to back up to a SanDisk SSD or a network share. See How to Properly Backup Your Windows 11 PC to a SanDisk Extreme Portable SSD Using Acronis True Image for guidance on setting up flexible destinations. These tools handle the complexity of disconnected drives and retry logic automatically.Method 3: Map Network Drive and Use Robocopy
For advanced users who want a lightweight solution without installing heavy software, you can use the command-line toolrobocopy. This allows you to mirror folders to a network share or a mounted drive manually.
1. Map your network drive or mount your disc so it has a drive letter (e.g., Z:).
2. Open Command Prompt as Administrator.
3. Run a command like:
robocopy C:\Users\YourName\Documents Z:\Backup /MIR /XOCommon Troubleshooting Steps
If you are still experiencing issues with backup destinations, check the following:- Drive Letter Conflicts: Ensure your mounted disc has a unique drive letter that doesn't conflict with existing partitions.
- Permissions: Verify that your user account has Full Control permissions over the mounted drive or network share.
- File System Format: File History requires NTFS. If your mounted disc is formatted as FAT32 or exFAT, it will not work. Reformat the drive to NTFS if possible.
- Connection Stability: For network shares, ensure the connection is persistent. Use a static IP for the server and ensure the share is set to reconnect at login.