NeK

Instead of directly removing the possibility to mount I would have added an interim version that either would use a popup and report all volumes that will be unsupported in the next one with the option to convert them to a supported configuration or in the new setup before really removing the old version do a scan or prompt the user to select all his volumes/containers to check them for incompatibility and give the option to convert to something supported

Yes it really would be a big help to have VSS available for Veracrypt encrypted partitions, I am additionally missing it for: Previous Versions / Snapshots Deduplication requires VSS

Just want to thank you, I successfully upgraded 3 encrypted Windows 10 installations to 1803 with VC 1.23-BETA0 without the need to decrypt! That is really a great improvment. In my case Additionally used "/ResizeRecoveryPartition Disable" to avoid the creation of an additional partition.

"Disable fast boot" Thank you so much, that makes totally sense, it might be the Windows Fall Creators Update that enabled it again, as I was sure that I disabled it in the past ... first try looked good!

I still have issues with the system favorite volumes with v1.22 Beta 3. Have it running on my computer and notebook and both have the issue: When I start my computer (cold boot) I have to wait until windows is ready and reboot Windows, only then the system favorite volumes get mounted, always at the second boot.

The disks are normally build in the tower and connected by sata cable directly to the mainboard, so no eSata or external disk. Mount system favorite volumes when Windows starts: checked Toshiba MD04ACA400 \?\PhysicalDrive1 : Layout Partition Style = PARTITION_STYLE_GPT Layout Parition Count = 1 Partition 1: StartOffset=17408 Length=134217728 - MSFT_RESERVED - OK Samsung HD204UI \?\PhysicalDrive6 : Layout Partition Style = PARTITION_STYLE_GPT Layout Parition Count = 1 Partition 1: StartOffset=17408...

Hi thanks I checked it now and the Volume IDs is the same in the favorites and the properties of the disk. I found out it happens always with 2 disks. In the eventlog it is reported like this for those disks: Favorite "ID:..." is disconnected. It will be ignored. But it is working OK if I disable to use the Volume IDs for those disks.