Background: I am running Windows 10 Pro 1709. My C: drive is encrypted with BitLocker. I have an ASUS RT-AC55U with an 8TB HDD attached to its USB 3.0 port. My goal is to use part of that HDD as an encrypted space for my backups—i.e., mine will be the only PC with the container mounted—while allowing the rest of the HDD to be accessible to other users on the network. To that end, I created a large VeraCrypt NTFS container on the network-attached HDD: Now I have mounted that container as the lettered drive B: and added some files from another source: I am trying to use File History and System Image Backup with the drive B:.

Problem: I can point File History at B:, but it will stop backing up my C: drive very shortly into the process. Subsequently, it will warn me that my data is not yet backed up while showing that the backup is a few GB in size:

Further attempts to run File History do not increase the backup size nor make the warning go away. Additionally, when I go to perform a system-image backup, the tool does not even list B: as a possible target, giving STATUS_WAIT_1 (0x80070001):

Things I've tried: Using a VeraCrypt container of a different format (doesn't work), backing up to an unencrypted external HDD (works but doesn't fit my needs), BitLocker-unencrypting my C: drive (makes no difference), plugging the HDD directly into my computer instead of going over the network (makes no difference), using a smaller container (makes no difference).

While I hope for a solution to this specific problem, I'd be happy to entertain answers that discuss alternate ways of meeting my goals.

  • Please understand that 1. once decrypted a VC container behaves like any other drive and 2. it isn't "designed" to work over the network (it may work but if it does it will always be problematic. Knowing this please edit and describe the problem you're having when directly connected. It isn't clear, at all, what you're actually complaining about.
    – user772515
    Apr 24, 2018 at 1:56
  • @MichaelBay: Can you elaborate on why VC will be problematic over the network? The help strongly implies that this shouldn't be a problem. I've added more detail.
    – user746633
    Apr 24, 2018 at 2:39
  • No need to elaborate, just read the last paragraph. Also keep in mind the information you linked implicitly assumes a proper network configuration in a professional environment. It isn't applicable to (and the authors didn't even consider) a home router USB connected drive. Re: why it refuses to backup when locally connected and mounted I cannot help you. If you can read/write the container reliably using a file manager there's no reason for it not to work with the backup tool.
    – user772515
    Apr 24, 2018 at 2:51
  • Did you ever find a solution to this?
    – Rob Rose
    Aug 2, 2018 at 21:04
  • No, I didn't. Still interested, though.
    – user746633
    Aug 2, 2018 at 22:54


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy