Windows 10: Couldn't turn on Windows security centre service?

couldn't turn on windows security centre service?

:)

 

Turn On Windows Security Centre Service Message

Hi Kush,

We suggest that you perform these steps and see if it helps:

Step 1: Turn off your Windows Security Centre Service Message.

Step 2: Perform System File Checker (SFC) scan.



System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. To perform the SFC Scan, you may refer to this
link.



Step 3: Clean boot.

A clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This will help to eliminate software conflicts that occur when you install a program. Please see this
link for the steps.

Step 4: Turn on you Windows Security Centre Service Message

Let us know if the same issue persists.

 

Turn On Windows Security Centre Service Message

I tried step 1 and then step 2, in step 2 no problems were found.

I did not try step 3 because the system I have setup is a complete clean install of Windows 10. Apart from my web cam and printer all other drivers were installed by Windows.

The Windows Security Centre Service message is still popping up then usually disappearing after a few seconds. Are their any specific applications that are likely to conflict with Windows Security Centre?

 

Security centre is turned off notification


Today on a couple of occasions shortly after booting my pc I have been alerted by the notification centre sound and pop up that security centre is turned off. However the pop up disappears so fast it's a wonder I even saw it. Looking in the notification centre list after there is no mention of it. It's as if the security centre is being turned on correctly just as windows is thinking 'hey it's not on'. I don't think there is any issue as such and I verified both defender and windows firewall are on and functioning ok. I did a few restarts just now and it did not happen again, so it's prob a rarity and was just a little tardy starting the service but it has happened twice today. It's just odd because I've never encountered that before and I wondered if anyone had seen this happen. I noted that the security centre service is set to automatic delayed start. I did think 'delayed' was the key component here but having looked at some other machines it seems to be the normal setting.