Quantcast
Channel: VeraCrypt
Viewing all 7620 articles
Browse latest View live

New Post: Not actually auto mounting on Windows 10 (+long mount times)

$
0
0
humm...weird...and you don't get the password prompt upon logon? You favorite don't get mounted or they get mounted by VeraCrypt exits afterwards?

This is the simplest configuration and it works for me and others on Windows 10. This is the basic test that we all do to check if VeraCrypt works (favorite mounting, both normal and system).

Thus, there must be another cause. First thing is to check Windows Events Viewer to see if there is any error (both on System and Application) that would explain this.
Second, try running the same the command line from a command prompt and check if you get the password prompt: "C:\Program Files\VeraCrypt\VeraCrypt.exe\" /q preferences /a logon /a favorites

Third thing, verify if you have any software on your machine that can block VeraCrypt from auto-running at startup: some security software offer such functionality and they may falsely target VeraCrypt binaries.

Anyway, I have done a test on a Windows 10 Pro with an encrypted USB key that uses only a keyfile (no password). I recorded a video that demonstrates how to set this encrypted USB key to mount automatically at startup without typing any password. Here is the link to the video: https://www.youtube.com/watch?v=gbJKUEUXWVo

As you can see, it works as expected. That's why I said there is something else involved in your case.

New Post: Embed the PIM into the volume header so it doesn't need to be typed in

Commented Unassigned: Cannot access any encrypted file containers after Windows 10 upgrade [177]

$
0
0

My machine was upgraded to Win 10 yesterday.
The containers appear to mount correctly, but when trying to open them in file explorer I get the following error:
Location is not available
G:\ is not accessible.
Incorrect Function.

I have tried the following so far:
Chkdsk appears to work ok, the OS can see the drive.
Uninstalling veracrypt stable and reinstalling the latest veracrypt beta / Reboot.
Creating an encrypted small test file container from within Windows 10 - Same issue.
Attempting to access the drive via the command prompt.
Enabling/Disabling mount as removable drive.
Checking disk management - Not sure if veracrypt volumes usually show up here, but there are no entries there atm.
I've had a quick look at the event viewer and couldn't see anything obviously related.
I have tried mounting external hard disks and other USB drives with no issue.

All my project source code is contained in these volumes, so I'd like to get up and working again asap.

Any ideas anyone?


Comments: BOOM! figured it... The problem has to do with Apple Bootcamp drivers.... Followed directions here: https://discussions.apple.com/thread/7140688 1. Run [Sysinternals Autoruns](https://technet.microsoft.com/en-us/sysinternals/bb963902.aspx?f=255&MSPPError=-2147217396) "Autoruns.exe" as administrator. 2. Search for: apple 3. uncheck Apple HFS 4. Done. Reboot... ***************** Other note: I also went into add/remove software and selected "repair" for Apple bootcamp... Not sure if that did anything... I only installed bootcamp to get Apple Keyboard and Apple Thunderbolt display drivers working... There's also a note saying to install the latest bootcamp version--this may also fix the problem; not sure since I haven't tested that....

New Post: Not actually auto mounting on Windows 10 (+long mount times)

$
0
0
Is the current problem tukan is experiencing due to Apple bootcamp?

Forum member duntuk made the following discovery for his system in the issue "Cannot access any encrypted file containers after Windows 10 upgrade".

duntuk wrote:
The problem has to do with Apple Bootcamp drivers....

Followed directions here:
https://discussions.apple.com/thread/7140688
  1. Run Sysinternals Autoruns "Autoruns.exe" as administrator.
  2. Search for: apple
  3. uncheck Apple HFS
  4. Done. Reboot...
Other note: I also went into add/remove software and selected "repair" for Apple bootcamp... Not sure if that did anything...

I only installed bootcamp to get Apple Keyboard and Apple Thunderbolt display drivers working...

There's also a note saying to install the latest bootcamp version--this may also fix the problem; not sure since I haven't tested that....

New Post: Not actually auto mounting on Windows 10 (+EFS incompatibility)

