Windows 10: my Windows Defender shows red, i could not activate it again.

hello

my PC with widows 10 . windows security does not work. how to reactivate it?

:)

 

Cannot activate Windows Defender

On my laptop "Toshiba Satellite L455" I did upgradation to W-10 from W-7 (original).

There is no antivirus program on this PC.

I wanted Windows Defender to run. But it says that it is switched off.

Want to activate it.

On opening Windows defender, there is no option to activate it.

In step 2 of your suggestion, it says:

"Windows could not start the Windows Defender Network Inspection Service on local computer.

Error 1068: The dependency service or group failed to start"

Can you pl give a method to activate the defender?

 

i activate the windows defender but it shows windows potentially unprotected

Whether i activate windows defender but it shows the pc potentially unprotected.

suggest me what to do??

 

Windows Defender Red X

I ran the first scan an no integrity errors were found.

The second suggestion came up with "No component store corruption detected. The operation completed successfully" and "[==========================100.0%==========================] The restore operation completed successfully.

The operation completed successfully." The red X on the Windows Defender icon continues.

The issue is that the icon in the notifications tray shows the red X and when I hover over it, it says "Actions needed." Yet, when I open up Windows Defender, all the areas show green Xs and say there are no actions needed. So, the third suggestion above
only takes me there where there's nothing to be troubleshot, even though the icon says there are actions needed.

Right-clicking on the choices when I click on the icon I get this error message: "Page not available. Your IT administrator has limited access to some areas of this app, and the item to tried to access is not available. Contact IT helpdesk for more information."
Which makes no sense as this is a personal computer at home. I'm the IT department.

There's got to be something with this April update causing this, as it never happened until then.