Update failing due to invalid digital signature of downloaded file

[hnmr]

Hi there,

I have received a notification about a new available version and want to update. When I start the download, it works fine but shows an error at the end "The digital signature of the downloaded update file is invalid. Most likely, it got corrupted. Please download the update again." I have tried the update/download several times with the same result.
The installed version is "Veeam Agent for Windows 5.0.3.4708 - Free Edition". The setup file downloaded has the version 6.0.2.1090.

Here are the last relevant lines of the file Svc.VeeamEndpointBackup.log:

Code: Select all

[29.05.2023 12:52:56] <39> Info     No license was received
[29.05.2023 12:52:56] <39> Info     Licenses:
[29.05.2023 12:52:56] <39> Info         Local license: none
[29.05.2023 12:52:56] <39> Info         Foreign license: none
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] Checking updates for version 5.0.3.4708
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] Downloading new update definition file from https://autolk.veeam.com/json-rpc.php
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] Result is UpdatesFound
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] List of alive updates in DB:
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] -----------------------------
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] AgentWindows v.5.0.3.4708 in state Updated (28.06.2022 23:24:26) with URL https://download2.veeam.com/VAW/v5/VeeamAgentWindows_5.0.3.4708.exe. Id 54d6b244-1aa8-4212-915c-391db1ee378a, Parent Id -
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] AgentWindows v.6.0.2.1090 in state FailedToValidate (29.05.2023 12:35:46) with URL https://download2.veeam.com/VAW/v6/VeeamAgentWindows_6.0.2.1090.exe. Id 7accabdf-e1bb-4147-87eb-43c0a95252a7, Parent Id -
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] -----------------------------
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] Deleting obsolette update info AgentWindows v.6.0.2.1090 in state FailedToValidate (29.05.2023 12:35:46) with URL https://download2.veeam.com/VAW/v6/VeeamAgentWindows_6.0.2.1090.exe. Id 7accabdf-e1bb-4147-87eb-43c0a95252a7, Parent Id -
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] Adding major update info AgentWindows v.6.0.2.1090 in state New (29.05.2023 12:52:58) with URL https://download2.veeam.com/VAW/v6/VeeamAgentWindows_6.0.2.1090.exe. Id 52b557b5-df95-4ce2-abe6-c2be51961aa6, Parent Id -
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] List of alive updates in DB:
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] -----------------------------
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] AgentWindows v.5.0.3.4708 in state Updated (28.06.2022 23:24:26) with URL https://download2.veeam.com/VAW/v5/VeeamAgentWindows_5.0.3.4708.exe. Id 54d6b244-1aa8-4212-915c-391db1ee378a, Parent Id -
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] AgentWindows v.6.0.2.1090 in state New (29.05.2023 12:52:58) with URL https://download2.veeam.com/VAW/v6/VeeamAgentWindows_6.0.2.1090.exe. Id 52b557b5-df95-4ce2-abe6-c2be51961aa6, Parent Id -
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] -----------------------------
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] Starting BITS job Id 52b557b5-df95-4ce2-abe6-c2be51961aa6 from URL https://download2.veeam.com/VAW/v6/VeeamAgentWindows_6.0.2.1090.exe
[29.05.2023 12:52:58] <43> Info     [AutoUpdate] BITS job creating
[29.05.2023 12:53:24] <29> Info     [AutoUpdate] BITS job Id = 52b557b5-df95-4ce2-abe6-c2be51961aa6 completed successfully
[29.05.2023 12:53:24] <29> Info     [AutoUpdate] Validating update C:\ProgramData\Veeam\VeeamUpdates\52b557b5-df95-4ce2-abe6-c2be51961aa6.Exe.
[29.05.2023 12:53:26] <29> Info     [This server] Trying to connect to Installer service. Account: '<current user>'. IP addresses: '127.0.0.1;192.168.178.34'. Port: '6183'.
[29.05.2023 12:53:26] <29> Info     [This server] Trying to connect to Installer service on 127.0.0.1:6183.
[29.05.2023 12:53:26] < 4> Info     VD: Set end point. Host: [127.0.0.1], Port: [6183]
[29.05.2023 12:53:26] < 4> Info     VD: Set RPC timeout. Request timeout: [3600] sec.
[29.05.2023 12:53:26] < 4> Info     Connecting to the remote instance of deployment service
[29.05.2023 12:53:26] < 4> Info     Connecting to RPC port '6183', host '127.0.0.1', service 'VeeamDeploymentSvc', secure channel: 'false' .
[29.05.2023 12:53:26] <29> Info     [This server] Checking whether remote Installer service is available.
[29.05.2023 12:53:26] < 4> Info     Getting version of the deployment service.
[29.05.2023 12:53:26] < 4> Info     Service version: [6]
[29.05.2023 12:53:26] <29> Info     [This server] Connection to Installer service is established. Endpoint: '127.0.0.1:6183'
[29.05.2023 12:53:26] <29> Info     [This server] Trying to connect to proxy service. Account: '<current user>'. IP addresses: '127.0.0.1'. Port: '6183'. Backup console version: '5.0.3.4708'.
[29.05.2023 12:53:26] < 4> Info     Connecting to RPC port '6183', host '127.0.0.1', service 'VeeamRpcInvoker', secure channel: 'false' .
[29.05.2023 12:53:26] <29> Info     [This server] Connection to the proxy service is established. Endpoint: '127.0.0.1:6183'
[29.05.2023 12:53:26] <29> Info     [This server] Creating Package Commander.
[29.05.2023 12:53:26] <29> Error    [AutoUpdate] Failed to validate
[29.05.2023 12:53:26] <29> Error    Failed to check signature: The digital signature of the downloaded update file is invalid.
[29.05.2023 12:53:26] <29> Error    Most likely, it got corrupted. Please, download the update again. (System.Exception)
[29.05.2023 12:53:26] <29> Error       bei Veeam.Backup.ProxyProvider.CProxyPackageCommander.CheckSignature(String modulePath)
[29.05.2023 12:53:26] <29> Error       bei Veeam.Backup.Core.CProductUpdateValidator.ValidateUpdate(CProductUpdateInfo updateInfo, String path)
[29.05.2023 12:53:26] <29> Error    The digital signature of the downloaded update file is invalid.
[29.05.2023 12:53:26] <29> Error    Most likely, it got corrupted. Please, download the update again. (System.Exception)
[29.05.2023 12:53:26] <29> Error       bei Veeam.Backup.ProxyProvider.CProxyPackageCommander.CheckSignature(String modulePath)

