Skip to main content
Question

cannot install veeam agent - OpenSSL v3.0.0 FIPS issue

  • June 19, 2026
  • 6 comments
  • 27 views

Forum|alt.badge.img+1

hello, i am not able to install veeam agent VeeamAgentWindows_13.0.3.1220.exe on my personal laptop running W11.25H2 and latest windows updates

please advise and thanks much

from the logs

[19.06.2026 09:38:18][INFO] Creating Installer Application instance.
[19.06.2026 09:38:18][INFO] Enumerating OpenSSL v3.0.0 FIPS related products...
[19.06.2026 09:38:18][ERROR] System.ComponentModel.Win32Exception (1605): This action is only valid for products that are currently installed.
   at Veeam.Setup.MsiLibrary.VmMsiCommon.GetProductInfo(String strProductCode, String strProperty)
   at Veeam.Setup.Endpoint.Core.VmRelatedProductsCollector.Collect(ProductConfiguration msi)
   at Veeam.Setup.Endpoint.Core.VmRelatedProductsCollector.Collect(VmProductList`1 products)
   at Veeam.Setup.Endpoint.Core.VmSuiteStateManager.Initialize()
   at Veeam.Setup.Endpoint.Core.InstallerApp..ctor(StartupConfiguration startupConfiguration)
   at Veeam.Setup.Endpoint.App.App_OnStartup(Object sender, StartupEventArgs e)
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

 

6 comments

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

There is something leftover on your system that Veeam is detecting via the Registry.  Try this to see if it fixes the issues - run the PS command to get the GUID for the PSChildName and then uninstall any residual components via MSIEXEC.

$paths = @(
"HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall",
"HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall"
)
foreach ($path in $paths) {
Get-ChildItem $path | Get-ItemProperty |
Where-Object { $_.DisplayName -like "*Veeam*" -or $_.DisplayName -like "*OpenSSL*" -or $_.DisplayName -like "*FIPS*" } |
Select-Object DisplayName, DisplayVersion, PSChildName
}


# Replace {GUID} with the IdentifyingNumber/PSChildName from above
msiexec /x {GUID-HERE} /qn
 
 
 
 

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

There is something the installer is detecting on the machine causing the errors and failed install.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • June 19, 2026

note: the registry entries do not exist on my system.

 

thank you for taking time to write the custom script on-the-fly. most impressive.

however this is no output, as run on the command line and inside notepad++

so, i added the following line to make sure there was some output
“write "thanks Chris.Childerhose!"

so here is the output

NPP_SAVE: d:\iso\veeam\vagent\13\doit.ps1
CD: d:\iso\veeam\vagent\13
Current directory: D:\iso\veeam\vagent\13
powershell.exe -ExecutionPolicy Unrestricted -NoLogo -File "d:\iso\veeam\vagent\13\doit.ps1"
Process started (PID=1000) >>>
thanks Chris.Childerhose!
<<< Process finished (PID=1000). (Exit code 0)
================ READY ================


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

Ok then unsure what to suggest now other than contacting Support.  There is something the installer does not like.

Did you check the Add/Remove Programs for anything Veeam and remove it?  Just a thought.


Forum|alt.badge.img+1
  • Author
  • Influencer
  • June 19, 2026

so in the past, my laptop was connected to a VBAR server running over tailscale.
for five years, all was great.

yesterday, i remove my laptop from the VBAR.
using VBAR, i uninstalled the veaam agent and removed the license.
rebooted my laptop.

now, i am trying to install standalone veeam agent free edition and getting the above error


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

So then my guess is there are remnants from the VBAR install somewhere that need to be cleaned up.  Check in the Add/Remove Programs for FIPS and remove it as well as any other Veeam items.