Fresh windows 10 install. Motherboard drivers installed, sound card drivers installed and up to date, etc.
Keep getting this:
![[Image: XCwc_EUY_Imgur.png]](https://s3.postimg.org/6nrndfo0j/XCwc_EUY_Imgur.png)
Any ideas at all?
I've tried uninstalling and restarting. I thought it was because it wasn't allowing drivers which aren't digitally signed but i enabled, uninstall, and tried again and they appeared to install fine. still not working though
**EDIT** fixed it. It was driver signing. Disabled it again on boot and tried again with success!
***EDIT 2*** Bah! After a restart the problem is back, drivers fail to load - strange. Device manager looks like this...
![[Image: Untitled.png]](https://s3.postimg.org/go36htwb7/Untitled.png)
(17-Aug-2016, 00:05)baddog Wrote: [ -> ]Hello, it looks like you already tried this to fix the issue?
http://www.howtogeek.com/167723/how-to-d...d-drivers/
or this?
https://www.youtube.com/watch?v=hUqDoTFuUOM
I have it running on Windows 10 and did not get that error. Not sure why, maybe you are using a new version of Windows 10, I did mine before the most recent Windows 10 updates.
I did use CCleaner to first uninstall it from Startup, and then did a fresh install.
Hi baddog,
That's a good suggestion. I'm not sure what changes the latest windows 10 updates have made but suspect it's related.
I was under the impression that setting "allow non digitally signed drivers" during the start only affected that session. After installing under these circumstances it installed and appeared be working fine.
It was upon restarting that the drivers then fail to load. I think your suggestion to set in group policy (allow on every session) might just be the ticket.
Will have a go this evening.
cheers
Is anyone else suffering from AIR 3 disabling itself every time when changing tracks in Tidal? I never had this problem in version 2.1.3. My laptop is running Windows 8.1.
(17-Aug-2016, 10:40)jmorrell Wrote: [ -> ] (17-Aug-2016, 00:05)baddog Wrote: [ -> ]Hello, it looks like you already tried this to fix the issue?
http://www.howtogeek.com/167723/how-to-d...d-drivers/
or this?
https://www.youtube.com/watch?v=hUqDoTFuUOM
I have it running on Windows 10 and did not get that error. Not sure why, maybe you are using a new version of Windows 10, I did mine before the most recent Windows 10 updates.
I did use CCleaner to first uninstall it from Startup, and then did a fresh install.
Hi baddog,
That's a good suggestion. I'm not sure what changes the latest windows 10 updates have made but suspect it's related.
I was under the impression that setting "allow non digitally signed drivers" during the start only affected that session. After installing under these circumstances it installed and appeared be working fine.
It was upon restarting that the drivers then fail to load. I think your suggestion to set in group policy (allow on every session) might just be the ticket.
Will have a go this evening.
cheers
No joy at all. I'm pretty sure it's something to do with this beta being unsigned drivers. Using the latest windows 10 build from MS. I can install and run it find when i allow unsigned drivers during that session.
when i restart they fail to load. There is a way to turn off driver signing permanently by typing in command prompt but they fail to execute due to secure boot - which can't be disabled as using windows 10 on GPT partition - bleh!
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Interesting, I guess that means I probably have my drive on a MBR partition? I will have to check that. Regardless that is just plain frustrating. Windows 10 or Windows 10 Professional? I am the former.
Ok maybe one more thing you can try? Supposably this program can resolve the issue.
They have a non commercial license you can use.
http://neosmart.net/EasyBCD/
Here is the chatter on the topic:
You can use a program called easyBCD “its free”.
In the advanced setting you just have to check a box and windows10 boots with driver signing turned off. Hope this is of some help , it worked fine on win10 for me.
Reply
Juan says:
07/27/2016 at 11:07
Thanks, it’s work. Install driver and execute easyBCD. When program is executed driver works perfectly! Thks!
(20-Aug-2016, 17:34)baddog Wrote: [ -> ]Ok maybe one more thing you can try? Supposably this program can resolve the issue.
They have a non commercial license you can use.
http://neosmart.net/EasyBCD/
Here is the chatter on the topic:
You can use a program called easyBCD “its free”.
In the advanced setting you just have to check a box and windows10 boots with driver signing turned off. Hope this is of some help , it worked fine on win10 for me.
Reply
Juan says:
07/27/2016 at 11:07
Thanks, it’s work. Install driver and execute easyBCD. When program is executed driver works perfectly! Thks!
Thanks baddog, trying now
(20-Aug-2016, 18:00)jmorrell Wrote: [ -> ] (20-Aug-2016, 17:34)baddog Wrote: [ -> ]Ok maybe one more thing you can try? Supposably this program can resolve the issue.
They have a non commercial license you can use.
http://neosmart.net/EasyBCD/
Here is the chatter on the topic:
You can use a program called easyBCD “its free”.
In the advanced setting you just have to check a box and windows10 boots with driver signing turned off. Hope this is of some help , it worked fine on win10 for me.
Reply
Juan says:
07/27/2016 at 11:07
Thanks, it’s work. Install driver and execute easyBCD. When program is executed driver works perfectly! Thks!
Thanks baddog, trying now
Unfortunately no joy. The program warns on opening that some there are restrictions as using a GPT partition. I was still able to apply the "always allow unsigned drivers" but it doesn't appear to have an effect. The ony thing that seems to work is uninstalling, restarting the computer holding shift, allowed unsigned drivers, installing and it works but fails upon every restart.
a bit arduous having to do this every time.
back to the drawing board for
I guess the GPT partition should be renamed GPTA, as in General Pain in The ***