What's the deal with Win 10 and driver signing

I have my clean install up and running. I need to install some drivers for my Fiio X3 to work as a DAC. The drivers are signed (and confirmed signed during the install process), and no warnings pop up during the install. But the X3 won't work. Checking the device manager there is a warning about not being able to verify the signing or some BS like that. In order to get the X3 to work I need to boot the damn computer with driver signing disabled every freaking time.
What's up with this damn thing?

 

High end and Pro Audio support is not a Windows 10 strong point. Give them time to get signed drivers sorted out. Audio drivers are among the last on Windows to get properly updated on working on new versions.

 

disable secure boot

permanently enable driver test signing

command prompt -> right click run as admin

bcdedit /set testsigning on

bcdedit.exe -set TESTSIGNING ON

bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS

bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS

 

Tried the CMDs but of course got the error about secure boot. Put all further work on hold just in case I end up punting the computer down the hallway. Everything was working fine until I decided to try a clean install.
Was fairly OK with Win 10 up till lately, but all these little niggly things are really piling up, making a copy of Win 7 look a hell of alot more appealing

 

disable secure boot before you put command

also, don't run cmd from Win+R, search "command prompt" and right click -> run as admin

 

Tried the commands before I read your post. Got fed up at the time, so hadn't gotten round to disabling secure boot.

Anyways got it disabled now, thanks. Is there anyway to get rid of the version #, et al from the bottom corner of the screen. I find it a tad distracting, but I could learn to live with it

 

For kicks I figured that I'd install a copy of Win7 just to test out if all my issues would be solved. I used an OEM version I got using the ISO downloader, installed it to USB using rufus. The install goes well until it has to reboot, then the whole thing freezes at the Windows Starting animation. Had the same thing happen trying to use a Windows to Go install too.
Got secure boot disabled, gpt, uefi set up correctly. Any ideas if I've overlooked something or are they actually hobbling laptops to not be able to run Win7 now

 

it is sometimes just a driver hanging up. I usually have an issue when the system tries to start the drives in ACH rather than IDE or visa versa. It could be some other driver as well.

 

Makes sense. I tried telling the installer to get updates first, but that just led to an error.
Maybe I need to try a different version of Windows7?