cancel
Showing results for 
Search instead for 
Did you mean: 

Secure Application Manager Disconnected

Highlighted
New Contributor

Secure Application Manager Disconnected

I have a Windows 10 64 bit PC at home I use to remote into work. I had Pulse Secure working on it, but a month ago, I did a reset on it to rectify some version conflicts I had with SQL. This worked great, I reinstalled my programs, and when trying to remote in, I reinstalled Pulse Secure. In doing this, I get an error regarding an unsigned driver - NetBios. When restarting in safe mode (allowing unsigned drivers) and reinstalling, the same error occurs.

Strange thing is, when I connect, Everything seems fine. I have to click 'yes' to allow changes to be made, and then it gives me a success message that I've connected to my work network. However, when looking at the Secure Application Manager icon, it says disconnected. I am unable to connect at all.

My PC name was changed during the reset, so that may have something to do with it. Any info you can provide would be very much appreciated.

Thank you,
Mike
5 REPLIES 5
Highlighted
Moderator

Re: Secure Application Manager Disconnected

What version of the PCS server are you using? What version of Pulse? There are incompatibilities with Pulse versions pre-5.2R5 and Windows 10 anniversary update; one of them is that the OS does not recognize the driver.
Highlighted
New Contributor

Re: Secure Application Manager Disconnected

I resolved the problem by doing a full recovery on the pc. Thank you.
Highlighted
Moderator

Re: Secure Application Manager Disconnected

Thank you for the update; I am glad to hear it works now
Highlighted
New Contributor

Re: Secure Application Manager Disconnected

I am facing a similar issue with Windows 10 1607 and facing the driver issue w.r.t NEOFLTR.SYS file. Whats the solution to fix the issue. Would someone please help!!!
Highlighted
Moderator

Re: Secure Application Manager Disconnected

bhat: please upgrade to 8.2R6 on the PCS server
if there is failure at that point, please open a case with our support team as 8.2R6 resolves the items we have found ourselves as well as reported by other customers