What is causing the “Windows Hello for Business provisioning will not be launched“?
We investigated this particular issue by looking at various user reports and the repair strategies that most affected users have used to resolve this particular error message in Event Viewer. Based on our investigations, there are several different scenarios that are known to trigger this particular issue: If you’re looking for a method that will prevent the “Windows Hello for Business provisioning will not be launched” error from filling up your Event Viewer, this article will provide you with several troubleshooting strategies. Down below, you’ll discover several different repair strategies that other users in a similar situation have used to get the issue resolved. For the best results, follow the methods in the order that they are presented since they are ordered by efficiency and severity. One of them is bound to resolve the issue in your particular scenario.
Method 1: Modify the Windows Hello policy
As some users have reported, there is one method that will allow you to enforce a policy on your machine that will ensure that the “Windows Hello for Business provisioning will not be launched” error will no longer fill up your Event Viewer. There are two different policies that you need to adjust in order to ensure that the issue is resolved. Here’s how to modify the WIndows Hello policy in order to prevent the Event Viewer message from appearing again: If you’re still seeing new instances of the “Windows Hello for Business provisioning will not be launched” error or this method wasn’t applicable, move down to the next method below.
Method 2: Using Registry Editor to disable the PassportforWork policy
If the first method was not applicable or you didn’t want to the GPedit utility, you can replicate the same step from the Registry Editor. This way, you’ll ensure that you’ll not see any new Event Viewer events with “Windows Hello for Business provisioning will not be launched” error. But keep in mind that the change will only be applicable to one computer. If you’re experiencing the error on multiple computers from the same network, Method 1 is preferable. Here’s what do to disable the PasswordforWork policy using the Registry Editor: At the next startup, check your Event Viewer and see if there are new “Windows Hello for Business provisioning will not be launched” error. If you’re still seeing new error events, move down to the next method below.
Method 3: Disabling the Log Provider for Windows Hello
Another reason why you might see constant Event Viewer events with the message “Windows Hello for Business provisioning will not be launched” error is that your machine doesn’t have the necessary hardware to logging on with Hello. In this case, the only applicable method is to follow the steps below to disable the Log Provider for Windows Hello. This will stop any associated events from being logged, which will spare you from receiving any new error messages in Event Viewer. Note: Keep in mind that this method will only mask the problem, not fix it. So even if you’ll stop receiving “Windows Hello for Business provisioning will not be launched” errors, it will be because the Log Provide will be disabled not because the issue was resolved. Here’s a quick guide on disabling Log Provider for Windows Hello via Registry Editor:
AMD ‘Vermeer’ ZEN 3 Ryzen 4000 CPUs Will Be Launched In 2020 Assures Co. While…TPM Provisioning Service Not Working? Here’s the Fix!Fix: “Verizon Provisioning Error” on Android/iPhone?How to Fix Windows Hello not Working on Windows 10