Appreciate your help very much!
Regards,
H.

[Brad403]

The same thing happened to me. So, to get around it, I downloaded Veeam Agent for Windows free edition again, and when I launched it, it allowed me to update it from the previous version.

[M_Peror]

Same here. Sure the workaround would work, but is not very confidence-inspiring if the agent fails to trust its own updater.

[SuperPigDots]

Yeah, I am having the same issue. It's a pain to have to fill out all the signup stuff and redownload a fresh install just to work around this issue. I'm just not updating until this is fixed... unless it still isn't in like 6 months.

[3d0]

The same thing happened to me. So, to get around it, I downloaded Veeam Agent for Windows free edition again, and when I launched it, it allowed me to update it from the previous version.

I confirm, the workaround works. Maybe the autoupdate can't manage the upgrade to a major version.

[SDay]

Is Veeam not addressing the problem and show a way to update without the work-around? Wouldn't the be the right thing to do?

[Mildur]

Hi Stefan

There was a change for Veeam Agent v6 in how the signature is handled. This requires on some circumstances a manual update of the Veeam Agent v5 to v6.
We will provide a KB article shortly. I'll update this topic when it is ready.

Best,
Fabian

[wgjett3]

FWIW, I had the same issue. If you poke around within the agent software you will actually see the reason why the failure is happening. The message said that there's a difference in v5 and v6 and there was a hotlink to download the latest version of the agent software...without signing up for a trial again.

[wgjett3]

I should clarify that the agent was installed in "unmanaged" mode. I don't imagine those options would be available if you're managing your endpoints from the VBR console.

[Mildur]

The KB article is now available:
https://www.veeam.com/kb4455

Thanks,
Fabian

[hnmr]

Thank you everyone for your comments!
The workaround in the KB article didn't work for me. I had to execute the downloaded installer manually.
BTW: It can be found in C:\ProgramData\Veeam\VeeamUpdates after it has been downloaded by the Veeam update process (which itself fails). At least, I didn't have to sign up to Veeam to download the installer....

[dejudicibus]

Same issue.