,Japan

en[EVENT359] Windows Hello for Business provisioning has encountered an error during policy evaluation.

Microsoft-Windows-User Device Registration/Admin error logged.
This is related to Windows Hello for Business.
There is a distinction between Windows Hello and Windows Hello for Business.
If you are using biometric authentication such as fingerprint authentication on your Windows PC, this article is not for reference.
The procedures described are at your own risk.
Event Log
message | Windows Hello for Business provisioning has encountered an error during policy evaluation. ExitCode: The specified file cannot be found. Method: WinStationIsSessionRemoteable See https://go.microsoft.com/fwlink/?linkid=832647 for more details |
log name | Microsoft-Windows-User Device Registration /Admin |
Source | User Device Registration |
Event id | 359 |
level | error |
user | Login user |
GPEDIT.msc
Use the Local Group Policy Editor (GPEDIT.msc). Windows 10 Home must be activated. Related post
How to mitigate the error
1. Start Local Group Policy Editor
Hold down the Windows key on the keyboard and press R to start "Run" , then type gpedit.msc and click OK .
2. Display "Use Windows Hello for Business"
When the Local Group Policy Editor starts, make the following transition to display "Use Windows Hello for Business".
gpedit.msc> Local Computer Policy> Administrative Templates> Windows Components> Windows Hello for Business> "Using Windows Hello for Business"

3. Disable "Use Windows Hello for Business"
Since it is "unconfigured", click the "Disable" check button and then click OK .When there is no effect ... (PLAN-B)
The error recording stopped on my PC by the procedure in the previous section.If you don't see any improvement, you have PLAN-B.
Let's disable the two options for Windows Hello for Business.
Local Group Policy Editor> Windows Hello for Business
- Use a hardware security device
- Use biometrics

Summary
[Event ID 359]- Disable "Use Windows Hello for Business"
- Disable "Use hardware security devices"
- Disable "Use biometrics"
Doesn't WORKGROUP matter?
According to the English article I read, "Windows Hello for Business can only be used with AD or Azure AD. So I don't think you need to worry if the error is recorded on a PC that is not under AD (Active Directory). (I don't care about my home PC...)
Validation: Windows 10 Pro October 2018 Update, v1809
en-event の記事 (Articles about the en-event)
- Windows 11 22H2 and the event log (tak)
- en[EVENT131] Metadata staging failed
- en[EVENT7009] Service Control Manager (SCM)
- en[EVENT2484] Tile Database Corruption
- en[Event ID 10016] How to fix PerAppRuntimeBroker error
- en[Event3] Kernel-EventTracing Microsoft Security Client OOBE
- en[EVENT2002] Eap method DLL path
- en[EVENT333] ESENT error (taskhostw, WebCacheV01.dat)
- en[EVENT10016] Windows.SecurityCenter.WscBrokerManager, APPID not available
- en[EVENT34] Cancel power saving setting of power management of Bluetooth HID device
- en-event ラベルの記事(要約付)
- Japan が含まれる記事(要約付)
新着順 (New arrival order)
- なぜ必要?DNSキャッシュクリアの重要性と具体的な手順
- 【緊急】KB5063060配信開始:Easy Anti-Cheat搭載PC向け自動適用の理由とは
- 【トラウマ】藤井聡太との死闘が残したもの──タイトル戦はトップ棋士の試金石
- 【VAIO】BIOS R0500K9リリース:Windows 11 24H2対応と脆弱性修正の詳細(2025年06月11日)
- 【Pixel/2025年6月】Android 16と指紋認証、Bluetooth、カメラ、システムの改善と修正
- 【盛者必衰】四段経験なしで全棋士を統括?清水市代新会長誕生が将棋界にもたらす衝撃と期待
- 【Windows 11】24H2 アップデート後のトラブルシューティング(DISM, SFC, コンポーネントサービス)
- Intel(R) ME Firmware Ver.11.8.97.4739(2025年6月3日)【vaio】
- 【Clibor】行頭に連番を挿入する方法【New!】
- 【ブログ執筆者必見】Cliborでテキスト整形をマスター!コピペ効率を劇的に上げる方法
タイトル:en[EVENT359] Windows Hello for Business provisioning has encountered an error during policy evaluation.:SC2
このサイトを検索 | Search this site