Hi ​@yakub.karahasanoglu,

Did you try to re-download the ISO? Could be an issue with the ISO or the files within.

And did you make sure that you are using the correct installer? As far as I remember there are two:

One for the upgrade and one for clean installations:

12.2.0.334 to 12.3.1.1139 upgrade failed | Veeam Community Resource Hub

Hard to say ​@yakub.karahasanoglu . You could possibly try to re-download the ISO file from your Support account, or check the install logs:

Installation and upgrade logs - the %ProgramData%\Veeam\Setup\Temp folder

Which one would be better for me to download?

When I checked I didn't see anything useful.

Check the log files here - C:\ProgramData\Veeam\Setup\Temp\

If that does not help check what Lukas posted and worse case contact Support.

You can try the upgrade ISO and see.  If that fails download the full ISO as it will do the same thing.

​@yakub.karahasanoglu - I didn’t see any differing ISO for upgrade vs install. I don’t think there are any. There’s just 1 download I’m pretty sure. If you didn’t see anything in the log, your best bet is to contact Support.

Just to add, also check the Windows Event Logs and see if anything is logged there as well. 

The log created in the temp file during the upgrade is as follows.

SetupBackupServer_16_04_2025_17_21_16.txt

[16.04.2025 17:18:38]:[00000001] [veeam] INFO    Checking installed product version (Id='{B1E61D9B-8D78-4419-8F63-D21279F71A56}', Name='Backup', ProductVersion=12.3.0.310, IsPreview=False)
/16.04.2025 17:18:38]:]00000001] ]VEEAM] INFO    Analysing installed product (Version='12.2.0.334')

If I uninstall the application and install the new version, can I get the jobs back from the backup configuration? Or will I have any problems?

​@yakub.karahasanoglu - yeah...not much there. I advise getting with Support to help with the Upgrde. Assuming you met all the requirements for Upgrade?...Support is your best avenue to get you sorted.

Hi

I encounter the exact same error when upgrading from 12.2.0.334 (as OP) to 12.3.2

The SuiteEngine log:

System.ComponentModel.Win32Exception: The system cannot open the device or file specified.
   at Veeam.Setup.MsiLibrary.VmMsiCommon.CheckError(VmMsiDatabase db, UInt32 result)
   at Veeam.Setup.MsiLibrary.VmMsiCommon.CheckError(UInt32 result)
   at Veeam.Setup.MsiLibrary.VmMsiCommon.OpenDatabase(String strPackage, UInt32 persistMode)
   at Veeam.Setup.Common.Foundation.SuiteContext.VmProductDetector.GetRelatedProductProperty(String relatedProductCode, String propertyName)
   at Veeam.Setup.BRSetup.LaunchConditions.VmUnsupportedPreviousVersionLaunchCondition.IsLgsBuildInstalled(VmSuiteProductInfo productInfo)
   at Veeam.Setup.BRSetup.LaunchConditions.VmUnsupportedPreviousVersionLaunchCondition.Check(IMessageHandler messageHandler)
   at Veeam.Setup.Autorun.WPF.Pages.AutorunPageViewModel.ExecuteLaunchConditions(Bundle bundle, IMessageHandler messageHandler, Boolean lazy, String& message)
   at Veeam.Setup.Autorun.WPF.Pages.AutorunPageViewModel.UpdateBundle(Bundle bundle, String bundleProperty, IMessageHandler messageHandler)
   at Veeam.Setup.Autorun.WPF.Pages.AutorunPageViewModel.PrepareForActivation()
   at Veeam.Setup.Wizard.WPF.WizardViewModel.MaybeSwitchToPage(Int32 index, Boolean refresh)
   at Veeam.Setup.Wizard.WPF.WizardViewModel.MaybeSwitchToNextEnabledPage()
   at Veeam.Setup.Wizard.WPF.WizardViewModel.ProcessPageSwitchRequest(PageSwitchRequestedEventArgs args)
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state)
   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)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   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)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Window.ShowHelper(Object booleanBox)
   at System.Windows.Window.Show()
   at System.Windows.Window.ShowDialog()
   at Veeam.Setup.Wizard.VmAutorunEngine.RunAutorun()
   at Veeam.Setup.Wizard.App.RunWizard()

​@mm_3945877 - As is shared in the comment threads, we recommend getting in touch with Veeam Support to help with your upgrade.

Best.

It is much easier to uninstall, reinstall, and import the configuration than to perform an in-place upgrade

Looks on OS related issue

Try to reinstall .NET framework