Recently, since about half a year and till today, after nearly each bigger Windows Update I am observing problems booting Windows (10, Pro, x64) when there is whole system partition encryption applied. The problem seems to be Windows Update changing boot files on 2nd = "system" partition. While I have other disk with Linux and I can rename files properly to fix this issue, there may be some (many?) users that will end up with Windows constantly trying to do the automatic repair. I am not sure if there is a solution for this problem on VeraCrypt side. Each update time I need to boot Linux, rename the files and then I can boot Windows. Anyone else has observed this? As I don't see any topics here about that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Recently, since about half a year and till today, after nearly each bigger Windows Update I am observing problems booting Windows (10, Pro, x64) when there is whole system partition encryption applied. The problem seems to be Windows Update changing boot files on 2nd = "system" partition. While I have other disk with Linux and I can rename files properly to fix this issue, there may be some (many?) users that will end up with Windows constantly trying to do the automatic repair. I am not sure if there is a solution for this problem on VeraCrypt side. Each update time I need to boot Linux, rename the files and then I can boot Windows. Anyone else has observed this? As I don't see any topics here about that.