Win10 Sharing of VeraCrypt problems

Open source disk encryption with strong security for the Paranoid

Brought to you by: idrassi

Win10 Sharing of VeraCrypt problems

Forum: Technical Topics

Creator: S. Wanex

Created: 2015-08-09

Updated: 2023-04-02

S. Wanex - 2015-08-09

The problem seems to be with drives that are “created” by VeraCrypt. Windows 7 handles them as any other drive, where Windows 10 seems to handle them but denies network access to them, giving a don't have permission error.

Win10 can access Win7 VeraCrpt files. Win7 cannot access VeraCrypt files on win10.

Any clue how I might resolve this problem?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mounir IDRASSI - 2015-08-09

Thank you for reporting this.

Windows 10 must be querying VeraCrypt volume for some extra properties that are not recognized by VeraCrypt driver and this may explain the remote access failure.

There was a similar report on Codeplex concerning this (https://veracrypt.codeplex.com/discussions/642388#post1437901).
Like the post above, I would like to ask you two things:

Can you please check the Event Viewer on the Windows 10 machine and look for any event that occur the same time as someone is trying to access the shared folder from an other machine? Probably you'll find an entry that can explain the cause of this access error.

I have just released VeraCrypt 1.13 in order to solve a compatibility issue with Tor Browser. Can you please install this new version just to be sure that this doesn't come from the same issue corrected in 1.13?

Thanks in advance for your help to understand this issue.

Last edit: Mounir IDRASSI 2015-08-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Scott - 2015-08-23
  
  I am attempting to access veracrypt file on a Win10 machine on my LAN from Win7 machines and am getting a no permission to access sharing error. I just upgraded to version 1.13 but the error still exists.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

S. Wanex - 2015-08-25

I'm hoping that this Win10 problem can be resolved! Since I only have one machine on Win10, I can't verify if win10 can communite with win10 over the lan to a veracrytp file. Win10 has enough problems and security issues to make me strongly consider moving to linux.

I do see that there is a veracrypt package for linux. Is there a list distros that are known to work with veracrypt?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mounir IDRASSI - 2015-09-06

As discovered in the Codeplex thread, this issue appears only when the volume is mounted as removable media.
Sharing a VeraCrypt volume that is mounted as normal disk (option "mount as removable media" not checked), works as expected.

Windows 10 must have be requiering removable media shared over network to support some specific properties not implemented by VeraCrypt. Some time is needed to indentify what is missing.

Meanwhile, to avoid such issue when sharing volumes over the network, avoid mounting such volumes as removable media.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

DaMaxx - 2015-09-23

I found myself with the same problem on Windows 8.1 x64. Remove the mark 'mount as removable media' fixed it. So it seems the problem started with Windows 8.1?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Michael - 2023-04-02

Did a solution to this ever get found? I'm hitting it as well.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.