"Turn on Virus Protection" Notification pops up after reboot

I don't have any 3rd party security software installed and never had, like stated above. Also, i don't remember changing anything in my PC or installing anything even remotely related to this during the days when the bug appeared.

However, my manufacturer recently updated BIOS, so it might be related, but then it's also related to that Certificate Enroll error which i get with server 400 code. I also checked that in my BIOS secure boot was set to "custom" for some reason, and offered me to restore keys etc. options. I changed it to standard, locked all those tricky options. So I guess now it should be handled automatically. The system booted normally with "standard" option, but i still got the notification and also still get that "Protocol AIK certificate request error". However, standard Microsoft Support is only limited to "let's try uninstall your system" or "let's check your PC for viruses". I tried showing them Event Viewer error logs, but they didn't understand that.

blownwiththeWin said:

Hi, everyone! I lately discovered a weird bug. For now I think it can be reproduced by performing a system restart... A few minutes after restart and logging in I get a "Turn on Virus Protection" notification. It says that it's now turned off and I should click to turn it on. But when i click, it's already turned on..... I googled a bit, seems like some users experience the same lately, but nobody knows how to fix it. Any ideas?

Update: not sure, but seems like it's related to Chrome Browser unless it's a coincidence. Notification pop-ups when I launch chrome or something. I completely removed it from my computer and reinstalled. Fun fact that this notification popped again the first second when I downloaded Chrome installer from Edge... might be just a coincidence or whatever.. just my observations

Click to expand...

This bug seems to be fixed on my PC after the latest update.

LittleJay said:

This bug seems to be fixed on my PC after the latest update.

Click to expand...

"Seems" might the key word here. It gets fixed until the first few reboots, then appears again. At least on my PC.