Код ошибки 80090016 офис 365

Содержание

Код ошибки Outlook 80090016

Вы хотите исправить код ошибки Outlook 80090016 для Office 365? Если вы ИТ-специалист и управляете Office 365 для ваших клиентов это руководство может помочь вам исправить ошибку доверенного платформенного модуля (TPM), которую могут увидеть ваши клиенты. Некоторые клиенты при синхронизации контактов или электронной почты будут запрашивать учетные данные. После успешного ввода учетных данных их снова попросят ввести то же самое. И тогда возникает следующая ошибка:

Что-то пошло не так. Модуль Trusted Platform Module на вашем компьютере неисправен. Если эта ошибка повторится, обратитесь к системному администратору с кодом ошибки 80090016.

Выполните следующие действия, чтобы исправить код ошибки Outlook 80090016 для Office 365:

Решение 1. Удалите TPM и проверьте.

После успешной перезагрузки компьютера проблема устранена, а это означает, что микросхема TPM действительно повреждена, поэтому вам следует попытаться найти замену ее оборудованию.

Если проблема «Код ошибки Outlook 80090016» по-прежнему возникает, попробуйте другое решение, указанное ниже.

Решение 2. Переименуйте подключаемый модуль проверки подлинности Azure Active Directory.

Ударить + R и ввод %appdata%LocalPackages и нажмите клавишу Enter или нажмите ОК.

Имейте в виду, что Microsoft. AAD. BrokerPlugin_cw5n1h2txyewy папка будет автоматически воссоздаваться при каждом входе в систему затронутого клиента. Просто запустите Outlook, а затем разрешите организации управлять устройством. Если вы получаете какую-либо ошибку TPM, игнорируйте ее и продолжайте использовать Outlook. Однако тогда ошибка «Код ошибки Outlook 80090016» может больше не появляться.

Заключение:

Надеюсь, теперь вы понимаете, как исправить код ошибки Outlook 80090016. Если шаги окажутся полезными, поделитесь ими со своими друзьями и помогите им. Для дальнейших запросов и вопросов дайте нам знать в разделе комментариев ниже. Также не забудьте поделиться с нами своими отзывами!

Код ошибки Outlook 80090016

Что-то пошло не так. Модуль Trusted Platform Module на вашем компьютере неисправен. Если эта ошибка повторится, обратитесь к системному администратору с кодом ошибки 80090016.

Выполните следующие действия, чтобы исправить код ошибки Outlook 80090016 для Office 365:

Решение 1. Удалите TPM и проверьте.

Если проблема «Код ошибки Outlook 80090016» по-прежнему возникает, попробуйте другое решение, указанное ниже.

Решение 2. Переименуйте подключаемый модуль проверки подлинности Azure Active Directory.

Ударить + R и ввод %appdata%LocalPackages и нажмите клавишу Enter или нажмите ОК.

Заключение:

Outlook: Something Went Wrong Error 80090016

Outlook Error 80090016

Note: The this won’t affect users who are subject to MFA (Multi Factor Authentication,) so this can be enabled to solve this problem.

Solution One Code 80090016

On the affected machine navigate to;

Outlook Error something went wrong

Rename that folder to Microsoft. AAD. BrokerPlugin_cw5n1h2txyewy. old

The log out and back in again.

Solution Two Code 80090016

WARNING : This involves disabling modern authentication, do not consider this a fix, it’s more of a work around, that will stop working in or around November 2019, when modern authentication is manditory.

On the affected machine, run regedit and navigate to;

Create a new DWORD (32 Bit) Entry

Outlook EnableADAL

What does this do?: It disables ‘Modern Authentication’.

Then restart Outlook. (Note: It may re-prompt for a password).

Author: PeteLong

41 Comments

“What does this do?: It enables ‘Modern Authentication’.”

Hi Bruce (correct! – need more coffee)
– And don’t call me Shirley! ?

Worked a treat with a client battling this issue. Thanks!

Working perfectly.
Thank you so much ?

You made my day. It solved this 3 days pending issue in 10 seconds. That’s great.

I followed the steps, restarted outlook, and am still having the same issue. I wonder what else could be causing the problem.

me too, same error remains (after rebooting too)

Reg entry worked for me. THANKS.

