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

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

July 30, 2015, 8:26 pm
$
0
0
Anyone else upgraded to windows 10 pro?

I just did and can't access any of my encrypted volumes. They mount, but you can't access them under windows 10.

They're all encrypted partitions, using NTFS.

Image


Things I've tried:

Changed volume key
Changed "header key derivation"

Currently un-encrypting a 3TB HDD, which is showing 27 hours till completion. Ugh.

I have 3 other drives which are 4TB each... So don't want to spend all that time un-encrypting and re-encrypting...

Plus I don't think I can interrupt the un-encryption process without loosing all data...

Meaning I'm stuck waiting for this, even if I wanted to downgrade back to windows 8.1.

Anyhelp would kindly be appreciated. Thanks!

BTW, I also added comments to a similar support thread:
https://veracrypt.codeplex.com/workitem/178
↧
Search

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

July 30, 2015, 8:27 pm
$
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: I've experienced the same problem using VeraCrypt 1.12-BETA on Windows 10 Pro. I have an administrator account with UAC disabled. I tried to create a 200 MB standard volume in NTFS on my desktop folder. VeraCrypt prompted me that it can't create NTFS volume and asked me if I would create a FAT volume instead. But the created volume cannnot be accessible even it has been mounted successfully. I tried to right-click on it and choose format, but it also failed.
↧
↧

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

July 30, 2015, 9:28 pm
$
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: I thought this maybe an UAC issue at first, but after disabling UAC completely using registry hack(EnableLUA=1) and reboot, I also didn't work. Formatting the container, either by VeraCrypt or manually, is always denied by system.
↧

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

July 31, 2015, 3:32 am
$
0
0
Hi,

I just created an account to hear about how well this program works under windows 10. Seems there are some problems here and there.
I would be good to know when this problem will be solved. I dont want to abandon TC and upgrade before these issues remain.

And lastly i want to say thank you for continuing the work after TC.
↧

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

July 31, 2015, 4:59 am
$
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: Hi idrassi, Only windows defender is running on this machine atm, there is no 3rd party virus app. Mounting an NTFS volume as a removable volume doesn't work. I've also tried mounting as a read only volume and also moving the file container to a USB drive and tried mounting it from there... again no joy. Disabling windows defender makes no difference. I've checked the application and system logs, no events show up when either trying to access the volume through file explorer or indeed after the failed NTFS format. I've tried mounting the container on a machine running Win 7 and Win 8.1. In both cases I could access the data with no problems, so I don't think it's a permissions issue. The screenshots do not contain line numbers btw. Screenshots to follow. I'm running 1.12-BETA (64 bit) July, 28th 2015.
↧
↧

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

July 31, 2015, 5:00 am
$
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: I have done further tests on freshly installed Windows 10 machine (Home and Pro): no problem at all, being it opening existing disks or creating new NTFS volumes. The only difference is that in your case you performed an upgrade from a previous Windows version. I suspect that the upgrade process has marked VeraCrypt in a certain way which make it not working with NTFS volumes (very strange...). I will have to perform an upgrade process to try to reproduce. Meanwhile, it is easy to check that VeraCrypt works on freshly installed Windows 10 (confirmed on several machines).
↧

Reopened Unassigned: System Favourites not all mounted during boot [168]

July 31, 2015, 5:34 am
$
0
0
Hello everyone,

I'll explain my situation.
On my laptop I have encrypted the whole system drive (SSD). After that, I also encrypted all the other non-system partitions, added them to the "System Favourites" and gave them a nice display name. I also choose the options that prevents the partitions from being unmounted when the program is not running as an Administrator. Everything works perfectly.

I tried to do the exact same thing to my desktop PC. First I encrypted the whole system drive (SSD) and then encrypted the non-system partitions too. After that I decided to reinstall Windows, so I unencrypted the system drive and left the other drives encrypted.
After reinstalling Windows, I encrypted the system drive again and added all the (previously) encrypted non-system partitions to the "System Favourites", gave them a nice display name and selected the option that prevented them from being dismounted when the program is not being run as an Administrator.

