Hello Ventuzians!
THE FORUMS ARE CLOSED!

Please join our discord server HERE!! << click me :D

We are shutting our Ventuz Forum, but don't worry, it will all be archived for you to search in if you have a query. From now on, please add all your comments, questions or observations into our Discord Server

Thanks for the great time - see you on discord!!
Dee, Karol, Daniel and the whoooole Product and Support team!

V4.08 - DeltaCast driver doesn't install

Please report bugs in this group. We will maybe populate a list of known bugs with a possibly modified description at a later time.

Moderator: Support

Post Reply
SamTheSwede
Posts: 91
Joined: 18 Jan 2012, 11:31

V4.08 - DeltaCast driver doesn't install

Post by SamTheSwede » 05 Apr 2016, 12:51

I get an error when updating the Deltacast driver to 5.19 as supplied with V4.08

The device status in windows device manager states:

"Windows cannot verify the digital signature for the drivers required for this device....."

Tried two different DeltaCast HD Key E 2 2 cards with the drivers from the Ventuz install catalog and from www.ventuz.com/drivers

Anyone that can reproduce or see what's wrong?

Win 7x64 on a quite recent VBox.

All the best,

Sam

SamTheSwede
Posts: 91
Joined: 18 Jan 2012, 11:31

Re: V4.08 - DeltaCast driver doesn't install

Post by SamTheSwede » 05 Apr 2016, 17:59

Solved!

Make sure to update Windows 7 as some old digital signature stuff expired on jan 31st 2016.

// Sam

User avatar
Karol
Posts: 640
Joined: 10 Jan 2012, 12:07

Re: V4.08 - DeltaCast driver doesn't install

Post by Karol » 07 Apr 2016, 09:45

Hi Sam!

Thank you very much for this info! We didn't know that - seems that our systems are pretty well maintained :)
I guess you won't be the last who stumbles upon this issue.

Cheers
Karol

SamTheSwede
Posts: 91
Joined: 18 Jan 2012, 11:31

Re: V4.08 - DeltaCast driver doesn't install

Post by SamTheSwede » 07 Apr 2016, 19:07

Karol,

It was actually a brand new machine, a V-Box that haven't been unpacked for a year.... :o

BTW, stumbled upon it again today, but now we knew why the problem occurred!

// Sam

Post Reply