oh man worked like charm thanks

This may resolve the issue, but I feel like jumping straight into disabling modern auth is not the best resolution.

Firstly Thanks for the feedback, If you feel there’s a better solution, please post it here for the benefit of others.

Thanks PeteLong for your hints. Nevertheless I agree with Heywood, it is not a good idea to disable Modern Authentication. And I am affraid it is the one who propose a solution who should estimate the impact and offer other options when it has undesired consequences.

Guys, Do some research! if a tenant requires MFA/ADAL or OAuth they will have it enabled at an ORG level, so disabling it on a client machine will make no difference whatsoever. If you disable it on a client and it can still connect it was not being used anyway.

While I appreciate all feedback, think like technicians, if you don’t like a solution, then either find a better one, and communicate it to your peers, or don’t implement the solution that I propose. Remember I’m providing this information for free, for the benefit of the technical community.

If modern auth is not working for a single client then disabling it is a workaround. While this may get someone out of a tough spot, calling it a solution is misleading. Nothing wrong with a workaround, but it is best to at least highlight the risks of disabling the more secure authentication method if that is what you are recommending.

You saved my day and swett
Thank you so much

You saved my working hours, Thank you very much….

Great, working perfectly. Thank you so much.

This is actually a poor solution if you are in an enterprise environment as it disables modern authentications and defaults to legacy.

If that’s the better solution, it’s the first one that’s been offered, can anyone confirm that this resolves the issue? If so I’ll update ether article accordingly?

Pete I tried the tip from BraveSpear and it worked for me

Thank you Andrew article updated accordingly. Kudos to BraveSpear.

BraveSpear’s solution worked for me as well.

#1 Worked for me. Thanks

worked for me, Thanks for the tips

Solution 1 worked perfectly…

I had similar issue that was resolved by uninstalled the “Trusted Platform Module” in Device Manager and restart the computer.

Wouldn’t let me change the name of the file like in solution 1 because it said that the file was in use. Uninstalling from device manager worked for me as well, so thank you!

dude you saved my day. thanks for this pinpoint solution.

trying method one but file is locked and cannot be renamed. Used by another app. But I do not know which one…

Make sure Outlook is closed, and it’s not running in the task tray, and no other users are logged in.

The registry change worked fine, thanks, until we can apply a better correction.

Renaming the folder doesn’t work in all situations. I’ve now encountered this specific issue on 5+ machines. For several of them, renaming the folder did the trick. For the rest, I’ve ended up recreating the user profile, after trying everything else. The question is, why is this becoming a regular thing?

Thanks, this information is very usefull

Muchas gracias por compartir esta información, para mi la solucion #1 no funcionó, la opcion de Regedit SI.

Tal como alguien pregunta más arriba, sería interesante saber porque se está produciendo esta situación.

Solution 2 its working for me thank you man

Hi.
This worked on a computer that has issues whith all kinds of authentication. Outlook, OneDrive, Chrome sync account, Adobe Cloud account and so on.
Well, it worked for a while that is. After three or four re-boots and about the same ammount of shut-downs the issues are back.
Thanks anyway…

Hi, thank you so much, Solution N1 work for me! Like Joakim said, I don’t know if the fix will work for longer than 3-4 reboots. I will let you know. Thank you.

Thanks for this – Solution 1 was part of the solution for me.

This user seems to have a damaged TPM – and if I enforce MFA in the Admin console for that user, it generates an error on the endpoint, saying malfunction in TPM.

If I disable MFA for that user, he still has to accept a login prompt in the Authenticator, and all his apps seem stable and fine with the saved login.

Turn on MFA again – problem returns.

Disabling MFA for that user (perhaps as long as the user had previously enrolled his device to authenticate logins) seems to retain the MFA security, but not contact the TPM for whatever generates the problem.

So, there could be 3 things going on simultaneously:
1. Cooked TPM
2. Enabling enforcement of MFA generates the TPM error
3. bad data of something in the path specified in Solution 1 above.

Maybe this helps someone!
Live long and prosper

tried solution 1 but windows says the file to rename is being used by another program. what program uses this so I can close it?

Источники:

https://ru. obecmacov. sk/how-fix-outlook-error-code-80090016

https://www. petenetlive. com/kb/article/0001549