Everything seemed to work fine, but after I restarted my PC, weird things started to happen. For example, the drives are never "hidden" in VeraCrypt, even when the program is not running as an Administrator. (My computer account is an administrator, but that shouldn't make a difference - The "Run as Admin" box is unchecked on the program's .exe file)

![Image](http://i18.servimg.com/u/f18/14/98/02/11/115.png)

Also the partition names do not show up in Explorer, I just get the default display name. Sometimes one of the names shows up, but the others just use the default.
Then there's also another issue, where sometimes none of the System Favourites are mounted, and I have to mount them manually. Or sometimes only 1 of them is actually mounted. But they are never "hidden" in VeraCrypt, they always show up like normal encrypted volumes.

![Image](http://i18.servimg.com/u/f18/14/98/02/11/214.png)

I'd appreciate if anyone could help with this issue.
Thank you very much for your time and help in advance.

Kind regards,

Miniwinkel

P.S. I have to double-check, but I think my system uses UEFI during boot. But if that was the issue, I shouldn't be able to decrypt the system drive during boot at all, right?
P.P.S. Apologies, I think I posted this in the wrong section. Can someone kindly move it for me?
↧

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

July 31, 2015, 5:40 am
$
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: Error Screenshots
↧
Search

Commented Unassigned: System Favourites not all mounted during boot [168]

July 31, 2015, 7:36 am
$
0
0
Hello everyone,

I'll explain my situation.
On my laptop I have encrypted the whole system drive (SSD). After that, I also encrypted all the other non-system partitions, added them to the "System Favourites" and gave them a nice display name. I also choose the options that prevents the partitions from being unmounted when the program is not running as an Administrator. Everything works perfectly.

I tried to do the exact same thing to my desktop PC. First I encrypted the whole system drive (SSD) and then encrypted the non-system partitions too. After that I decided to reinstall Windows, so I unencrypted the system drive and left the other drives encrypted.
After reinstalling Windows, I encrypted the system drive again and added all the (previously) encrypted non-system partitions to the "System Favourites", gave them a nice display name and selected the option that prevented them from being dismounted when the program is not being run as an Administrator.

Everything seemed to work fine, but after I restarted my PC, weird things started to happen. For example, the drives are never "hidden" in VeraCrypt, even when the program is not running as an Administrator. (My computer account is an administrator, but that shouldn't make a difference - The "Run as Admin" box is unchecked on the program's .exe file)

![Image](http://i18.servimg.com/u/f18/14/98/02/11/115.png)

Also the partition names do not show up in Explorer, I just get the default display name. Sometimes one of the names shows up, but the others just use the default.
Then there's also another issue, where sometimes none of the System Favourites are mounted, and I have to mount them manually. Or sometimes only 1 of them is actually mounted. But they are never "hidden" in VeraCrypt, they always show up like normal encrypted volumes.

![Image](http://i18.servimg.com/u/f18/14/98/02/11/214.png)

I'd appreciate if anyone could help with this issue.
Thank you very much for your time and help in advance.

Kind regards,

Miniwinkel

P.S. I have to double-check, but I think my system uses UEFI during boot. But if that was the issue, I shouldn't be able to decrypt the system drive during boot at all, right?
P.P.S. Apologies, I think I posted this in the wrong section. Can someone kindly move it for me?
Comments: Hi, I'm afraid I'm not sure I understand completely your last message: does the system favorite fail to mount on Windows 8 with the the 1.12-BETA? Or are you talking about the labels? If you are talking about the labels, can you please create a new issues with this one title if for failure to mount at startup. Thanks.
↧
↧

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

July 31, 2015, 8:11 am
$
0
0
I have done further tests on freshly installed Windows 10 machine (Home and Pro): no problem at all, being it opening existing disks or creating new NTFS volumes.

The only difference is that in your case you performed an upgrade from a previous Windows version. I suspect that the upgrade process has marked VeraCrypt in a certain way which make it not working with NTFS volumes (very strange...).

I will have to perform an upgrade process to try to reproduce. Meanwhile, it is easy to check that VeraCrypt works on freshly installed Windows 10 (confirmed on several machines).

Further exchanges on the issue tracker: https://veracrypt.codeplex.com/workitem/177
↧

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

July 31, 2015, 4:39 pm
$
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: I tested using a disk (NTFS) encrypted using VeraCrypt 1.0e on a Windows 8.1 Enterprise 64-bit: Disk works as expected on Windows 10 Pro and Windows 10 Home (Windows 8.1 Enterprise includes all features of Windows 8.1 Pro). The fact that the partition was converted from TrueCrypt has no effect since it only changes the key derivation and not the layout or content. A good test would be to connect your disk to another Windows 10 machine, preferably a clean install. If you don't have access to such machine, you can just install Windows 10 on VirtualBox for example and mount the disk on the VM (Windows 10 Enterprise is free for 90-days without needing a serial).
↧

New Post: Error: incorrect password/PRF or not a valid volume

July 31, 2015, 5:10 pm
$
0
0
With some extra help from another set of eyes, I was able to get into my files. Thank you for your assistance!

Nicole M. Meyer, Pharm.D.
Goodrich Pharmacy Resident
601 Jacob Lane
Anoka, MN 55303
(763) 421-5540

↧

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

July 31, 2015, 6:28 pm
$
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: @idrassi that's good to know about the clean install of Windows 10 working. I was planning on doing that regardless, but did the [upgrade first as instructed at slickdeals](http://slickdeals.net/f/8010191-windows-10-official-download-tool-upgrade-or-create-installation-media-usb-or-dvd-or-iso-file?v=1). Here's info from slickdeals: > While running Windows 7/8, you must first run setup.exe on the newly created Windows 10 media. > (If you simply boot from the newly created Windows 10 media, it would NOT accept your Windows 7/8 key.) > After non-clean install, you can THEN do clean reintall. During reinstall, select the Skip button at the product key page.
↧
↧

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

August 1, 2015, 12:49 am
$
0
0
VeraCrypt not auto starting when open your session on Windows 10

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
"VeraCrypt"="\"C:\Program Files\VeraCrypt\VeraCrypt.exe\" /q preferences /a logon /a favorites"

1.12-BETA

TC 7.1a is auto starting
↧

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

August 1, 2015, 1:59 am
$
0
0
By reading the content of your registry, this seems to be a configuration issue from your side: VeraCrypt will try to mount any configured favorite volumes and it will quit right after (notice the /q) unless the option "Start VeraCrypt Background task" is checked in the preferences. So, judging by your report, it is clear that you either:
  • forgot to check this option.
  • you didn't configure VeraCrypt favorites to mount at startup.
Since VeraCrypt kept the same TrueCrypt logic, if you go to TrueCrypt, you'll see that you either have checked the background task option or you have at least one TrueCrypt favorite configured to mount at logon. Most probably you have a TrueCrypt favorite volume set to mount at startup.

Thus, to have the same behavior as TrueCrypt, just use VeraCrypt like TrueCrypt and add a favorite volume to VeraCrypt that is configured to mount at startup.

Voilà voilà...actually many TrueCrypt users compare between VeraCrypt and TrueCrypt without putting them both in the same configurations, so it is normal to have different behavior!
↧
Search

New Post: Laptop is not booting with newest beta

August 1, 2015, 4:25 am
↧

New Post: Laptop is not booting with newest beta

August 1, 2015, 4:26 am
$
0
0
msberlin wrote:
Thanks, I will try it in the evening. But the "1" in the german layout ist the same as in the us layout ? What will happen, if the pw is not correct ? error message ?

Edit: I forgot to say, that I put in a fake message in connection with "Do not show any texts...", maybe interesting ?
Any new idea to my questions an problem ? ;-)

Thanks !
↧
↧

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

August 1, 2015, 4:49 am
$
0
0
Hey Brett,

Can you share you changes with us/me if you manage to compile things correctly?
↧

New Post: Security hole in newer Windows versions

August 1, 2015, 7:57 am
↧

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

August 1, 2015, 8:19 am
$
0
0
That's not the case, in VC prefs VC background task is enabled, start VC background task disabled
Favorite volume has flag mount on logon set.
Same in TC prefs (enabled.disabled)
↧
Viewing all 7620 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>