,Japan
Event ID 359.
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
:SC2
このサイトを検索 | Search this site