Skip to main content
Question

An error has occurred: Version provider was not found in suite context.

  • November 6, 2025
  • 1 comment
  • 130 views

2025-11-06

 

Subject: VBR 12.3.2.4165 Installation Failure Version provider was not found in suite context on Windows 11 Pro ARM Parallels

Hello,

I am attempting a fresh installation of Veeam Backup & Replication Community Edition (ISO: 12.3.2.4165) on a newly created virtual machine, but the Veeam Setup Engine consistently fails with the error: An error has occurred: Version provider was not found in suite context.

Environment Details: My host is a MacBook Air running macOS Tahoe 26.1 and I am using Parallels Desktop 26 for Mac. The guest operating system is Windows 11 Pro, Version 25H2. The system type is a 64-bit operating system with an ARM-based processor. The ARM architecture may be a factor in the installer's execution checks.

Troubleshooting Steps Completed:

I have tried running Setup.exe as administrator, unblocked the ISO file in its Properties, and also extracted the entire ISO contents to a local folder and tried the setup again.

I have confirmed that .NET Framework 4.8.1 or later is installed and enabled.

I have also manually checked for and deleted conflicting upgrade registry keys in HKEY_CLASSES_ROOT\Installer\UpgradeCodes, specifically targeting keys related to the known installer conflict. This is a new VM and no previous version of Veeam has ever been installed.

Since the error persists after all standard fixes, I suspect the issue is related to the Veeam installer's compatibility checks on the ARM architecture.

Could you please advise on the next steps, or is this a known issue with the 12.3.2.4165 installer on Windows ARM virtual machines?

I can provide the setup logs from C:\ProgramData\Veeam\Setup\Temp if needed.

Thank you.

1 comment

  • New Here
  • August 30, 2026

2025-11-06

 

Subject: VBR 12.3.2.4165 Installation Failure Version provider was not found in suite context on Windows 11 Pro ARM Parallels

Hello,

I am attempting a fresh installation of Veeam Backup & Replication Community Edition (ISO: 12.3.2.4165) on a newly created virtual machine, but the Veeam Setup Engine consistently fails with the error: An error has occurred: Version provider was not found in suite context.

Environment Details: My host is a MacBook Air running macOS Tahoe 26.1 and I am using Parallels Desktop 26 for Mac. The guest operating system is Windows 11 Pro, Version 25H2. The system type is a 64-bit operating system with an ARM-based processor. The ARM architecture may be a factor in the installer's execution checks.

Troubleshooting Steps Completed:

I have tried running Setup.exe as administrator, unblocked the ISO file in its Properties, and also extracted the entire ISO contents to a local folder and tried the setup again.

I have confirmed that .NET Framework 4.8.1 or later is installed and enabled.

I have also manually checked for and deleted conflicting upgrade registry keys in HKEY_CLASSES_ROOT\Installer\UpgradeCodes, specifically targeting keys related to the known installer conflict. This is a new VM and no previous version of Veeam has ever been installed.

Since the error persists after all standard fixes, I suspect the issue is related to the Veeam installer's compatibility checks on the ARM architecture.

Could you please advise on the next steps, or is this a known issue with the 12.3.2.4165 installer on Windows ARM virtual machines?

I can provide the setup logs from C:\ProgramData\Veeam\Setup\Temp if needed.

Thank you.

Correct, its the setup executable failing as it sees is ARM edition. I just went down this rabbit hole and came across your post. I was able to make it quite far with Windows 11 25H2 ARM inside Parrallels on MacOS. Crazy setup but would be nice to eliminate traveling with a 2nd laptop. 

I was able to get into the VBR console and connect to localhost but it shows offline BackupProxy and Server. I have the option to rescan and update both. This is where it fails for me and I hit a roadblock. It tries to install VeeamMountService and unfortunately it fails as it attempts to install a Kernel Level Driver that is for X64 architecture. This causes the rescan and update to fail and not bring Veeam to a usable state. Can’t seem to make it past these. Running this MSI fails as well with the same driver related error. 

I installed manually using the exe’s in setup for PostgreSQL, Reportviewer, .Net and the required IIS features and components. For PostgreSQL I had to permit access using the conf files as I’m assuming Veeam setup.exe does this. Then for Veeam (run CMD as admin and execute): VeeamBackupCatalog64.msi → Server.x64.msi → Shell.x64.msi

What’s weird is I do have Veeam 12.2 working inside Windows 11 ARM. I do not get hung on the issues where it seems to force to update/install MountServices and seems to ignore these. I know you lose features but I am able to use backup and replication features.