Windows Hello for Business - Event 360

Anonymous
2024-12-19T18:45:43+00:00

Recently performed an In-Place Upgrade (IPU) of my Win 10 22H2 system to remedy other issues. Following that IPU I find the following message about Windows Hello for Business. I do not need nor want WHfB and as far as I can tell it is not enabled yet is attempting to run with each boot as shown.

Group Policy Shows it as Disabled (I think). The double-negative grammar in the description is pretzel logic so hard to know what these settings actually imply

Similarly, the Registry shows Passport for Work is 'Enabled' Not, i.e., Disabled.

How to COMPLETELY disable Windows Hello for Everyone?

***Move from Windows / Windows 10 / Windows Hello, lock screen and sign-in***

Windows Windows Client for IT Pros Identity and access Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

18 answers

Sort by: Most helpful
  1. Anonymous
    2024-12-23T11:21:17+00:00

    Hello tocguy001,

    Thank you for posting in Microsoft Community forum.

    If the screenshot is local group policy or local registry setting?

    Please run the command dsregcmd /status to check if the Azure AD or AD.

    Please check if your device is registered to Intune.

    Here is a similar thread for your reference.

    How to fix Event Viewer warning User Device Registration Event ID 360 Windows Hello for Business provisioning will not be launched.  I have Windows 10 HOME. No business. - Microsoft Q&A

    I hope the information above is helpful.

    If you have any question or concern, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    0 comments No comments
  2. Anonymous
    2024-12-23T18:24:44+00:00

    "If the screenshot is local group policy or local registry setting?" In my original post there is a screenshot of the Local Group Policy settings and a different screenshot showing the Registry. Given that there is one of each, please rephrase your question so that I may understand it clearly.

    dsregcmd /status

    Device State

    AzureAdJoined : NO

    EnterpriseJoined : NO

    DomainJoined : NO

    Device Name : Redacted

    User State

    NgcSet : NO

    WorkplaceJoined : NO

    WamDefaultSet : NO

    SSO State

    AzureAdPrt : NO

    AzureAdPrtAuthority : NO

    EnterprisePrt : NO

    EnterprisePrtAuthority : NO

    IE Proxy Config for Current User

    Auto Detect Settings : YES

    Auto-Configuration URL :

    Proxy Server List :

    Proxy Bypass List :

    WinHttp Default Proxy Config

    Access Type : DIRECT

    Ngc Prerequisite Check

    IsDeviceJoined : NO

    IsUserAzureAD : NO

    PolicyEnabled : NO

    PostLogonEnabled : YES

    DeviceEligible : YES

    SessionIsNotRemote : YES

    CertEnrollment : none

    PreReqResult : WillNotProvision

    For more information, please visit https://www.microsoft.com/aadjerrors

    From the non-Microsoft link that you'd provided in your reply above I see that somehow Microsoft has configured WHfB to be enabled on systems that it is not compatible with such as Win 10 Home.

    As for Intune, I've never heard of it much less intentionally registered with whatever it might be. When these devices become more troublesome to operate and maintain than not they will cease to be used and MS market will ... dry up.

    0 comments No comments
  3. Anonymous
    2024-12-23T23:11:28+00:00

    I implemented the fixes described on the linked page you provided. Edited the Group Policies as well as the Registry. After reboot the same issue persists however as can be seen in the event log.

    So we've changed Group Policies and modified Registry values yet yielded no change to the underlying cause.

    https://filestore.community.support.microsoft.com/api/images/391e3807-5c45-4391-b980-9b6436dbf8aa?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OS3fxw3g%2BXfDiAtNkIrVbWcygSdQJEW8IynZZoBdQZmXXjR%2BaQQmHCEH3Hf7v9YqXDY4O1FQvPBe82PuSsvOv0UIJ9Bf0Fp7RdIHr341%2F%2B7q%2BjNqKPjaxSgFUO8Tp%2FefAy6u%2FvUPB4skSQnv6WPTwqMUoUEw%2BjFVkxoFv4xZCRkkE2GErKiga4wp%2B9DWOxghpQEfxbOnwDBBe0ZwEXYXb17g%2BtuckPXY4Os1y11IL4P%2FNOiE2zVYdwVYnLOEf95mkxh4TBHGAWyQCNb10CZl%2Bt4cES8hnnijqA%2B7vSJgZ96TQ%3D
    Another scan of the Registry reveals the following key with a seemingly related Value named EnableNgcUpsell set to 1. I could find no info describing this Value on Microsoft's sites.

    \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-HelloForBusiness/Operational

    Please advise...

    Thank you

    0 comments No comments
  4. Anonymous
    2024-12-24T09:15:45+00:00

    Hello

    Greetings!

    Please check the operating system version of your machine. Please run the command winver to check.

    Is it Windows Home edition?

    Best Regards,
    Daisy Zhou

    0 comments No comments
  5. Anonymous
    2025-01-09T16:07:49+00:00

    Windows Hello still trying to run at startup.

    Also, neither DISM nor SFC have had an effect on remedying this issue.

    TY for your support.

    1 person found this answer helpful.
    0 comments No comments