. Thank you again for continuing to support me!
I'll try your order of formatting next. Let me report what I did last night and see if that'd shed any light as this time I went super clean.
I'm suspecting it has something to do with "Mount selected volume as removable medium" option. Or something else that's VeraCrypt specific.
New Win10Pro on my test laptop (t61 takes a while to install). The only thing I selected during the install was the mandatory time zone, login with my
(same as my other Win10Pro PC, I don't keep a second HoTMaiL account anymore). I left the internal C: untouched with NTFS, the way Win10Pro clean installs. partitions it and formats it.
For the test, created a folder C:\Shared_C. Shared it by right mouse clicking on it: Share with-->Specific People->Share. Just those 3 clicks. I didn't have to select anything as my
was preselected (the only ID on that new machine) and it was already with a permission of Owner.
Went to my other PC where I was logged in already with the same
hit F5 to refresh the Network, saw \Shared_C, got in, copied a few files, painless setup to share a folder with 3 clicks. (I might give up Ubuntu one day, who knows).
Next, I connected to the laptop 2 USB drives (old WD, 1 TB and 500 GB).
First, the 1TB - partitioned and formatted with Win10 as NTFS and mounted as L. I created a folder Shared_L on it. Same 3 clicks and shared it. Back from my other PC, I could see Shared_L, copy files into it, delete them. Concluded that it's not a network or
a Windows permissions issue, or that I'm using an external HD vs the internal one.
Repeated it on the 500GB - again, partitioned and formatted with Win10 as NTFS and mounted as V. Similarly created Shared_V, same 3 clicks, everything works. I can see it remotely, copy, delete, etc.
Next, I let Win10 encrypt L: with BitLocker. Left the process crunch overnight.
Similarly, I followed VeraCrypt's wizard and let it encrypt V: overnight.
Both steps had completed by this evening. I added V: to VeraCrypt's Favorites to make it easy to mount and selected only "Mount selected volume as removable medium".
Went back to my other PC and felt no difference on Shared_L. My files were still there, I could still copy more, delete, etc. If it wasn't my PC, I would have not know that it was now BitLocker encrypted, or an external disk.
Clicked on Shared_V and immediately got "Windows cannot access \t61\Shared_V".
After lots of playing with this and that, quite a few reboots, connecting and disconnecting the external drives I got lucky!
I had rebooted the box and changed the options under VC's Favorites to have nothing selected, i.e. I un-checked the "Mount selected volume as removable medium". I hit Mount Favorite Volumes and that did the trick - I could see the files remotely again!!!
Now, the question is WHY?
I am sure I used to use that same setup with TrueCrypt (well, it was WinXP and Win7 back then) and the only issue I had found was that I had to go and share the folder every time I rebooted the box as TrueCrypt/Win7 somehow were forgetting the share (not an
issue as I had a .bat file to run a few net use commands to share them again).
There was no difference if I was mounting the truecrypt-ed drives as removable medium or not, if they were internal drives or external... at least I don't recall one.
I do prefer to mount removable disks as removable to reduce corruption when the PC crashes or the kids unplug it, or we just have a power outage.
Any chance you could confirm my theory and see if there's a fix?
Thank you again!