Error 1325: VBRCatalog is not a valid short file name

This posting is ~5 years years old. You should keep this in mind. IT is a short living business. This information might be outdated.

While upgrading a rather old (but very stable) Veeam Backup & Replication 6.1 installation to 8.0 Update 3 (with intermediate step to 6.5), I ran into a curious error. Right after the welcome screen, this error message


Patrick Terlisten/ Creative Commons CC0

appeared. A closer look into the BackupSetup.log (you can find this log in the %temp% dir. Just enter %temp% into the Explorer address bar) resulted in this very interesting log entry:

MSI (c) (28!50) [10:38:14:496]: PROPERTY CHANGE: Modifying CATALOGPATH property. Its current value is 'D:\Veeam\VBRCatalog\'. Its new value: 'E:\VBRCatalog\'.

First, the VBRCatalog folder was located under D:\Veeam, so why the hell was the CATALOGPATH property changed to E:\VBRCatalog? I searched the registry for for E:\VBRCatalog and found multiple entries for it. One of the entries was located under “HKLM\SOFTWARE\Wow6432Node\Veeam\Veeam Backup Catalog”. The entry under “HKLM\SOFTWARE\Veeam\Veeam Backup Catalog” pointed to the correct path. I found some other entries, e.g. in connection with Windows Installer.

After changing all found entries to the correct path, the update went smooth. The reason for this error was that the VBRCatalog was moved after the installation. I did this more than 3 years ago and followed Veeam KB1453. But this article only describes the change of the CatalogPath entry under “HKLM\SOFTWARE\Veeam\Veeam Backup Catalog”. You have to change all references to the old VBRCatalog path! Otherwise you will run into the same error as I.

Patrick Terlisten
Follow me

11 thoughts on “Error 1325: VBRCatalog is not a valid short file name

  1. Paul Milligan

    Thank you. I was unable to uninstall the Veeam trial and was getting the same error. The addition of a new SATA card in my server had resulted in a drive letter change. Your post put me on the right track.

  2. Frank

    Thank you.Like you i was unable to upgrade the free edition from 8.0 to 9.0 and also like Paul having the same error when try to uninstall 8.0.
    I’m pretty sure i didn’t change anything with the drive letters but as in your case i had the E:VBRCatalog entry multiple times in the registry.

  3. Hannes S

    Thanks! Same error here when Upgrading from 9.0 to 9.5 – only thing odd is, that my Veeam machine never had a drive lettered E: but still somehow exactly this entry existed and pointed to the wring directory. Updates from 8 to 9 versions did not encounter any errors or problems. Strange thing… but anyhow, thanks again ;)

  4. Steph

    Thanks! Got the same error during an upgrade from 9.0 to 9.5 but for a different path. I did a search for VBRCatalog in the registry and found that HKLMSoftMicrosoftCurrentVersionInstallerUserDataS-1-5-18Components548FDDBB83EB487478FBC0FD5AC7CDCB was pointing to E:VBRCatalog .. This drive does not exist anymore… Changed it to C:VBRCatalog and it solved my problem!

  5. Paul

    really useful. I followed the principles here & helped the upgrade for Veeam 9.5 – to update 4. Many thanks

  6. Алексей

    2020 год и все еще помогаете людям :)
    Обновление c Veeam v9.5 до v10 и та же ошибка, хотя я никогда его не перемещал.
    Поискал по реестру и везде заменил E:VBRCatalog на С:VBRCatalog и помогло!


Leave a Reply

Your email address will not be published. Required fields are marked *