tinchote

If I'm not wrong, VC's bootloader is signed with the 2011 CA for secure boot. These certificates will expire in June-October. I assume this requires a new version of the bootloader that is signed with the new certificate?

I had successful updates with two computers, both with 1.26.7. In both cases from iso.

The previous couple big updates worked with the system partition encrypted, but it would be nice to have confirmation for 24H2.

Is there any documentation available on System Encryption Settings? I cannot find anything related to editing the bootloader configuration, and particularly the "PasswordTimeout" and "ActionTimeout" settings.

Is there any documentation available on System Encryption Settings? I cannot find anything related to editing the bootleader configuration, and particularly the "PasswordTimeout" and "ActionTimeout" settings.

Is there any documentation on how to use these options?

We misunderstood each other. When you said that it was natural for the volume to be seen as RAW, I thought you were talking in general, and not about the mis-connected one. We do agree in everything. Can I open a ticket, or is one expected for the devs to follow up from this?

Thanks for your answer. Chkdsk sees the disk perfectly and not as RAW; in fact, one can call chkdsk by right-clicking on VeraCrypt itself. It is not normal for chkdsk to see the disk as RAW. I'll try to see if I can implement what you say. In any case, when this happens, VeraCrypt is not reporting any kind of problem, and meanwhile Windows gives all kind of errors, failing to write to the MFT, and the drive is visible, the folders can be openened, but errors arise when one attempts to open a file....