$
0
0
No that's apparently not same case. If I read the topic the problem there is about not accessing once mounted volume, problem here is not automountning volumes using encrypted keyfiles. Once my volumes are mounted in VC/TC manually later they expose no problems (edit: they can't handle NTFS encrypted files as written below). Also I don't have installed Paragon HFS on Windows 10.
There must be something very weird with file system or files security in Windows 10.
I unencrypted both keyfiles, after restart
TC 's keyfile seems no more been altered during restart (TC was able automount correctly)
VeraCrypt still not auto starting (or it autostarts but due some problem it dies silently). Does it provide some logging? This is very weird and I need to know what's happening.
More observations: test volumes can mount, still long mount times, trying to copy my encrypted keyfile on NTFS of them I get error Incorrect function. This sounds similar to error described in the other thread. In summary

copy encrypted keyfile -> VC volume (NTFS) => Incorrect function
copy unencrypted keyfile -> VC volume (NTFS) => OK
copy encrypted keyfile -> VC volume (FAT) => OK
copy unencrypted keyfile -> VC volume (FAT) => OK
copy encrypted keyfile -> TC volume (NTFS) => Incorrect function
copy unencrypted keyfile -> TC volume (NTFS) => OK
copy encrypted keyfile -> local regular volume (FAT or NTFS) => OK
copy unencrypted keyfile -> local regular volume (FAT or NTFS) => OK

Furthermore copying unencrypted file to VC or TC NTFS volume and set it encrypted then succeeds but trying to access it results again in Incorrect function error. In short there seems to be some incompatibility between TC/VC NTFS encryption and Windows 10 NTFS encryption. Disk info shows me system drive NTFS version still 3.01. All the Windows 10 filesystem is very weird, In encrypted private folder setting/unsetting encrypted attribute for .bat files results in access denied error while I still can edit/delete them and can still change encryption for other files, WTF?
Using same personal certificates as on Windows 8, and can copy encrypted files between Windows 10 ↔ Windows 8 local drives also

New Post: Not actually auto mounting on Windows 10 (+EFS incompatibility)

$
0
0
Can someone confirm problem of NTFS encrypted files transferability between VC and regular volume, or is only appearing on my PC?

New Post: Embed the PIM into the volume header so it doesn't need to be typed in

$
0
0
It's possible to turn off the need for driver signing in x64 Windows (x86 Windows doesn't need signed drivers).

Turn OFF signed drivers:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON

Turn ON signed drivers:
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF

Of course, it's better to keep this on out of security view point, but when push comes to shove this is possible.

Commented Unassigned: Cannot access any encrypted file containers after Windows 10 upgrade [177]

$
0
0

My machine was upgraded to Win 10 yesterday.
The containers appear to mount correctly, but when trying to open them in file explorer I get the following error:
Location is not available
G:\ is not accessible.
Incorrect Function.

I have tried the following so far:
Chkdsk appears to work ok, the OS can see the drive.
Uninstalling veracrypt stable and reinstalling the latest veracrypt beta / Reboot.
Creating an encrypted small test file container from within Windows 10 - Same issue.
Attempting to access the drive via the command prompt.
Enabling/Disabling mount as removable drive.
Checking disk management - Not sure if veracrypt volumes usually show up here, but there are no entries there atm.
I've had a quick look at the event viewer and couldn't see anything obviously related.
I have tried mounting external hard disks and other USB drives with no issue.

All my project source code is contained in these volumes, so I'd like to get up and working again asap.

Any ideas anyone?


Comments: Exactly, it worked for me. The SD card sometimes stop working but probably this is the Windows 10 driver...

Commented Unassigned: Cannot access any encrypted file containers after Windows 10 upgrade [177]

$
0
0

My machine was upgraded to Win 10 yesterday.
The containers appear to mount correctly, but when trying to open them in file explorer I get the following error:
Location is not available
G:\ is not accessible.
Incorrect Function.

