I just pressed without any password and the machine booted.The DiskCryptor bootloader still prompted me for a password at each reboot.De-crypt the system drive (most likely C:).As always, backup first!! I did not need my backup, but I can't guarantee you won't need yours ). UPDATE: Just to close the loop, I performed the following steps with no ill effects. I have seen users complain in the past that the Windows OS upgrade sees the encrypted drive/partition as RAW format and Windows tries to be too helpful by automatically quick formatting the partition and assigning a drive letter to make it usable by Windows. NOTE: Dismount and disconnect any external encrypted volumes attached to your PC before you begin the OS upgrade. You must decrypt the system encryption before performing any OS upgrades.Īlso, Windows 10 November update requires decrypting the OS in order to apply the Windupdate. The workaround is described in a separate forum post: What is the best way to report this to Microsoft? Obviously, on VeraCrypt, we are lacking man power to investigate further such deep kernel blocking by the update installer. By doing this, Microsoft is breaking FDE software other than Bitlocker and Microsoft partners ones. VeraCrypt driver is working as expected but this installer clearly blocks it during the process of updating the system. Microsoft is doing something nasty in the update installer. There is nothing magical in TrueCrypt driver that would have prevented this. It is this specific Windows update that seems to disable filter drivers used for on the fly encryption and if Windows was encrypted using TrueCrypt, it would have failed too. TrueCrypt would have had the same problem. Windows 10 version 1511, build 10586 update fail This appears to be a problem with Full Disk Encryption software generally (with the presumable exception of MS's own BitLocker).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |