This project has moved and is read-only. For the latest updates, please go here.
1
Vote

2015.09.19 Beta 1.15 Upgrade Prevents Access to Hot-Keys & GUI Until Reboot

description

Hello Mounir,

When I perform VeraCrypt upgrades, I usually answer No to the message box to reboot my system now since I usually have other applications or tasks that I am performing with mounted and/or unmounted volumes.

The 1.15 beta dated 2015.09.19 will not allow me to use hot-keys or open the GUI when I click on the desktop icon until I reboot my system. All attempts to access the application resulted in the attached error messages I received. Also, the VeraCrypt icon no longer shows in the system tray.

I had to reboot my PC in order to gain access to the application.

Past upgrades would still allow the GUI to be accessed via the desktop icon, although the hot-keys failed to work until the user either rebooted the PC or answered the yes/no question to see the latest release notes when they opened the application without reboot. This could lead to users corrupting their volumes if they are still mounted and with no way to access the application to dismount.

Kind Regards.

file attachments

comments

Enigma2Illusion wrote Sep 20, 2015 at 7:36 AM

Uploading second error message.

Enigma2Illusion wrote Sep 20, 2015 at 8:01 AM

PS: What happens to systems that are using system encryption and the user defers the reboot using this version?

idrassi wrote Sep 20, 2015 at 11:07 PM

Hi Enigma2Illusion,

This error is currently unavoidable:
  • when upgrading, the installer tries to dismount volumes, unload the driver and close the GUI in order to be able to overwrite their respective files.
  • in the situation you are describing, the installer was able to close the GUI and replace VeraCrypt.exe but it couldn't unload the driver because the volume could not be dismounted.
  • the installer offers to reboot. If refused, VeraCrypt.exe can't be launched since it doesn't match the driver version.
  • It worked before because there was a mistake in the previous 1.15-BETA: it was using 0x0114 as a version instead of 0x0115. The last build uses 0x0115 and that's why you are seeing the error.
In the case of system encryption, you will get the same thing with the GUI failing to start.

It is very difficult to implement a correct solution for this...we must update the driver, the associated server and the exe files and ideally the user should be able to continue using VeraCrypt after the update and before reboot. I don't see how we can do this right now if there are volumes mounted during the upgrade that can't dismounted automatically because the old driver will continue running but the associated service will be deleted!

This needs a lot of thinking because of the complexity of the relationship of the components involved (driver + service + mounted volumes + exe files).

Enigma2Illusion wrote Sep 21, 2015 at 12:00 AM

Hello Mounir,

Thank you for the detailed explanation of the issue.

Suggestion

In the interim until a method can be developed to allow deferring the reboot during upgrade, what about changing the installer after the user selects Upgrade/Repair (the default) to prompt the user with a screen that will dismount all mounted volumes due to a reboot of the system is mandatory? Validate that all volumes except system of course, are dismounted before proceeding with the upgrade of the software.

Allow the user the option to abort the upgrade instead of dismounting all volumes at this screen in case the user cannot reboot their system at the moment of the upgrade due to other activities they have running on their system.

Also remove the No option to reboot message box at the end of upgrade to avoid confusion and leaving users with open volumes.

What are your ideas?

Kind Regards.