No longer shutdown; now snoozing??

Hi DavidCash
 
I am not aware of any major changes in terms of v9.08.72 when compared to the previous release and am having trouble situating your statement about "discontinued my ability to shut it down completely and replaced the function with "snoozing""?
 
As far as I am aware when I click on 'Shutdown protection' WSA exits completely...I have WIndows screaming at me that I have no antivirus protection.  What is indicating to you a state of 'snoozing' rather than complete shutdown?  If you could provide some guidance on that point then I can look to check here and see if I can replicate the issue for you.
 
Regards, Baldrick

I have a feeling that the "snoozing notification" is a result of a recent download conflict between Windows Defender and WSA.  Prior to this problem, I had both programs installed but I never ran the two together.  On the contrary, my usual procedure for over a long year, was to (a) disconnect from the internet, (b) select the WSA shutdown, (c) receive notification that my anti-virus was indeed "shutdown"... And then I would enter my Action Center where (a) my Security had both Defender and WSA showing with red alerts, and (b) with the option to activate either.  I then could select Defender if I wanted.
 
So I would then reconnect to the internet, download updates for Defender, and run a quick scan.  Several minutes later, I would disconnect from the interent, deactive Defender, and reactive WSA.
 
A silly procedure but nevertheless one which always listed WSA as "shutdown", not as "snoozing".
 
Since it is not a big deal with me, I will simply remove Defender from being pinned to my Taskbar, and move on.
 
I have not upgraded yet to Win 10.  It is apparent to me that Defender will be obliterated if and when I do.  And it is also apparent to me that I am well protected by WSA. 

Ah, I see...thanks for clarifying.
 
You may well be right and if interested please see this previous thread about the aforementioned Windows Security Centre  & WSA issue, which includes a fix for that issue which may or may not be pertinent to you.
 
Regards, Baldrick