Before posting, and to avoid disappointment, please read the following:
- This forum is not for 2BrightSparks to provide technical support. It's primarily for users to help other users. Do not expect 2BrightSparks to answer any question posted to this forum.
- If you find a bug in any of our software, please submit a support ticket. It does not matter if you are using our freeware, a beta version or you haven't yet purchased the software. We want to know about any and all bugs so we can fix them as soon as possible. We usually need more information and details from you to reproduce bugs and that is better done via a support ticket and not this forum.
For technical support visit https://support.2brightsparks.com/
2 posts • Page 1 of 1
- Posts: 6
- Joined: Wed Dec 19, 2007 6:50 am
I'm using 10.2.88.0, and I've recently needed to recreate my profiles that backup to Bitlockered VHDX files, which I created in v8 or v9. In v10, because they're Bitlockered, I had to assign them a drive letter in SBP settings when I created the new profiles. After I run these profiles, double-clicking the files in File Explorer gives the error message "Couldn’t Mount File : The disk image isn't initialized, contains partitions that aren't recognizable, or contains volumes that haven't been assigned drive letters. Please use the Disk Management snap-in to make sure that the disk, partitions, and volumes are in a usable state." This happens even if I've assigned them the same or different drive letters in Disk Management than I used in SBP. Thus, after I've run my SBP profiles, I have to visit Disk Management and assign drive letters again to be able to mount them in File Explorer, and this will all be undone the next time I run the profiles. This did not happen with my old profiles created in earlier versions using these same VHDX files, not even after running them in v10. This is happening only with the new profiles I just created in v10. Any ideas?
- Posts: 6
- Joined: Wed Aug 23, 2023 7:42 am
I used to have the same issue. Then, this issue was solved after I used encryption at the file/folder level instead of whole-disk encryption via BitLocker. That way Syncovery can backup directly without needing to mount/assign drives first. You can try my method