Hi,
I am having a little issue since the update to Win11 22H2. It worked fine for my system drive after decryping and then re-encrypting, and also my second HDD that I have crypted and set as a favorite for automount on boot just works fine.
I have one additional file container that is crypted, 2GB of size. It works fine, but takes around 10 seconds to mount. Wasn't that long before. Can live with it.
What is slightly annoying is that my crypted external hdd doesn't work at all anymore. Mounting it takes around 5 minutes (4TB) and while it shows as mounted in Veracrypt then, it just works and works and works and I can never open it in the explorer. It shows up in My Computer but without any properties.
Maybe it will work if I wait another hour, no idea, but it was like present in an instant before and has been over all the years. I doubt it suddenly failed. I only use it for backup, last time maybe a month ago when I was still on 22H1.
Any fix for that? Should I just re-format and create a new volume?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am having a little issue since the update to Win11 22H2. It worked fine for my system drive after decryping and then re-encrypting, and also my second HDD that I have crypted and set as a favorite for automount on boot just works fine.
I have one additional file container that is crypted, 2GB of size. It works fine, but takes around 10 seconds to mount. Wasn't that long before. Can live with it.
What is slightly annoying is that my crypted external hdd doesn't work at all anymore. Mounting it takes around 5 minutes (4TB) and while it shows as mounted in Veracrypt then, it just works and works and works and I can never open it in the explorer. It shows up in My Computer but without any properties.
Maybe it will work if I wait another hour, no idea, but it was like present in an instant before and has been over all the years. I doubt it suddenly failed. I only use it for backup, last time maybe a month ago when I was still on 22H1.
Any fix for that? Should I just re-format and create a new volume?
Have you tried the disk on other systems (both 22H1 and not) ? Is the issue consistently with 22H1 ?