#1 Global Leader in Data Resilience

Failed dependencies: libmsi1 is needed by veeam-guest-interaction-proxy

KB ID: 4734
Product: Veeam Backup & Replication | 13
Published: 2025-09-03
Last Modified: 2025-09-03
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

Attempting to add a Linux server as a managed server fails with the following error:

Failed dependencies: libmsi1 is needed by veeam-guest-interaction-proxy

Rocky Linux may also display the following error if the libmsi1 package is already installed:

Failed dependencies: ntfs-3g is need by veeam-mount-target

Cause

This error occurs when the libmsi1 package is missing from the Linux server being added to Veeam Backup & Replication.

This dependency may be missing on Rocky and RHEL (Red Hat Enterprise Linux) distros because it is part of the EPEL (Extra Packages for Enterprise Linux) Repository, which is disabled by default.

Solution

Below are distro-specific instructions for enabling the repo that contains the missing package(s), and installing those package(s).
Rocky Linux 9.x
Execute the following commands to install the EPEL Repository and the required packages to allow Veeam Backup & Replication to deploy the GIP (Guest Interaction Proxy) and Mount server components:
sudo dnf install -y epel-release
sudo dnf install -y libmsi1 ntfs-3g
RHEL 9.x
Execute the following commands to install the EPEL Repository and the required package to allow Veeam Backup & Replication to deploy the Guest Interaction Proxy components:
sudo subscription-manager repos --enable codeready-builder-for-rhel-9-$(arch)-rpms
sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
sudo dnf install -y libmsi1

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.