Windows 10: Windows Hello for Business is STILL getting the EVENT 360 during startup, event after...

As can be seen from some LOCKED posts on this thanks Microsoft, the EVENT 360 is STILL seen in current Windows 10 AND windows 11 systems, even after disabling the GPEDIT.MSC Computer AND User Administrative Templates for the Use Windows Hello for Business section. This has been happening for a long time by the look of the post belowwEven this post from August 2018 quotes the issue:"I'm having the same issue, and setting 'Use Windows Hello for Business' to Disabled for both Computer and User via gpedit.msc on windows 10 Pro didn't work for me. Still getting the event."I consider this a bug,

:)

 

Event 360 / Windows Hello for Business


Hi all

A gumby-level question.

1. I noted today:

Event Viewer > Custom Views > Administrative Events > Warning, 22/04/2018, 9:03:25 AM.

"Event 360, User Device Registration", which is associated with Windows Hello for Business.

2. I have Windows 10 Home Edition, v. 1709, build 16299.371.

3. Why, I wonder, is my OS fussing with a Business version of Hello Windows?

Any thoughts?

Cheers

 

Event ID 360 errors

Dear PatrickWoehl

Hope you are doing great.

As described in the thread below, there are many reasons involved in this event ID 360, please refer to the list of reasons in the following thread, which are all worth checking

Event ID 360 and 362 Windows Hello For Business does not provision





According to the error event 360, one of the above reasons was trying to register this device all the time. Disabling this key can fix this problem

 

Microsoft 10 Event ID 360 Windows Hello for Business provisioning will not be launched.

I am consistently getting a warning in Event Viewer with Event ID 360. The General Notes state:

Windows Hello for Business provisioning will not be launched.

Device is AAD joined ( AADJ or DJ++ ): Not Tested

User has logged on with AAD credentials: No

Windows Hello for Business policy is enabled: Not Tested

Windows Hello for Business post-logon provisioning is enabled: Not Tested

Local computer meets Windows hello for business hardware requirements: Not Tested

User is not connected to the machine via Remote Desktop: Yes

User certificate for on premise auth policy is enabled: Not Tested

Machine is governed by none policy.

See Windows Hello for Business cloud Kerberos trust deployment guide for more details.

Anyone have a resolution to this warning?

My Computer info is as follows:

OS Name Microsoft Windows 10 Pro for Workstations

Version 10.0.19041 Build 19041

Processor: Intel(R) Core(TM) i9-9900KS CPU @ 4.00GHz, 4008 Mhz, 8 Core(s), 16 Logical Processor(s)

MotherBoard: ROG MAXIMUS XI CODE
Video: ASUS ROG-STRIX-RTX2080TI