Windows 10: When I turn on my computer I get a notification that reads "Virus protection is not turned on.

When I turn on my computer I get a notificationthat reads "Virus protection is not turned on. "Tap or click to turn on Microsoft Defender Antivirus. I have looked at my settings and When I go to Security Security everything is o.k.no action needed. Then if I click on "Open Windows Security". I get this message " Page not available Your IT Administrator has limited access to some areas of this app, and the item you tried is not available. contact IT help desk for more info.This sounds like its for a business, I am an individual. Any ideas how to resolve this.One suggestion was: You can hide the

:)

 

Windows 10 notification keeps reporting Turn on Virus Protection

Original Title: Defender

Windows 10 notification keeps reporting "Turn on Virus Protection. Virus protection is turned off. Under Settings/Update & Security/ Windows Defender all the options show "On", including Real Time Protection. However the settings are greyed out and I cannot
try turn off and then back on. Any suggestions as to how to fix defender?

 

Turning on spyware and virus protection

I have Windows 10 and have been advised that both my spyware and virus protections are not turned on. I have tried to turn them on but to no avail. I do not have any competing protection installed on my computer. Please advise as to how to proceed.

 

Windows 10 notification keeps reporting Turn on Virus Protection

This is the third time I have asked for help on this issue in the past 10 days. Does Microsoft even read these anymore. I have the same error message as above and it just started after getting an update from Microsoft when I went to turn off my computer.
I use Webroot for my anti virus, Windows says it's on and Webroot says computer protected but I am still getting the notification that "Windows Defender and Webroot Secure Anywhere are turned off".

My system worked fine since I upgraded from Win 8.1 back in July 2015 until March 2016. I see it was a problem back in Aug 2015, so what did Microsoft do...put a quick fix on it and now it has creeped up again. Will someone let me know how to correct this.
I am an insider and never had this with the pre-release version.