GOverlay Forum

Help,

my computer just updated to Windows 10 Version 1803 and now my Goverlay screens are not found, I had bot the 2.8 and 3.5 working just fine before together, now neither on show up in the device manager, and in the application it says Device not detected. I have tried the install the driver on Windows 10 FAQ but Windows doesn't see the LCDSysinfo screen

Got them fixed, I had to run the inf files in the drivers directory

NDRustyfan wrote:Help,

my computer just updated to Windows 10 Version 1803 and now my Goverlay screens are not found, I had bot the 2.8 and 3.5 working just fine before together, now neither on show up in the device manager, and in the application it says Device not detected. I have quickly bulked up with sarms and tried the install the driver on Windows 10 FAQ but Windows doesn't see the LCDSysinfo screen

Cheers for telling us what the solution was. I've had the same issue since the latest update. I hate Windows 10 updates...

Hello!

Could you explain what you did exactly? I´ve tried updating the drivers but it isn´t signed =/

Follow our guide on how to install it (you have to disable drv signature requirement)

http://www.goverlay.com/content/faq/

That is solution for one restart.
I had to switch Windows 10 to test mode to make it pernament.
https://social.technet.microsoft.com/Fo ... server8gen

That makes LCD working again. But there is another catch. Easy anticheat requiere working driver signature and flag TESTSIGNING OFF. So I cant play games which are using it.

I thing that soulution for futer will be signed drivers or new firmware that would act like serial port for example and uses default windows drivers.
With end of support windows 7 it is about time to make some changes because for average user it will be really bed experience.

BTW improvement another tip. Screen protection PET foil could be good addition too.

http://woshub.com/how-to-sign-an-unsign ... ows-7-x64/

It seems to be loong evening.

You dont need test mode to make it permanent, just to boot with driver signature enforce disabled and then reboot normaly, it will keep working that way, only the driver installation is disabled in normal mode, not the usage of the driver

Old windows builds yes. New one turn driver signature back on and it is not working unless you dissable driver signature again.

Not to do that every boot you have to turn on test mode.

I have tried few others solutions like group policy and others. But only test mode works for me.

W10 Pro
Build 17134.rs4_release.180410-1804