360 security for windows 10 desktop keygen#
On a few machines, I found events reporting they were trying to register with AAD but failing (which make sense for on-premise AD joined boxes). It's not a security concern to me, as long as there are not other events logged related to AAD. The event is logged when Windows starts, which is when it checks its domain relationship, so the same behavior occur with AAD.Īs stated in this KB article about other events, I do think the event 360 can be ignored as it doesn't apply to your environment. It doesn't seem to be linked to Windows Hello but rather to the Azure Active Directory (AAD) join and probe process. I observed it from two types of environment: on Workgroup computers (typically at home) and with on-premise Active Directory joined computers (corporate network) on Windows 10 1607+. was the finger print scanner trying to register, or was it possibly a malicious user device trying to get into my computer, or something else?) I have seen other accounts of people running into this error, but not much explanation, and the nature of the event is still largely unclear to me (e.g. Odd this would have caused this event when I was already logged in though.
I finally found after some more searching on revisiting this topic, that "Windows Hello" is likely associated with the finger print scanner. I did not try to print anything when the system froze. I do connect to a wireless printer, so that might be a clue, not sure if this message is in reference to that. a person attempting to connect to my computer)? Is there anywhere else I should check / actions I should take? Is this just a normal log entry, or indicating something possibly malicious (e.g. Does this mean someone is connected to, or tried to connect to my computer? I ran an antivirus scan, and looked in the security event log, and both results were okay. Google searching reveals that AAD is Azure Active Directory. I should not have any devices connected to my computer, it is a home computer. User certificate for on premise auth policy is enabled: Not Tested User is not connected to the machine via Remote Desktop: Yes
Local computer meets Windows hello for business hardware requirements: Not Tested Windows Hello for Business policy is enabled: Not Tested User has logged on with AAD credentials: No Windows Hello for Business provisioning will not be launched.ĭevice is AAD joined ( AADJ or DJ++ ): Not Tested I was trying to see what went wrong in the event viewer, and noticed several application hangs (not really a security concern), and then this, in the Administrative Events: Warnings section, which is more of a concern to me: It appears Windows Defender was coming up with a notification, but that froze as well. My computer just froze, and I ended up having to reboot.
0 kommentar(er)
