Skip to main content
Question

Failed to connect to the backup server: Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins' is denied

  • June 18, 2026
  • 6 comments
  • 42 views

morgan.munck
Forum|alt.badge.img

Hello everyone,

I updated a VBR console to v13, but after the update, I was unable to connect to the console and received the following message:

“Failed to connect to the backup server: Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins’ is denied”

I noticed that when I launch the console using “Run as administrator,” I can access it without any issues. 

I checked the Registry Editor, and the permissions are correct.

What’s surprising is that I haven’t encountered this error with other customers who have upgraded to v13.

I don’t know how to resolve this issue. Do you have any ideas, or have you also experienced this problem?

Thanks in advance

 


 

Bonjour tout le monde,

J'ai passé une console VBR en v13, cependant après cette mise à jour je ne parvenais plus à me connecter à la console avec le message suivant:

"Failed to connect to the backup server: Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\Plugins' is denied"

J'ai constaté qu'en démarrant la console grâce à: "Exécuter en tant qu'administrateur" je peux accéder sans soucis à la console. 

J'ai vérifier dans l'éditeur de registe et les autorisations sont bonnes.

Ce qui est surprenant c'est que je n'ai pas cette erreur chez d'autres clients passés en v13.

Je ne sais pas comment faire pour résoudre ce soucis? Avez-vous des idées ou avez vous aussi eu ce soucis?

Merci d’avance

6 comments

coolsport00
Forum|alt.badge.img+23
  • Veeam Legend
  • June 18, 2026

Hi ​@morgan.munck - there was a post on this similar issue a few mos back:

It seemed a bit egregious the fix they came up with. Does this environment run SQL or PSSQL? Does the environment have special registry fixes from the previous version? Those reg fixes may need updating/recreated? Aside from checking the above post and those couple items, I would recommend getting in touch with Support.

Hope that helps.

 


Chris.Childerhose
Forum|alt.badge.img+22

I have seen this and run as Administrator works.  I went in and changed the permissions on that registry key, and it then worked as my account.  To me, it seems to be a bug but would be best reported to Support so if it is, they can fix it.


morgan.munck
Forum|alt.badge.img
  • Author
  • VUG Leader
  • June 18, 2026

There have been no changes to the registry key in the past. I'll report this issue to support and get back to you when I have more information. I would be willing to try changing the permissions on the registry key, but since this is in one of our clients' environments, I'd prefer to get approval from support before making any changes to the registry. 


Chris.Childerhose
Forum|alt.badge.img+22

There have been no changes to the registry key in the past. I'll report this issue to support and get back to you when I have more information. I would be willing to try changing the permissions on the registry key, but since this is in one of our clients' environments, I'd prefer to get approval from support before making any changes to the registry. 

Absolutely.  I saw this in our lab so was able to change it without issue but yes get approval most definitely.


coolsport00
Forum|alt.badge.img+23
  • Veeam Legend
  • June 18, 2026

@morgan.munck - yep...totally agree on that. Keep us posted what they say if you can.


AndrePulia
Forum|alt.badge.img+9
  • Veeam Vanguard
  • June 18, 2026

@morgan.munck What if you try reinstalling it from scratch? I think it would be faster.