I have tried the following so far:
Chkdsk appears to work ok, the OS can see the drive.
Uninstalling veracrypt stable and reinstalling the latest veracrypt beta / Reboot.
Creating an encrypted small test file container from within Windows 10 - Same issue.
Attempting to access the drive via the command prompt.
Enabling/Disabling mount as removable drive.
Checking disk management - Not sure if veracrypt volumes usually show up here, but there are no entries there atm.
I've had a quick look at the event viewer and couldn't see anything obviously related.
I have tried mounting external hard disks and other USB drives with no issue.

All my project source code is contained in these volumes, so I'd like to get up and working again asap.

Any ideas anyone?


Comments: Just to confirm this worked for me too, although I can no longer access my Mac partition from Windows. Hopefully Apple will release updated drivers or the VC team can find a workaround. Thanks for all the help and info folks.

New Post: Can't access drives after Windows 8.1 Pro upgrade to Windows 10 Pro

$
0
0
Thanks for confirming idrassi, will try it in a day or two myself. Cheers.
I have a clean install now and will be moving from TC to this since you are updating the program and it just feels better to know the support is there incase :)

Commented Unassigned: Cannot access any encrypted file containers after Windows 10 upgrade [177]

$
0
0

My machine was upgraded to Win 10 yesterday.
The containers appear to mount correctly, but when trying to open them in file explorer I get the following error:
Location is not available
G:\ is not accessible.
Incorrect Function.

I have tried the following so far:
Chkdsk appears to work ok, the OS can see the drive.
Uninstalling veracrypt stable and reinstalling the latest veracrypt beta / Reboot.
Creating an encrypted small test file container from within Windows 10 - Same issue.
Attempting to access the drive via the command prompt.
Enabling/Disabling mount as removable drive.
Checking disk management - Not sure if veracrypt volumes usually show up here, but there are no entries there atm.
I've had a quick look at the event viewer and couldn't see anything obviously related.
I have tried mounting external hard disks and other USB drives with no issue.

All my project source code is contained in these volumes, so I'd like to get up and working again asap.

Any ideas anyone?


Comments: @duntuk: Thank you very much for your efforts and for discovering the origin of the issue. This is a very helpful information and I posted it to Twitter: https://twitter.com/VeraCrypt_IDRIX/status/627794019830104064 It will difficult to find a workaround for such issues. This would need reproducing the issue here and then doing some low level system debugging to try understand why Apple drivers are causing issues and try to see if something can be done to workaround it. This is tedious task and there are currently no resources to invest on investigating it especially that there is no guarantee a workaround exists. It is easier for Apple engineers to fix their driver which will also solve other Windows 10 issues.

Edited Unassigned: Cannot access any encrypted file containers after Windows 10 upgrade [177]

$
0
0

My machine was upgraded to Win 10 yesterday.
The containers appear to mount correctly, but when trying to open them in file explorer I get the following error:
Location is not available
G:\ is not accessible.
Incorrect Function.

I have tried the following so far:
Chkdsk appears to work ok, the OS can see the drive.
Uninstalling veracrypt stable and reinstalling the latest veracrypt beta / Reboot.
Creating an encrypted small test file container from within Windows 10 - Same issue.
Attempting to access the drive via the command prompt.
Enabling/Disabling mount as removable drive.
Checking disk management - Not sure if veracrypt volumes usually show up here, but there are no entries there atm.
I've had a quick look at the event viewer and couldn't see anything obviously related.
I have tried mounting external hard disks and other USB drives with no issue.

All my project source code is contained in these volumes, so I'd like to get up and working again asap.

Any ideas anyone?


New Post: Can't access drives after Windows 8.1 Pro upgrade to Windows 10 Pro

New Post: Decrypt system partition before formatting it?

$
0
0
Hey Guys,

I have encrypted my system fully with Veracrypt.
Now I want to format my whole system.

I am not sure whether I have to Decrypt the system (where my OS is installed) first, before I can format it and install a new OS.

