A Digitally Signed Driver is Required - (New Windows 10 PCs)
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 https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB40156
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.