cancel
Showing results for 
Search instead for 
Did you mean: 

Dsconnect every x minutes after updating microsoft defender

SOLVED
azpiazu
New Contributor

Dsconnect every x minutes after updating microsoft defender

Good morning,

 

I want to expose the following issue in case someone can help me:

After executing a script to update the antivirus Microsoft Defender when I go to connect to Pulse Secure it asks me to enter the password and the token twice, when the normal thing is one time.

Once connected every X minutes (every hour or so) it disconnects and I have to re-enter the password and the token again.

 

Does anyone have a solution for this?

 

Thank you very much in advance

1 ACCEPTED SOLUTION

Accepted Solutions
azpiazu
New Contributor

Re: Dsconnect every x minutes after updating microsoft defender

The problem was the version of windows installed. It was solved by installing the PRO version and the problem was with the Home version

View solution in original post

4 REPLIES 4
r@yElr3y
Moderator

Re: Dsconnect every x minutes after updating microsoft defender

@azpiazu Can you try changing the network i.e. by using mobile hotspot and check if you observing similar disconnects? Did it work before the upgrade of MS defender?

PCS Expert
Pulse Connect Secure Certified Expert
azpiazu
New Contributor

Re: Dsconnect every x minutes after updating microsoft defender

I have tried connecting from other Wi-Fi networks or from the mobile internet and the same thing happens. It also happens to more people at my job. If it happens to us since we updated the microfost defender, it has to be something related to that, because before that it worked correctly for us

Thanks for the help

r@yElr3y
Moderator

Re: Dsconnect every x minutes after updating microsoft defender

@azpiazu This might need additional debugging, can you please open a support ticket with us?

PCS Expert
Pulse Connect Secure Certified Expert
azpiazu
New Contributor

Re: Dsconnect every x minutes after updating microsoft defender

The problem was the version of windows installed. It was solved by installing the PRO version and the problem was with the Home version

View solution in original post