Comprehensive data protection for all workloads
Post Reply
lightsout
Expert
Posts: 227
Liked: 62 times
Joined: Apr 10, 2014 4:13 pm
Contact:

Patch 10a CP3 (build 10.0.0.4854 P20201202) failing with "failed to get full path to the package"

Post by lightsout »

Just downloading and running the update, and I'm getting the message "failed to get full path to the package". Looking back through the forums this seems to be a digital signing issue, but I don't see that, everything validates fine.

Code: Select all

PS C:\Users\Public> Get-AuthenticodeSignature '.\VeeamBackup&Replication_10.0.1.4854_KB4050.exe'


    Directory: C:\Users\Public


SignerCertificate                         Status                                                     Path
-----------------                         ------                                                     ----
43C940341257F3390612124531304E471905C80F  Valid                                                      VeeamBackup&Replication_10.0.1.4854_KB4050.exe
Anyone else seeing this issue? I can't find any logs so I am not sure what the problem is.

Thanks!
foggy
Veeam Software
Posts: 21074
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Patch 10a CP3 (build 10.0.0.4854 P20201202) failing with "failed to get full path to the package"

Post by foggy »

Have you reviewed this thread already? If no hints are applicable, feel free to ask our engineers for assistance. Thanks!
lightsout
Expert
Posts: 227
Liked: 62 times
Joined: Apr 10, 2014 4:13 pm
Contact:

Re: Patch 10a CP3 (build 10.0.0.4854 P20201202) failing with "failed to get full path to the package"

Post by lightsout » 1 person likes this post

I did, but I can't find any missing certs this time. I've raised a case #04537722 to work this out.
lightsout
Expert
Posts: 227
Liked: 62 times
Joined: Apr 10, 2014 4:13 pm
Contact:

Re: Patch 10a CP3 (build 10.0.0.4854 P20201202) failing with "failed to get full path to the package"

Post by lightsout » 1 person likes this post

Found a fix I've seen before. Deleted “Microsoft Code Verification Root” from the trusted root store, and that has fixed it. Not sure why this is required.
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 25 guests