Jofifi

The issue is still not resolved, but I found a workaround which tells me total size and free size: Open Powershell with administrative privilegis, enter (replace "m :" with your volume): fsutil volume diskfree m: This tells me the total size and the free size of the volume, fast and easy :-)

Thanks for sharing the solution. I have one question left: Did VC give an error message in your case? Because I can compare it to faulty USB devices (broken cable or similar) with VC encrypted partition on it: In this case, Windows shortly looses the connection to the USB drive involuntarily, and VC brings instantly a big error message that disconnecting without VC-dismounting can result in data loss.

This is really strange. I suppose it can't be caused by VC or Truecrypt, as they just get letters from BIOS... you tried an external USB-keyboard? does the problem occur when typing anything (e.g. trying to set a password) into BIOS? * reset BIOS to default?

Hi, Originally I had Windows 10 1903 installed without any recovery- or OEM-partition (just on one single partition, non-UEFI-machine. I VC-encrypted that system partition. Then I did an Upgrade to Windows 10 1909 using the Install-DVD, using the following method from github veracrapt-w10-patcher (without de-encrypting the system partition): 1. Download and extract Windows 10 installation media (with media creation tool, then 7zip...) 2. You need at least version 1.23 of VeraCrypt. o You can update...

Hi, Originally I had Windows 10 1903 installed without any recovery- or OEM-partition (just on one single partition, non-UEFI-machine. I VC-encrypted that system partition. Then I did an Upgrade to Windows 10 1909 using the Install-DVD, using the following method from github veracrapt-w10-patcher (without de-encrypting the system partition): 1. Download and extract Windows 10 installation media (with media creation tool, then 7zip...) 2. You need at least version 1.23 of VeraCrypt. o You can update...

Thanks for your reply, it just seems to have been unblocked. I use Windows 10 1909. Behaviour in Q-Dir is the same as in Windows Explorer: Drive M is not visible in "this PC". It just seems to be a different "skin" for the data that windows supplies for "this PC". I already thought about registry, but the problem is that drive M is not a physical drive. So all the registry stuff e.g. for USB drives used in the past does not apply. No drive is recorded as ever to have been mounted as M. I can't even...

Bug: "Fast format" doesn't work when creating container (can't be cancelled)

For me, the problem seems solved since using Windows 10. I never had the message so far, no matter if I use "mount as removable medium" or not. So it seems the problem was somehow caused by Windows 7.