Windows hello for business provisioning will not be launched 360
Windows Hello for Business provisioning will not be launched — что это?
Приветствую. Windows Hello for Business provisioning will not be launched — сообщение в журнале событий, переводится как подготовка Windows Hello для бизнеса не будет запущена.
Начинаем разбираться
Собственно вопрос — как отключить данное предупреждение? На форуме Microsoft нашел способ — работает он или нет, к сожалению сказать не могу, у меня нет такого предупреждения. Как я понимаю — нужно отключить Windows Hello for Business, и это сделать можно через Редактор локальной группой политики. Итак, зажимаем кнопки Win + R, пишем в окошко команду:
Откроется редактор. Переходим сюда: Конфигурация компьютера > Административные шаблоны > Компоненты Windows > Windows Hello для бизнеса:
В этом разделе, справа будут настройки:
В результате должно получится так:
Если у вас в этом окне будет больше трех опций — попробуйте и их отключить.
Важно! Оказалось настройка есть также и в разделе Конфигурация пользователя. То есть путь такой же, но только Конфигурация пользователя:
У меня лично здесь опций нет:
Будут опции — пробуйте отключать.
На форуме Ru Board был найден еще один способ
Один юзер на форуме написал — если отключение Windows Hello for Business не помогает, попробуйте в реестре отключить. Запустите реестр — зажмите Win + R, напишите команду:
Перейдите по этому адресу:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-User Device Registration/Admin
Два раза нажимаем по параметру Enabled:
Значение меняем на 0:
Данный способ был написан на форуме 12-12-2017, работает ли он сейчас — неизвестно. Надеюсь — работает.
Надеюсь информация помогла. Удачи.
Добавить комментарий Отменить ответ
Этот сайт использует Akismet для борьбы со спамом. Узнайте как обрабатываются ваши данные комментариев.
Windows hello for business provisioning will not be launched 360
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I am trying to deploy windows hello. I have a 2016 DC with FSMO roles. I have writeback enabled in AAD Connect.
Hybrid Key Trust
Device Writeback
MFA license
User password and device syncing
PKI setup
2016 DC with all FSMO Roles..There are 2 other 2012 R2 Dc’s. I have verified my test computer is using the 2016 for logon.
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Yes
User has logged on with AAD credentials: Yes
Windows Hello for Business policy is enabled: Yes
Local computer meets Windows hello for business hardware requirements: Yes
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Yes
Enterprise user logon certificate enrollment endpoint is ready: No
Enterprise user logon certificate template is : Not Tested
User has successfully authenticated to the enterprise STS: No
Certificate enrollment method: enrollment authority
All replies
To retrieve the join status please Open the command prompt as an administrator:
Type dsregcmd /status
Review the following fields and make sure that they have the expected values:
AzureAdJoined : YES
This field indicates whether the device is joined with Azure AD. If the value is NO, the join to Azure AD has not completed yet.
-Your federation server does not have WS-Trust endpoints enabled
-Your federation server does not allow inbound authentication from computers in your network using Integrated Windows Authentication.
-There is no Service Connection Point object that points to your verified domain name in Azure AD in the AD forest where the computer belongs to
Windows hello for business provisioning will not be launched 360
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I am trying to deploy windows hello. I have a 2016 DC with FSMO roles. I have writeback enabled in AAD Connect.
Hybrid Key Trust
Device Writeback
MFA license
User password and device syncing
PKI setup
2016 DC with all FSMO Roles..There are 2 other 2012 R2 Dc’s. I have verified my test computer is using the 2016 for logon.
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Yes
User has logged on with AAD credentials: Yes
Windows Hello for Business policy is enabled: Yes
Local computer meets Windows hello for business hardware requirements: Yes
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Yes
Enterprise user logon certificate enrollment endpoint is ready: No
Enterprise user logon certificate template is : Not Tested
User has successfully authenticated to the enterprise STS: No
Certificate enrollment method: enrollment authority
All replies
To retrieve the join status please Open the command prompt as an administrator:
Type dsregcmd /status
Review the following fields and make sure that they have the expected values:
AzureAdJoined : YES
This field indicates whether the device is joined with Azure AD. If the value is NO, the join to Azure AD has not completed yet.
-Your federation server does not have WS-Trust endpoints enabled
-Your federation server does not allow inbound authentication from computers in your network using Integrated Windows Authentication.
-There is no Service Connection Point object that points to your verified domain name in Azure AD in the AD forest where the computer belongs to
how to disable Windows Hello for Business
I got this warning message on Event Viewer:
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
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 https://go.microsoft.com/fwlink/?linkid=832647 for more details.
OS Name Microsoft Windows 10 Pro
Version 10.0.16299 Build 16299
System Type x64-based PC
Replies (20)
* Please try a lower page number.
* Please enter only numbers.
* Please try a lower page number.
* Please enter only numbers.
This is a policy you can set on your machine.
Right click your start button and select run.
Type gpedit.msc
Go to Computer Configuration > Administrative Templates > Windows Components > Microsoft Passport for Work OR Windows Hello for Business
Edit «Use Microsoft Passport for Work» OR «Use Windows Hello for Business» and set it to disabled.
63 people found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
«Windows cannot find ‘gpedit.msc’. Make sure you tuped the name correctly, and then try again»
Windows search » Computer Configuration» not found.
9 people found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
13 people found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
17 people found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
I checked the registry and \HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork Enabled is set to 0.
I am using the administrator account.
2 people found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
This is a policy you can set on your machine.
Right click your start button and select run.
Type gpedit.msc
Go to Computer Configuration > Administrative Templates > Windows Components > Microsoft Passport for Work OR Windows Hello for Business
Edit «Use Microsoft Passport for Work» OR «Use Windows Hello for Business» and set it to disabled.
I did this and still in event log I get Hello for business will not be launched, device AAD joined (AAD or DJ+++) not tested
Hello for business is enabled not tested. Lots more information all stated as not tested. Whenever I click on any of the links for more information I get page not found. All in all pretty bad show Microsoft. I never had any of the events I have now before the last update, all the updates were with useless stuff that I just do not need.
20 people found this reply helpful
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
First question to ask. What version of Windows 10 do you have?
Then the reasonable solution, this should be the ‘standard’ response in this forum. I can’t even tell you how much wasted time people have burned looking for Group policy editor, in the home version of Win10 when looking for answers in this forum. Don’t get me wrong, I totally appreciate the volunteers and users that try and help.
NOW, back to the problem. I for one am tired of the common event viewer problems that have plagued Windows for three versions )7, 8.x, 10 x four major updates. DCOM permission errors are the main headache for people whom ‘care’ about errors in the OS. This Hello for Business is one that is utterly unnecessary as this is the HOME version of Windows 10. Lets just get RID OF IT. Set it up as an APP in the store for those who want it, and have a compatibility check BEFORE download and installing it. Tada! done, problem solved.
So the question is, where is this located, and where is the uninstall routine for it? Surely Microsoft wouldn’t ‘force’ this on us, in a OS where it can’t even be used? Cluttering up the event viewer with yet another distraction for some of us that would like to have as close to an error free system as possible.
Windows hello for business provisioning will not be launched 360
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
I am trying to deploy windows hello. I have a 2016 DC with FSMO roles. I have writeback enabled in AAD Connect.
Hybrid Key Trust
Device Writeback
MFA license
User password and device syncing
PKI setup
2016 DC with all FSMO Roles..There are 2 other 2012 R2 Dc’s. I have verified my test computer is using the 2016 for logon.
Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Yes
User has logged on with AAD credentials: Yes
Windows Hello for Business policy is enabled: Yes
Local computer meets Windows hello for business hardware requirements: Yes
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Yes
Enterprise user logon certificate enrollment endpoint is ready: No
Enterprise user logon certificate template is : Not Tested
User has successfully authenticated to the enterprise STS: No
Certificate enrollment method: enrollment authority
All replies
To retrieve the join status please Open the command prompt as an administrator:
Type dsregcmd /status
Review the following fields and make sure that they have the expected values:
AzureAdJoined : YES
This field indicates whether the device is joined with Azure AD. If the value is NO, the join to Azure AD has not completed yet.
-Your federation server does not have WS-Trust endpoints enabled
-Your federation server does not allow inbound authentication from computers in your network using Integrated Windows Authentication.
-There is no Service Connection Point object that points to your verified domain name in Azure AD in the AD forest where the computer belongs to