(06-17-2024, 12:57 AM)Froggie Wrote: The Devs may have to come up with another solution. Since the entire installation package is unsigned, my guess would be that this new driver is unsigned as well. I run a System that doesn't require driver signing so I never see that error.
We'll see how the Devs handle this issue...
Yes we have to wait for the devs, they will probably find a solution