All Topics » Pulse Desktop Clients

A Digitally Signed Driver is Required - (New Windows 10 PCs)

Contributor (1)
Jan 4, 2017 3:45pm
Have had a number of new Laptops being brought to out support desk from users with new Windows 10 PCs being unable to access our Corporate network. Similar, have had users with new desktops ringing us. When attempting to install the necessary Pulse Secure software amongst other things they get the following error:

Program Comparability Assistant
A digitally signed driver is required
netbios redirector
Pulse Secure, LLC

Windows blocked the installation of a digitally unsigned driver.
Uninstall the program.........

These are brand new Windows 10 Laptops/Desktops with the latest fully patched Windows updates.

I noticed you have a KB for Windows 7 on what seems a closely related issue but could find nothing on Windows 10

Taking my cue from the above article and using google I think I was able to pin down the problem to uefi bios computers with secure boot enabled.
Temporary/one off workarounds:
Boot up in safe mode with networking & then remoting in
Starting up the computer with "Disable driver signature enforcement"

However, only able to get a "permanent" workaround after disabling secure boot in the bios.

I put "permanent" in parenthesis because I don't consider this a proper solution. For our corporate computers for other reasons we disable secure boot. Moreover, because we lock it down we have a lot of control over what goes on to these computers. However, as an organisation we are a bit wary of recommending staff do this on their personal computers. Potentially, down the line they or one of their cherubs may install something on that is harmful to their computer and we don't want them coming back to us saying it wouldn't have happened if they followed this "solution."

My questions are as follows:
Why is this happening on new fully updated uefi/secure boot windows 10 computers and NOT similar but windows 10 updated computers with a "traditional" or older bioses?
Are there any "safer" solutions we can apply on the client end?
Is there anything our networking team can do with the Pulse Secure Server software from the back end to resolve this issue?

This is my 1st posting so sorry for the long rant and I apologise in advance if I have broken any forum conventions.


Contributor (0)
Jan 12, 2017 7:03pm
Our company is experiencing the same issue.
    Contributor (0)
    Jan 25, 2017 8:40pm
    We are having exact same issue! Please can we get an update on this.
    Contributor (0)
    Jan 27, 2017 1:53pm
    Upgrading our PSA hardware to 8.2R6.0 resolved this issue for us.
Pulse Secure Contributor (40)
Jan 20, 2017 8:50pm
What version are you using?
Do you see the same behavior with Pulse 5.2R5?
    Contributor (1)
    Jan 23, 2017 5:49pm
    Manually installed Pulse the Pulse 5.2R5 client on 1 of the PCs with this problem - No joy I'm afraid ie SAM status always Disconnected
Contributor (0)
Jan 24, 2017 6:54am
Hello All,

Facing a similar issue with secure boot enabled and windows 10 1607, whats the solution to have it resolved??


    Pulse Secure Contributor (40)
    Feb 1, 2017 11:09pm
    You should be able to use 8.2R6 successfully
    If you continue to see errors, please open a case as all the ones we have been able to identify and test have been resolved by 8.2R6
Contributor (0)
Jan 27, 2017 1:54pm
Upgrading our PSA hardware to 8.2R6.0 resolved this issue for us.
    Pulse Secure Contributor (40)
    Feb 1, 2017 11:08pm
    Thank you for the update; I am glad to hear it is working for you
Contributor (0)
Feb 3, 2017 7:50pm
Please use solution