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

1.18a failed to update

description

I tried to upgrade VeraCrypt 1.17 to 1.18a using the windows exe file. It failed to install/update the program and I had to install 1.17 to be able to use the program again.

comments

Enigma2Illusion wrote Aug 28, 2016 at 1:15 AM

What error did you get during the upgrade?

What version of Windows are you running on your PC?

Did you disable your Anti-Virus software before the upgrade?

CryptoDerp wrote Aug 30, 2016 at 1:39 AM

The program simply failed to install the upgrade. It simply said "installation failed" or something to that effect.

I am using Windows Vista. My Anti-Virus software wasn't disabled prior to installation.

Enigma2Illusion wrote Aug 30, 2016 at 3:10 AM

Are you running 32-bit or 64-bit OS?

Are you using system encryption?

Try the VeraCrypt upgrade with your Anti-Virus disabled or uninstalled during the upgrade.

CryptoDerp wrote Aug 31, 2016 at 11:33 PM

32-bit OS, no encryption.

Alberto123 wrote Sep 3, 2016 at 11:49 AM

I've got the same Problem subscribed above: Windows Vista 32-bit, no encryption, Avast AntiVir disabled during installation. No chance to install VeraCrypt 1.18a. Version 1.17 installs without any problem.

bastnja wrote Oct 21, 2016 at 8:47 PM

Hi, same problem with me here, running Vista and Windows Security essentials.
Veracrypt 1.17 installs no problems.
At 1.18 and 1.19, I get "Installation Failed" and here is the sequence of events:
-Installing Veracrypt decive driver
-Starting Veracrypt device driver
-adding icon ... Veracrypt.lnk
-The installation has been rolled back

TechTeamUK wrote Nov 7, 2016 at 5:07 PM

Same issue here, but first not on Vista it seems.

Win Server 2008 Std (32 bit), AV = McAfee (enabled), existing encrypted partition.

Slight backstory...

TrueCrypt to VeraCrypt update.
Managed to get through TC 7.1a to VC 1.0f-2.
Tried to update that to 1.19 - FAIL - auto roll-back (per Bastnja's comment above)
Try instead to 1.18 - FAIL (same again).
Try 1.17 - SUCCESS.
Then from 1.17, unable to update to anything newer (same issue again).

We're probably not going to be able to use this if a future update doesn't fix the install bug with newer versions, unfortunately.