Or is it possible to format the whole system (and lose encryption) and install a new OS without decrypt it first?

New Post: Recover Deleted VeraCrypt Volume

$
0
0
I've got an interesting data recovery case I'm looking at for someone. Client accidentally deleted a Veracrypt container from their HDD and wants to recover it. The password is known.

I realize VeraCrypt doesn't have any identifiable file signatures, so it can't be found using file caving like other file types. However I'm wondering if given that the password is known there's a way to recover the file. Perhaps by encrypting the entire dive using the same password, and then scanning for files... I don't know. Or does it use a random key in conjunction with the pass (I assume it does).

Any ideas?

New Post: Embed the PIM into the volume header so it doesn't need to be typed in

$
0
0
SHBouwhuis wrote:
It's possible to turn off the need for driver signing in x64 Windows (x86 Windows doesn't need signed drivers).

Turn OFF signed drivers:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON

Turn ON signed drivers:
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF

Of course, it's better to keep this on out of security view point, but when push comes to shove this is possible.
Thanks. I was aware Windows allowed for unsigned drivers (it makes developing & testing them easier) but for an end-user that isn't really a good choice. ninveh's method may work out best.

New Post: Sourceforge isn't trustworthy any more

$
0
0
Hi,

I'm aware of the Sourceforge story. They did a stupid move by changing the installers of some unmaintained projects.
As for VeraCrypt they never touched the binaries and they will never do for a simple reasons: All VeraCrypt binaries are PGP signed and more importantly, the Windows binary has an embedded digital signature that is automatically checked by Windows.

Moreover, Sourceforge only modified unsigned installers for unmaintained projects and afterwards they backtracked, so I don't see any issue for the future.

If you want to avoid Sourceforge, you can use Codeplex as it contains exactly the same binaries.

Sourceforge provides a wonderful hosting infrastructure that is not equaled anywhere else in the free open source hosting offering. If you want to want to have the same download quality (they have multiple mirrors across the glob) and statistic services they provide, you'll have to pay extra cash or your need to be sponsored by some business. I suspect that there are some entities that want to profit from this Sourceforge mistake in order to take them down and thus force many projects to pay extra money for services that are free with Sourceforge.

In all cases, no matter what download source you are using, always check the signature of the files as described here: https://veracrypt.codeplex.com/wikipage?title=Digital%20Signatures

New Post: Recover Deleted VeraCrypt Volume

$
0
0
Try Google searching "deleted truecrypt file container" for ideas. It appears recovering a file container is difficult task.

I would recommend clone the drive using two target drives and perform all of your repair attempts on the one clone. This will allow you to start over by cloning the untouched clone drive to the other clone drive used for recovery.

New Post: Recover Deleted VeraCrypt Volume

$
0
0
We are a professional data recovery lab (www.data-medics.com) so don't need the general advice about data recovery. Thanks!

I was hoping for some more specific details about VeraCrypt as I'm not familiar with it. Is it built on the same basic architecture as Truecrypt? Does it use a randomly generated key stored in the container that is re-encrypted using the password? Is this key stored at the beginning or end of the file? Things like this. I'm just trying to figure out if there's even a possibility of working up a solution to find the lost file.

New Post: Restrict number of password attempts

$
0
0
I just wanted to say thank you for a detailed reply. I am completely new to these ideas and I really appreciate the information.

I understand that we can't store a counter between sessions and every reboot would reset the counter back to 0. For my situation that would be good enough. It would put my mind at ease if there was some random theft. The most probable situation is they have a couple of password attempts, have no success and they throw out the hard drive as the header keys (and maybe the drive itself) have been wiped.

I also understand the problem you mentioned about plausible deniability. This is not an issue I would face and I would have no idea how to overcome that issue which makes it hard if compromises a feature people use.

I don't know if maybe the password counter feature could only be enabled if the user selects it when creating a system disk or container. That way people like me have the option to activate the feature and people who want plausible deniability could not activate the feature. Just an idea but not sure if something like that could be possible.
Viewing all 7620 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>