Issue when using v4.01 on Win7x64

User discussion and information resource forum for TeraByte Drive Image products, including TBNetManage.
Post Reply
MerleOne
Posts: 6
Joined: Sat Dec 28, 2019 10:18 pm

Issue when using v4.01 on Win7x64

Post by MerleOne »

Hi,
I get this error message (sorry it's in French) when I use IFW v4.01 on a Win7 PC (click on thumbnail to enlarge)
Image
It basically says that some drivers are not signed.
I never got this with 3.64 version nor 4.01 on Win10.
Does that mean that V4 is not Win7 compatible ?
Thanks,
Regards,
.merle1.
TeraByte Support
Posts: 3891
Joined: Thu May 05, 2011 10:37 pm

Re: Issue when using v4.01 on Win7x64

Post by TeraByte Support »

It basically same issue as viewtopic.php?t=4225

The driver has a SHA1 signature on it but it's not crossed signed because the MS cross-signing certificate is expired and they won't be issuing a new one. The SHA256 signature is from MS themselves. If you don't use meta-data option, those drivers aren't needed/used anyway.
MerleOne
Posts: 6
Joined: Sat Dec 28, 2019 10:18 pm

Re: Issue when using v4.01 on Win7x64

Post by MerleOne »

TeraByte Support wrote: Wed Jun 26, 2024 3:16 am It basically same issue as viewtopic.php?t=4225

The driver has a SHA1 signature on it but it's not crossed signed because the MS cross-signing certificate is expired and they won't be issuing a new one. The SHA256 signature is from MS themselves. If you don't use meta-data option, those drivers aren't needed/used anyway.
Thanks for your reply. 2 remarks :
1/ Regarding the link at the beginning, I would like to mention that version 3.64 works fine on that Win7 system. Issue occurs only with V4.x.
2/ I do use meta-data option in the general settings but especially in the backup of changes setting, to speed up the process, I would like to keep that option (for speed)

So I guess I have to keep using v 3.64...
Sincerely
.merle1.
TeraByte Support
Posts: 3891
Joined: Thu May 05, 2011 10:37 pm

Re: Issue when using v4.01 on Win7x64

Post by TeraByte Support »

You would either have to ignore the MS warning/turn off the driver restriction or use the old drivers, but the old drivers have a CVE: CVE-2024-31757
Post Reply