Vault Patch FAQ

Windows, 5.3., 5.4, 5.5, 6.0, 6.1, 7.0.
How do I know what patches I can safely apply to my current version of Vault?

If you are running the Windows version of Vault you have the option of patching it in order to bring your Vault up to a newer version, or to fix a bug that is addressed by a specific patch.  However there are some considerations to keep in mind about this process.

1) If you are using Vault APIs, patching from a much lower version to a much higher version can change the API.  So exercise extreme caution if you are considering patching Vault in this case.

2) You can't apply the latest patch to any version of Vault.  You can only patch certain ranges to releases

Vault 5.3x can be patched up to the latest patch version of 5.3m5p1779 but no farther.  To go farther requires an upgrade / full install.

Vault 5.4m0 can be patched all the way to 5.4M3p0174 but no farther.  To go farther requires an upgrade / full install.

5.4M4p0164 can be patched all the way to 6.1m0p0123 but no farther.  To go farther requires an upgrade / full install.

7.0m0p007 (newly released) will also have patches available for the Windows version.  If you are on an earlier version (5 or 6) you will not be able to patch upgrade to 7.  You need to do the upgrade / full install because 7.0 has a new set of dependencies (open-ssl, Ghostscript, etc) and MS libraries  (compiler changed to Visual Studio 2010) so a simple overwrite of the exe files will not work. 

NOTE: if you patching 5.4 all the way to 6.1, you will not have access to new features such as indexerd, etc.  To get any features that weren't already in 5.4 you'd need to do the full upgrade/install.

NOTE2: None of this affects Doc1 compatibility levels.  That is controlled by the RMFUTIL.DLL version level and is beyond the scope of this article

NOTE3: This only applies to Vault on Windows.  Patches are not supplied for UNIX Vault; full builds are released for those platforms.
UPDATED:  September 18, 2017