Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 38
Like Tree18Likes

Thread: WINDOWS 1607 APOLLO TWIN USB- Windows 10 Enforces Unsigned Driver Ban

  1. #11
    Up and Comer
    Join Date
    Oct 2015
    Posts
    5
    So I contacted UA with my problem and explained that I am using Windows 8.1 and was getting a Code 52. Customer Support replied to me with a fix for Windows 10 and said that my problems are resolved.
    I then sent them another email and explained that I am not using Windows 10 I am using Windows 8.1. The same person again sends me the same instructions on how to temporarily fix the problem for a Windows 10 Opperating System.
    Do they even read the emails sent to them. I am not very good dealing with computer issues in the first place but the instructions he sent dont work on my Opperating System. Frustrating to say the least.

  2. #12
    Experienced UAD User FonderieFoniche's Avatar
    Join Date
    Nov 2012
    Location
    Asti, Italy
    Posts
    181
    I just updated my system to Windows 10 Anniversary & UAD v.9.0, and I had the same "unsigned driver" problem with my Apollo Quad silver.

    I solved opening a command prompt as administrator, and disabling the driver signature enforcement with the string:

    bcdedit.exe /set nointegritychecks on

    Unlike the "F7" trick I've seen around, this one works permanently, unless the feature is restored with the same string:

    bcdedit.exe /set nointegritychecks off

    Just some remark:

    in case of the string isn't accepted by the system, either be sure to enter the command prompt as Administrator, and, if the bios of your machine has the chance to disable the UEFI Secure-boot in it, disable it before to launch the command string. It is possible you must clear the secure boot keys before the bios let you to disable the secure-boot (i.e on ASUS motherboards, like mine).

    Of course, your system this way WILL NOT PERFORM ANYMORE any control on the drivers you will install; so it must be done VERY carefully, and you must be very careful to what you install.

    I've not checked yet, but it is possible that the procedure must be repeated after every significant Windows update, in case it will restore the default signature enforcement.

    This way, I've now a perfectly working system, waiting for a definitive solution from UA.
    I hope this can help someone.
    Don Schenk likes this.
    facebook.com/Fonderiefoniche
    instagram.com/Fonderiefoniche
    __________________________________________________
    Apollo Quad, UAD2 Octo+Duo PCIe, UAD Software 9.1, Pro Tools 12.7

  3. #13
    Up and Comer
    Join Date
    Dec 2016
    Posts
    6
    we dont want to wait any longer. uad must bring the new driver. immediately!

  4. #14
    Up and Comer
    Join Date
    Oct 2016
    Posts
    13
    UA what is the purpose of having forums if you're not going to utilize them to get in touch with your customers? We have issues and you're not helping. You're just standing idly by with no new information etc. I hope you understand that actions like this are making you lose life long customers at this point. My business has been affected due to this incompatibility between your 3rd party drivers and windows 10. Were here with answers and the solution, but it's sad to see you seem uninterested to help.

  5. #15
    Up and Comer
    Join Date
    Oct 2016
    Posts
    13
    Even with the secure boot workaround. I get glitches and pops. Clicks,random noises, etc all day long on a brand new 2016 fully specd out pc with a twin duo usb3

  6. #16
    Practically a UAD Expert Kcatthedog's Avatar
    Join Date
    Dec 2011
    Posts
    7,666
    @wompr this is not an official UA forum and any UA staff who participate here do so informally.

    You need to contact UA Customer Service formally at UA, not here.

    Since UA is the first party and its plugs are proprietary to it and Windows is an independent operating system that UA doesn't have any control over or other 3rd parties developers, what 3rd party issues are you having and how is it UA's responsibility ?

  7. #17
    Up and Comer
    Join Date
    Jan 2017
    Posts
    1
    Quote Originally Posted by Kcatthedog View Post
    @wompr this is not an official UA forum and any UA staff who participate here do so informally.

    You need to contact UA Customer Service formally at UA, not here.

    Since UA is the first party and its plugs are proprietary to it and Windows is an independent operating system that UA doesn't have any control over or other 3rd parties developers, what 3rd party issues are you having and how is it UA's responsibility ?
    From what i can see, UAD lists this requirement:
    Windows 10 with Anniversary Update (64-Bit Edition) is required.

    ...and from what i can understand, the drivers needs to be digitally signed from now on in order to work:
    Driver Signing Changes in Windows 10 Anniversary Update

    Now, how is that not the responsibility of UAD to make their product work under Windows 10 if it is listed as required OS? Or am i missing something?

    I recently upgraded my DAW with a fresh Windows 10 install and is now stuck with tons of work and having to resort to weird tricks for it to hopefully work. At least, one could expect a public anouncement from UAD regarding this issue?

  8. #18
    Up and Comer
    Join Date
    Jan 2017
    Posts
    2
    Hey all,

    So this is the response I received from UAD. Not ideal but a workaround at best!

    Dave (Universal Audio)

    Jan 19, 4:02 PM PST

    Hi,

    Thanks for the email.
    We are working on this and will release signed drivers soon.

    In the meantime, here's the workaround.



    Click the Start menu and select Settings.
    Click Update and Security.
    Click on Recovery.
    Click Restart now under Advanced Startup.
    Click Troubleshoot.
    Click Advanced options.
    Click Startup Settings.
    Click on Restart.
    On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.

    Your computer will restart and Windows 10 will no longer block the UAD drivers from loading. Note that if you reboot your computer Driver Signature Enforcement will be re-enabled, so this procedure needs to be repeated with every boot.

    Thanks for your patience.
    GMichaelHall likes this.

  9. #19
    Practically a UAD Expert Kcatthedog's Avatar
    Join Date
    Dec 2011
    Posts
    7,666
    @dahlback you seemed to have missed that my comment was about wompr's reference to 3rd party developers ? I think Windows and apple are 2nd party to UA ?

  10. #20
    MBI
    MBI is offline
    Up and Comer
    Join Date
    Aug 2008
    Location
    Switzerland
    Posts
    18

    Question

    Quote Originally Posted by everythingsound1544 View Post
    We are working on this and will release signed drivers soon.
    The question is what means soon? Again 2-3 months until the next driver will be released?
    Dany likes this.

Page 2 of 4 FirstFirst 1234 LastLast

Similar Threads

  1. Replies: 24
    Last Post: 28th November 2016, 05:35 PM
  2. Replies: 4
    Last Post: 18th November 2016, 01:28 AM
  3. Replies: 5
    Last Post: 17th May 2016, 12:20 PM
  4. New Windows Driver for Apollo USB due Friday
    By mm-pro in forum Apollo Interfaces
    Replies: 2
    Last Post: 17th February 2016, 04:45 PM
  5. Apollo Twin Duo USB on Windows 10?
    By NayPalmay in forum General Discussion
    Replies: 3
    Last Post: 13th October 2015, 04:50 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •