Windows 10: The Windows Security Center Protection Status Delay Fix

It seems Windows 10 is giving me a new issue every few bootups. One of the most recent was the missing WSC icon. Windows Defender was running but the WSC icon (MSASCuiL) would not stay in processes when first started.

I was able to fix the issue in the end, but not before finding this information about protection status delay. It was not the solution to my problem; nevertheless, what the article describes was what I always thought was normal process. Never thought it could be tweaked and improved.

:)

 

Windows keeps turning off the security center.

Hi Maninder,

I suggest you to follow the steps below and check if it helps.

• Press Windows key + R and type Services.msc then hit enter.
• Services Console will appear.
• Find Security Center Service on the right details pane > right click it choose properties >
• Security Center Properties should appear > on the General Tab

set start-up type to automatic (Delayed start)

• On service Status Stop and then Start.

If this does not works & error still continues then there are more chances that your system is infected

Let us know the status of the issue in regards with Security Center. Your reply is important to assist you further.

Regards,

Guru Kiran

 

windows defender & security center services keep turning off


Are you running any other AV or did you have one running in the past? If you didn't use an uninstaller for the AV, then the remnants of it could be causing the problem. Normally any time you install an AV it disables Defender by default.

If you are getting any error codes please list those, that will be helpful in helping you.

As torre suggested, might be a good idea to do a reset or even a reinstall.

Reset Windows 10 - Windows 10 Forums

Windows 10 - Clean Install - Windows 10 Forums

There are also some suggestions listed here:

Unable to turn on Windows Defender in Windows 7 / 8 / 10

 

Shouldn’t the Windows Defender Security Center be monitoring and updating the operational status of third-party AV apps?

Things are getting a little bit fuzzy now that we have two user interfaces for Windows Defender, and two Security Centers (in the Creators Edition), and I’m seeing some pretty obvious inconsistencies in the protection status that’s being reported by
these different apps. My first clue that there was a problem came from a fluke that causes the Windows Defender Service to fail at startup whenever I use the
Restart option on this PC, and this startup failure usually crashes the Windows Defender Security Center. The bothersome part, though, is that when the Windows Defender Service fails to start, there’s never any indication of a problem in either the
old Security Center (Security and Maintenance) or the new Security Center (Windows Defender Security Center) – which is a bit awkward, because this means that the only warning that the Windows Defender Service is stopped is appearing in the old Windows Defender
UI, which is pretty well hidden away these days in the Creators Edition:

I have Avast Free installed on this PC, with Windows Defender running in its Limited Periodic Scanning mode. So I kind of expected that both Security Centers might completely ignore the status of Windows Defender when it’s running in its Limited Periodic
Scanning (on-demand) mode. Not a good thing; but I guess it's not really such big deal, because the status of the primary AV app (i.e., the app that’s providing real-time protection) would properly be the main determinant for the protection status. So then
I turned off all of Avast’s shields, expecting the protection status to be updated for both Security Centers – but this is what I got:





I actually did get a notification from the old Security Center that Avast was turned off, but not a peep from the new Security Center, and having these two Security Centers contradicting each other certainly can’t be a good thing. Since I’ve seen other
quirks with Windows Defender on this old machine, I installed Avast Free on my new
ideapad in order to make sure that this wasn’t just some kind of fluke – but I got exactly the same result. Now, the documentation seems to suggest that there should be a connection, and a commonality, between the two Security Centers with regard to
monitoring the protection status of third-party AV apps:

The Windows Defender Security Center app uses the Windows Defender Security Center Service (SecurityHealthService or
Windows Security Health Servce), which in turn utilizes the Security Center service (wscsvc)
to ensure the app provides the most up-to-date information about the protection status on the endpoint, including protection offered by third-party antivirus products, Windows Firewall, and other security protection.

The Windows Security app

So I was wondering whether this issue with the protection status not updating might be something that was specific to Avast, or if it was something more general. To answer that question, I installed AVG Free on another PC that's running
the Creators Edition. But once again, I got the same result – turning off both AVG’s
file shield and its behavior shield resulted in a notification from the old Security Center (Security and Maintenance), but the Windows Defender Security Center never noticed that the primary (real-time) AV app had been turned off. So it’s
beginning to look like this might be a general issue with the Windows Defender Security Center. Of course you could argue that the Windows Defender Security Center is designed exclusively for Windows Defender users, and that there’s no good reason for it to
extend the courtesy of monitoring the protection status of third-party AV apps. But that surely goes contrary to the spirit of building an all-inclusive health monitoring app for Windows 10. At the very least, people who use third-party AV apps need to be
aware of the situation.