I've just encrypted my drive with Windows BitLocker. When I open the drive via Windows Explorer it shows me a password field. When I do the same via DOpus I see "An error occurred reading folder..." and nothing else. Is it possible to make DOpus to operate with encrypted drives like Explorer?
Is there an easy way to create a test BitLocker drive without encrypting an entire physical disk/partition?
I tried creating a small TrueCrypt virtual HDD but the "Turn on Bitlocker" option was hidden for it & only seems to appear for my real HDDs.
I think no easy way. Only on real partition. Maybe try on BitLocker to Go with flash drive.
Can anybody confirm?
There might not be anyone reading the forum who uses BitLocker in that way.
Might be worth sending a support request to GPSoftware.
Just tried this and there does seem to be an issue when a drive is used in this manner. Although, I found that when I inserted the drive Windows popped up a dialog asking for the password and if entered then Opus would work fine. If I cancelled this then Opus can't read the folder (as one would expect). There's a work-around though - from the drive context menu (RMB on device in Folder Tree or Drives Toolbar) there's an option to Unlock Drive. If one uses this then all works fine.
We'll look into the issue further now that we know about it!
Was any progress made on this issue. I am running windows 10 and opus 12 with bitlocker drives that require unlocking before access and I am getting the same response. Its not a big issue as I can unlock as above or using explorer, however it would be good to have it seamless in Opus. Thanks
For future info, using Disk Management ("Create and format hard disk partitions"), you can create a virtual disk file (VHD) and mount it as a drive letter. Then you can do whatever you like to it including enable bitlocker etc.
I won't go into the full details but I often use these for testing etc.
Reference: technet.microsoft.com/en-gb/lib ... 52(v=ws.10.aspx
It was fixed for Windows 7 a long time ago, but Microsoft changed the way you unlock Bitlocker drives in Windows 10 (not sure if 8 is the same yet), so it went back to the old behaviour.
Taking a look now, I think we can make it work again for the next update.
Yes, Windows 8 was also affected, and we have fixed both for the next update.